Full-body translation draft; independent semantic review is pending. This is not proof of a public release or a completed live run.
Original cartoon replay · eight scenes
Evidence is not a subtitle,it decides how the story ends.
Turn Goal, Source Binding, Finder, Verifier, Ledger, Review, Action and Reconciliation into a cartoon film you can pause, rewind and give an alternative ending.This is not an agent saying it is done: it shows how completion is proved.
ORIGINAL CAST · SIX ROLESEach character represents a governance responsibility that another character cannot replace.
01
Evidence Replay Cinema
Eight scenes: from intent to provable completion
Press play to advance automatically, or inspect each scene on the timeline. The cards on the right connect the images to records, bindings and derived state. The final scene offers two endings: complete evidence or provider outcome unknown.
THE PROOF BEFORE THE ENDAn interactive short film about evidence, state and reconciliation
SANITIZED TEACHING REPLAY · NOT A LIVE RUN
Scene 01 / 08CONTRACT BOUND
Captain RootGOAL KEEPER
First, put the intended outcome on film
Without a frozen goal, scope and acceptance criteria, there is no ending that can be replayed.
00:00 / 01:04
Choose the provider state in the final sceneRevalidatable inputs determine the ending; narrators do not vote on it.
The full eight-scene transcript and an alternative ending
Read every scene's dialogue, governance explanation and complete demo records without enabling JavaScript. Playback changes presentation only, never a real run.
These are sanitized teaching records. The cards cover evidence, ledger entries, findings and action state; they do not pretend that every record is the same kind of evidence.
01 · First, put the intended outcome on film
Captain Root · GOAL KEEPER
Without a frozen goal, scope and acceptance criteria, there is no ending that can be replayed.
TaskContract v2 freezes the goal, scope, acceptance, authority and stages; a free-text claim of completion does not change state.
run.created → pending
task-contractcomplete
The goal, scope and acceptance criteria are frozen
04 · A Verifier looks for the frame nobody wants to see
Vera · INDEPENDENT VERIFIER
Keep both supporting and counter-evidence; a finder cannot stamp approval on its own finding.
This scene is explicitly marked as the review-kernel-v2-pilot observe-only branch: Verifier and finder are separate; conflicting results become INCONCLUSIVE, and missing or ambiguous anchors remain blocking. It ends before action and does not claim extra finder/verifier authority for executable workflows.
claim checked → finding open
claim-verificationcomplete
An independent verifier rechecks the claim and exact anchor
id
demo-verify-21
binding
reviewer · work unit · quote
digest
sha256:demo-1c90…
findingopen
Counter-evidence shows a mismatched source fingerprint
{
"demo": true,
"authoritative": false,
"presentationOnly": true,
"recordedOutcome": null,
"ending": "verified",
"scene": "06",
"derivedState": "finding resolved → broad review complete",
"records": [
{
"kind": "review-package",
"id": "demo-package-31",
"status": "complete",
"summary": "Base, head, scope and diff manifest are frozen",
"binding": "package digest · sentinel",
"digest": "sha256:demo-9bd2…"
},
{
"kind": "finding",
"id": "demo-finding-P1",
"status": "complete",
"summary": "The same stable finding is resolved with evidence",
"binding": "repair attempt · package digest",
"digest": "finding:demo-P1"
},
{
"kind": "final-broad-review",
"id": "demo-review-32",
"status": "complete",
"summary": "The complete changed surface is reviewed again after local repair",
"binding": "current head · current sentinel",
"digest": "sha256:demo-b204…"
}
]
}
07 · Keep the bridge raised: bind permission to this attempt
Sentinel · SIDE-EFFECT GATE
The action token binds action, provider, resource, revision, review, evidence and the idempotency key.
This is a sanitized teaching replay and issues no real token. Executable workflows must still request actions under their own review contract, source freshness, provider binding and protected authorization. After wrapper invocation, a nonzero exit with an unknown outcome is not automatically a safe failure.
The receipt does not match yet; keep the vault closed
Sending is neither proof of success nor proof of failure. Check the actual provider state first; never blindly resend an unknown outcome.
An unknown attempt requires query reconciliation through the pinned provider. Without fresh absence proof or a successful receipt, there is no completed ending.
provider outcome unknown → indeterminate
action-attemptindeterminate
The wrapper may have sent the request, but its terminal outcome is unknown
{
"demo": true,
"authoritative": false,
"presentationOnly": true,
"recordedOutcome": null,
"ending": "unknown",
"scene": "08",
"derivedState": "provider outcome unknown → indeterminate",
"records": [
{
"kind": "action-attempt",
"id": "demo-attempt-41",
"status": "indeterminate",
"summary": "The wrapper may have sent the request, but its terminal outcome is unknown",
"binding": "same attempt · same execution",
"digest": "attempt:demo-0041"
},
{
"kind": "completion-decision",
"id": "demo-completion-52",
"status": "open",
"summary": "An unknown side-effect outcome blocks completion",
"binding": "provider receipt missing",
"digest": "decision:not-issued"
}
]
}
01 · RECOMPUTERecompute the decision
Derive state again from the contract, events, evidence and receipts.
02 · DO NOT RESENDDo not repeat side effects
Provider reconciliation checks what already happened; it does not send the request again.
03 · FAIL CLOSEDStop when the outcome is unknown
A missing receipt, binding drift or unresolved P0/P1 cannot be edited into a completed ending.
02
Character Atlas
Six cartoon characters, six distinct responsibilities
Select a character to visit its representative scene. A Finder cannot verify its own finding; Ledger derives state only from events; Sentinel does not grant passage because the picture looks good; Echo investigates unknown outcomes without blindly resending.
The film is presentation; code and contracts are authoritative
Every scene points back to existing contracts and implementation in the repository. This page does not create runs, issue action tokens or treat generated illustrations as policy inputs.
Boundary:This page is a sanitized, deterministic teaching replay. Its images and demo JSON cannot authorize push, merge, deploy or any external side effect. Graphs, animation and narration cannot replace typed evidence and provider receipts for the current revision.
