Dependency graph
From a field record to a programme consequence
Each node is a record in the shared illustrative store, joined by ID. Open any node to see the register it lives in.
Story A — Arena MEP commissioning readiness
Illustrative demonstration chain.
- Field inspectionAsite FieldINS-ARENA-1181
MEP duct installation and damper witness
fail on 19 Sept 2026 · 14 photos · Arena bowl — level 02 east core
- Non-conformanceAsite FieldNCR-ARENA-087
Smoke damper installed to superseded revision C03
high severity · SAR 4.2m illustrative cost · 21 days impact · Demo MEP specialist D
- Controlled drawingAsite CDEDOC-ARENA-MEP-204
Arena bowl smoke control layout — level 02 rev C04
Supersedes revision C03, which was the revision witnessed on site.
- RFIAsite CDERFI-ARENA-442
Damper type confirmation at level 02 smoke zone boundary
overdue · raised 8 Sept 2026 · due 22 Sept 2026
- Commissioning systemAsite PMISCX-ARENA-1
Smoke control
1% ready · Open NCR-ARENA-087 — dampers installed to superseded revision; re-test required before integrated test.
- MilestoneAsite PMISMS-ARENA-03
Smoke control functional test
baseline 6 Nov 2026 → forecast 4 Dec 2026
- MilestoneAsite PMISMS-ARENA-04
Integrated systems test — arena bowl
baseline 10 Dec 2026 → forecast 14 Jan 2027
- Scenario readiness gateAsite PMISMS-ARENA-05
Scenario operational readiness gate
baseline 22 Jan 2027 → forecast 25 Feb 2027 — illustrative, not a committed opening date
What this chain is for
The point of the chain is traceability: a consequence at programme level can be walked back to the field record that created it, and the evidence for each step is held in the product that captured it. In this prototype the records are illustrative, but the structure is the one the Asite product set already captures.