Receipts
We claim Kontour makes AI-assisted work inspectable and recomputable. Here are real trust.bundle artifacts to test that claim — each produced by one of our own pipelines, rendered from its actual contents, downloadable as the raw file, and validated by the same tool we tell you to run. Nothing here is a hand-written sample.
Honest framing: these are Kontour's own pipeline receipts (dogfood). They demonstrate the format is real and checkable — not that an outside team has adopted it. Landing an external team's receipt is an open pursuit we track separately, not a claim this page makes.
Kontour Flow Agents — delivery workflow
The trust.bundle a Flow Agents delivery run emits as its own receipt: every workflow check (build, source-tree validation, verification) recorded as a claim with its evidence and status.
Kontour Veritas Governance Kit — readiness adapter
A Veritas Governance Kit readiness evaluation with no blocking failures, projected into a Hachure trust.bundle whose software-readiness-verdict claim derives to verified.
Kontour Veritas Governance Kit — readiness adapter
A readiness evaluation that a required standard blocks: the projected software-readiness-verdict claim derives to disputed, showing what a gate looks like when it refuses to pass.
Recompute, don't trust
Every bundle above is a Hachure trust.bundle. Download one and run it through @kontourai/surface's validateTrustBundle — the named validator. The CLI wraps it: a valid bundle prints its trust summary and exits 0; a malformed one exits non-zero.
Each receipt page repeats the exact command for its file and links the provenance commit, so you can trace the artifact back to the run that produced it.