CALLSHEET ZERO

SHOOT DAY 01 · UNIT A · REVISION CONTROL

VIEWING REVISION02

The day holds together.

Three agents propose. The Guard refuses. One scene moves.

VERIFIED SNAPSHOT · Captured run, 2026-09-05. Replay or inspect any step.

REV 01

COMMIT REFUSED

3 historical hard holds

Historical proposals
Captured run · 2026-09-05

Initial concurrent proposals
AgentSceneLocationTimeStatus

REV 02

COMMIT ALLOWED

0 final conflicts

Committed shared state
Captured run · 2026-09-05

Repaired shared schedule
AgentSceneLocationTimeStatus

repair.requested · Schedule Agent only

VERIFIED SNAPSHOT2026-09-05 · no new model call
Raw receipt

Proof of concurrency

Production incident

Weather hold. Cast delay.
Courtyard exterior lost. Lead actor +90 min. Cameras and transport remain shared.

The Guard prevents overlapping resource claims before a revision can commit.

Evidence, with context

Replay walks through captured live receipts. Run live starts a fresh model execution and may produce a different repair.

Adaption · learning receipt

Verified repair → preference data.
After a conflict-free revision commits, CALLSHEET ZERO can export that verified outcome to Adaption asynchronously.

Bounded proof

1 verified repair · preference_pairs.
A real bounded run succeeded and produced one chosen/rejected output row for future training or evaluation.

Truth boundary

Not in Run live.
The realtime Mozaik + Constraint Guard path stays independent. The deterministic Guard remains the safety authority.

Inspect Adaption evidence
Inspect runtime receipts UTC · original event order

COMMIT REFUSED is derived from hard conflicts. It is not an invented Mozaik event.