Experimental · Acceptance Contract
The receipt is not the decision.
A deploy agent reports that staging is ready. The release agent still requires a rollback-test record before production promotion can become eligible.
Bulla evaluates the retained transaction against a policy fixed before the delivery. If required evidence is missing, the report names the record to supply and waits. A verified failure refuses the consequence instead.
A deploy agent says the requested build is ready in staging. The release agent has one additional requirement before production promotion can become eligible.
- Deploy-agent claim
- Staging ready
- Requested build
- Matches
- Staging-controller observation
- Present
- Rollback-test result
- Missing
- Release-agent decision
- Wait for evidence
- Next required record
- Signed rollback-test result
- Production promotion
- Not eligible
- Authorization
- Not issued
- Promotion attempt
- Not attempted
The receipt preserves the staging claim. The release agent waits because the required rollback-test record is absent.
Eligibility is not authorization. This demonstration does not deploy anything.
Technical evidence
- decision
- HOLD_FOR_EVIDENCE
- eligibility
- INELIGIBLE
- authorization
- NOT_ISSUED
- execution
- NOT_ATTEMPTED
The browser renders a projection generated by the project-authored Python evaluator. It does not run the evaluator in the browser or establish that the deployment claim is true.
Limits of this demonstration
This synthetic demonstration evaluates retained records under one project-authored policy. It does not deploy anything or establish that the agent's claim is true.
Technical evidence
The profile, transaction, roles, keys, records, evaluator, and formal model are project-authored. A conditional evidence request does not establish that the requested test exists, will pass, or guarantees promotion. The result does not establish deployment occurrence, worldly truth, receiver-record completeness, legal enforceability, production use, organizational independence, or external implementation parity.
What changes. What stays fixed.
Changes after the record arrives
- Rollback-test requirement: missing → satisfied.
- Receiver decision: wait → proceed under its policy.
- Promotion eligibility: ineligible → eligible.
Does not change
- The deploy agent’s staging claim.
- The exact build and accepted contract.
- Authorization remains unissued.
- No promotion is attempted.
What the request means
The missing-evidence result is conditional. It says that a newly supplied record, correctly bound to this build, contract, environment, and accepted test authority, would satisfy this requirement if its verified result is PASS. It does not say that the test exists, will pass, or guarantees a release.
Changing the release standard is not evidence. A policy change requires a new contract revision and hash; it cannot rewrite the earlier result.
Reproduce the source-only alpha
The corpus contains three compact transactions: missing, passing, and failing rollback evidence. The Python checker reports the decision, consequence eligibility, authorization, and execution separately.
This project-authored synthetic demonstration does not establish that deployment occurred, that the receiver record is complete, or that another implementation reproduces the result.