Experimental source example · not in the installed Bulla package
Release eligibility waits for rollback evidence.
A deploy agent reports that staging is ready. A release agent still requires a rollback-test record before production promotion can become eligible.
Bulla evaluates retained records against policy fixed before delivery. Missing evidence produces a request for the exact record; a verified failure refuses the consequence.
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.
After rollback evidence arrives
Recomputed fields
- Rollback-test requirement: missing → satisfied.
- Receiver decision: wait → proceed under its policy.
- Promotion eligibility: ineligible → eligible.
Unchanged records and authority
- Deploy agent’s staging claim.
- Exact build and accepted contract.
- Authorization remains unissued.
- No promotion is attempted.
Conditional evidence request
A missing-evidence result describes what a future record must satisfy. Correct binding to this build, contract, environment, and accepted test authority would satisfy the requirement only when the verified result is PASS. No current test existence, passing result, or release follows from the request.
Policy changes require a new contract revision and hash. They cannot rewrite the earlier result or substitute for evidence under the accepted revision.
Reproduce the source-only alpha
Three compact transactions cover missing, passing, and failing rollback evidence. Python output reports the receiver decision, consequence eligibility, authorization, and execution separately.
Project-authored synthetic cases establish none of deployment occurrence, receiver-log completeness, or reproduction by another implementation.