Input contract parsed and bound to a check
A check ran; its captured output is referenced on this step.
evidence attached — verifying
Loading…
Deterministic gates decide completeness from verifiable facts only; model self-assessment informs, never gates.
Illustrative / representative sample data.
The verifier has no write access to implementation and never grades its own output.
The hash-chained log is tamper-evident proof that execution happened as recorded (proof of execution) — distinct from proof that generated code is correct (proof of correctness), which is out of scope. Z3 checks the requirement logic model, not generated code.
Walk the audit trail
This is what the gate sees: a hash-chained trace where every requirement moves from unproven to evidence-attached to proven. When one item never produces a check that ran, the gate holds the line — and the run does not get to call itself complete.
A check ran; its captured output is referenced on this step.
evidence attached — verifying
Use Back / Advance, the progress rail, or the arrow keys to step the run. The gate decides from verifiable facts only — it never marks the run complete while an item is unproven.
Input contract parsed and bound to a check
sha256:genesis → sha256:a1c4…parse
evidence: tests/contract/parse_input_test — captured run output
Code wired into a live execution path
sha256:a1c4…parse → sha256:b3d9…wire
evidence: tests/integration/dispatch_path_test — captured run output
Evidence record emitted by the independent verifier
sha256:b3d9…wire → sha256:c7f2…emit
evidence: verifier/emit_record_test — captured run output
Downstream ledger reconciliation
sha256:c7f2…emit → sha256:d5e0…ledger
evidence: none — no check has run
The line is held.
gate held an unproven item — fail-closed, correct
run status: HELD — not complete (an unproven item remains)