Candidate
The concrete generated state and exact diff presented for review.
Evidence
“Done” is not proof.
StateHinge is designed so accepted agent work leaves a trace connecting what was planned, what candidate existed, what checks ran, what a human approved, what was promoted and what recovery restored.
The evidence objects.
Validation
The declared validators and their terminal results.
Acceptance
The explicit human decision tied to that concrete candidate.
Recovery
Checkpoint/rollback result and evidence of the expected baseline.
What a hash does—and does not—prove.
A digest can establish identity or integrity of recorded bytes. It does not prove that code is correct, secure, valuable or free of unseen defects. StateHinge keeps that distinction explicit rather than turning a hash into a safety claim.
Why it matters
Evidence lowers the cost of reconstructing what happened.
For a team, the value is not the existence of another log file. It is being able to answer the operational questions quickly: Which candidate? Which checks? Which approval? Which accepted state? Which recovery baseline?
See the workflow