Scrutica
Where Cobham sits in the compute supply chain — geographic revenue split, segment mix, capex / FCF / buyback history, and industry placement — sourced from licensed-database extracts and SEC EDGAR, joined to the supply-chain graph through the industry classification.
No licensed-database enrichment loaded for this entity — geographic revenue, segments, capital allocation, and industry classification are absent. Coverage rules in the methodology.
Each hop carries its data source, source URL (where one exists), as-of date, and confidence label on the same line as the parent name. When two sources name different parents for the same hop, both sit on the page as alternates — the walker does not pick a winner.
Starting entity — the walker climbs from here, following documented parent / subsidiary edges in the ownership substrate.
Chain-of-title terminates at Cobham. No further parent is documented — for a public filer that means UBO is the dispersed float; for a state-linked entity it means the chain has reached the sovereign apex.
Documented M&A-shaped events touching this entity (Buyout, Corporate Divestiture, Asset Sale, Joint Venture, Spin-off). Capital raises without an ownership transfer are filtered out upstream — they don’t move the chain.
The substrates above join to the platform's analytical surfaces. Each link carries Cobham's own numbers into the tool that acts on them.
1 upstream · 0 downstream. The cascade simulator walks a seed disruption outward across the graph, weighted by the curator's substitutability assessment.
Facilities, sovereign-AI programs, export-control posture, and the announced-versus-deployed reality gap for the country.
Side-by-side facilities, GPU inventory, power, revenue, capex, and market cap.