REV 01
COMMIT REFUSED3 historical hard holds
Historical proposals
Captured run · 2026-09-05
| Agent | Scene | Location | Time | Status |
|---|
SHOOT DAY 01 · UNIT A · REVISION CONTROL
Three agents propose. The Guard refuses. One scene moves.
3 historical hard holds
Historical proposals
Captured run · 2026-09-05
| Agent | Scene | Location | Time | Status |
|---|
0 final conflicts
Committed shared state
Captured run · 2026-09-05
| Agent | Scene | Location | Time | Status |
|---|
repair.requested · Schedule Agent only
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.
Replay walks through captured live receipts. Run live starts a fresh model execution and may produce a different repair.
Verified repair → preference data.
After a conflict-free revision commits, CALLSHEET ZERO can export that verified outcome to Adaption asynchronously.
1 verified repair · preference_pairs.
A real bounded run succeeded and produced one chosen/rejected output row for future training or evaluation.
Not in Run live.
The realtime Mozaik + Constraint Guard path stays independent. The deterministic Guard remains the safety authority.
COMMIT REFUSED is derived from hard conflicts. It is not an invented Mozaik event.