Start with one ActionReceipt.
Run it beside an existing workflow before using it for any gate. Research challenges and independent checker work follow after the stable integration path.
01
Receipt one action in shadow mode
Add an ActionReceipt beside one existing operational log. Keep it out of production gates and settlement actions while you compare the records.
Start →02
External reliance candidate → possible D
Apply a published ReliancePolicy, sign the bulla.rely and boundary receipts, and retain the closed evidence package. Intake is open; the packet remains NOT_COUNTED until signed qualification and head records merge.
Start →03
Independent witness candidate → possible W
Run the public source-only operator kit under separate control, retain both release receipts, publish the read-only proof surface, and submit the closed candidate. A candidate never counts itself.
Start →04
Replay candidate → r
Run the frozen Python and standalone Node reports over the constructed witness fork and 10,000-decision graph. This does not create an outside witness operation.
Start →05
Prepare a cross-system disagreement
Describe how two systems or organizations use the same term differently. The browser prepares a private draft for you to keep or share.
Start →06
Challenge one claim
Test an authority, privacy, effect, or generalization claim. Findings remain publishable even when they contradict the project.
Start →07
Independent implementation → I
Implement a bounded checker from its written profile without importing Bulla.
Start →Prepare a signed candidate.
Keep the provider ActionReceipt, receiver-signed bulla.rely receipt, signed boundary receipt, organization-key attestations, control evidence, and runtime replay in one closed package. The public checker must recompute the same RELY, REFUSE, or ESCALATE outcome.
Intake is open at D0. A passing packet remains NOT_COUNTED until the dedicated intake authority signs a qualification event and ledger head and the reviewable pull request merges. The packet does not establish a later payment, deployment, or other worldly effect.
A fifteen-minute seam intake
Prepare the seven facts needed for a private report. Do not send secrets, personal data, credentials, or records you lack authority to disclose.
Analysis template
The review method asks for a typed claim chain, countermodel or distinction, RELY/REFUSE envelope, evidence options, burden coordinates, finality obstruction, and a replayable receipt. This page prepares the intake only; it does not submit an analysis request.
Read the review constitution →