This debut sequence uses only real ZDG runtime surfaces and real governed-run artifacts from the current proof bundle. The first frame establishes the proof surface. The next frames show BLOCK enforcement, PASS with replay-linked evidence, and CLI posture output without decorative or placeholder shots.
A four-frame proof story built from real ZDG runtime outputs: proof surface, BLOCK enforcement, PASS replay evidence, and CLI verification output.
Decision mix, replay linkage, and coverage are visible before any narrative.
Open with the public proof surface so the claim is immediately tied to the governed artifact and its replay-linked evidence.
The runtime path is allowed, but the release gate blocks and requires operator approval.
This is the enforcement moment: the system preserves the decision replay, trace, approval requirement, and evidence chain without relying on an internal backlog screen.
PASS keeps the run replayable: decision ID, trace ID, policy version, and evidence remain attached.
This frame shows that governance is not blanket friction. Safe work proceeds, but the proof spine remains inspectable.
Approval is not a side channel. It stays inside the governed chain.
This frame closes the WARN path with approved proceed and execution evidence in the same operator view.
The risky path stops at the gate pending operator intervention.
This is the hard-stop frame. It shows that the ZDG gate can deny release progression while still preserving the evidence spine.
Approval is part of the governed product surface, not an off-screen process.
This frame shows the accountable handoff. The release is still controlled, but the operator action is now visible and recorded.
Intent -> Approval -> Execution -> Evidence.
Close on the full chain. This is the frame that makes governed execution legible to operators, buyers, and owners in one glance.
ZDG turns governed execution into something operators, buyers, and owners can actually inspect. Not reconstruction. Not synthetic summary.