Small, runnable examples of automation that stops when evidence is missing or conflicting, explains why, and leaves the next decision with a person.
Try the interactive demo · Українською · See the proof pack
python3 run_proof.pyUse Python 3.12 and Node 24.14.0, matching CI. The Python implementations use the Python standard library and
no installed packages. Node tests the browser-local explorer with its
built-in vm, not npm or installed JavaScript packages.
- Evidence gate · Missing, stale or conflicting evidence produces an explicit hold; high-risk work escalates.
- Async polling contract · Submit, retain an ID, poll with bounded backoff, and handle completion or failure.
- Operating-core composition · One synthetic chain from evidence check to a local review handoff.
- Immutable artifact handoff · Bytes and a receipt remain bound across partial publication, digest conflict and namespace replacement.
- Agent action admission · A typed request must match the declared tool and simulator before local review.
- Bounded local-context review · Exact local source identities and deterministic lexical matching produce
local-context-review-readymetadata. - Operator handoff · A narrow evidence packet reaches
review-required; stale, malformed or conflicting input is refused.
All examples use synthetic inputs and local effects. No real provider calls, authenticated approvals or production deployments are demonstrated. Passing the tests establishes these fixtures, not safety for another system.
The proof pack contains fixture identities, checked outcomes and limits. The source and CI use the same proof command.
AI-assisted engineering by DiadkoShmek. Project index · External results.
Published for portfolio review. No reuse license is granted at this stage.