01
Reviewed decision
The useful constraint is kept with its source and authority.
Illustrative 60s demo
Claude finds the decision. Codex picks it up.
Follow a fictional repository example from a reviewed source to a later coding session and its verification step. It demonstrates the workflow, not a customer result.
acme-billing / zsh
Project packet
State
Claude Code session
Risk
billing and permissions
Next
review current policy
~/repos/acme-billing
>$ rg "workspace invite" apps docs
>$ rg "paid seats" apps docs
>$ rg "billing intent" apps docs
okfound: current seat policy and an older conflicting note
What changes
The demo is not a bigger prompt. It is a smaller decision packet.
Snipara does not replace the model. It gives the selected model a cleaner start: current decision, impact, verification, and a receipt path.
02
Later session
Another agent retrieves the decision before it edits.
03
Verification
The handoff includes the check that should confirm the change.
Inspect the public evidence
Review the protocol, limits, and setup.
The public proof page documents the controlled study and identifies which artifacts are available. Evals explains the method and limits; the quickstart shows the setup.