OMNIPHOENIX / PLANNING LAB
When one dependency slips, what follows?
Explore the original seven-job hyperstructure plan. Delay a job, block a dependency, and inspect the causal path before commissioning any work.
Durations begin after all dependencies finish. Resources are unlimited and parallel. Physical capacity and real-world impact are unknown. No providers, execution, transactions or settlement.
01 / Shape a disruption
Whole decimal digits only. Delays: 0–365000 days; horizon: 1–365000 days. Combined duration per job: at most 365000 days. Delay adds days to the job duration; blocking prevents that job and its descendants from finishing.
02 / Compare the dependency paths
Reward exposure is the exact sum assigned to blocked jobs and descendants. It is a planning total, never lost, earned, paid or recoverable money.
Causal trace, job by job
Arrows show dependency reachability from each disruption origin, not proof that every delay changes the finish date. Ties follow source order.
Source and report fingerprints
The source hash covers exact accepted UTF-8 bytes, including whitespace. The report hash covers canonical key-sorted report content. Checksums show consistency, not authenticity or authority.
03 / Inspect, import, recover
Everything is computed locally. Plan: at most 256 KiB and 100 jobs. Recovery: at most 4 MiB. Duplicate keys, BOM, malformed UTF-8 and altered recovery reports are rejected.