DEMO LAB / EXECUTION MISSION CONTROL
One interval. Every handoff. Retained.
Twenty work requests arrive. Seven advance; thirteen wait. Run the synthetic interval, choose whether support joins, and compare the remaining work. Open the inspectors when you want the underlying record.
SYNTHETIC DATA · PUBLIC ABSTRACTION · NO ACTION TRANSMITTED
Follow one request through the system
Twenty synthetic obligations cross a read-only boundary. Source identity and timing stay attached.
READ-ONLY REQUESTS PHYSICAL EXECUTION RETAINED LINEAGE
Stage 1 of 5. Request observed. Twenty synthetic work objects enter with source identity retained.
Five synthetic minutes. One inspectable operational record.
Run the interval, approve synthetic support or continue observation, then compare the two paths. This scenario uses individual approval; the homepage shows automatic routing under standing hospital authorization. Both are demonstrations, with no real action transmitted.
Both choices share the same pre-gate interval. Run to T+03:15, then choose whether bounded support enters the synthetic record.
Inspect work items and switch lenses
Same demand. One decision. Two trajectories.
Both paths are held at the same simulated second. Clinical priorities remain unchanged.
Run to T+03:15. The comparison will then preserve both paths without requiring a second replay.
- 00:00NOMINAL
- 00:45FORMING
- 01:45RISING
- 02:45CONSTRAINED
- 03:15HUMAN AUTHORITY
- 03:15.2RECOVERING
- 05:00RETAINED
- 20 obligations normalizedSOURCE
- 7 advanced / 13 queuedQUEUE
- Execution state risingSTATE
Mission control loaded at a synthetic rising-state preview.
The interface demonstrates inspectability, explicit authority, and deterministic reconstruction. It does not expose production logic, validated thresholds, patient data, or connected clinical actions.
Request protected evaluation →The animation is not the evidence. The retained causality is.
One object across every lens.
WI-4102 remains identifiable from source event through queue, ownership, support posture, and retained record.
The system cannot approve itself.
This scenario uses individual approval. The decision and its scope remain visible; the homepage illustrates standing hospital authorization.
The same interval returns intact.
The sealed record can be scrubbed without changing its events, state transitions, or lineage fingerprint.
THE OPERATIONAL RECORD