The Company Wide Dependency Map
The brain grows upward from reliable programme execution.
An approved programme becomes a control system when its activities are translated into owned, cross-functional work and daily execution signals. That execution spine connects planning to procurement, people, evidence, cash, contracts and owner decisions.
Tier 0 · execution spine
Tier 1 · signal layer
Tier 2 · operations
Tier 3 · money and law
Tier 4 · owner layer
Fault line
Inputs: Issue Register V1.0 · 28-Jul-2026 meeting · Governance Brain discussion · Execution Framework requirements guide · Owner Cockpit. Blueprint = operating architecture · Build Roadmap = rollout sequence.
Tier 0–1 drill-down · Execution Framework
The programme execution engine
One execution graph keeps the contractual promise intact outside and makes the work controllable inside. The Execution Framework performs the quiet architecture between the two.
CPM · outward contractual face
Execution Framework · translation and governance
CCPM and TOC · inward control face
Secondary view · commercial build sequence
Build the brain in the order that value compounds.
Run the programme first. The same execution facts then support certification and collection, preserve contractual rights and give the owner a portfolio control view.
Click a rollout tier
The build sequence
Each layer delivers value on its own; none needs a parallel data universe.
Foundation · one execution graph · evidence provenance · controlled CPM sync
Follow one piece of work
From the approved programme to collected cash
Click a step to see the proof carried forward.