Defence supply-chain exposure
Which programmes break when gallium does?
01 · Platform
Start with the programme.
Which platforms are in scope?
02 · System
Open the system.
Subsystems and assemblies, each one a stored row.
03 · Assembly
Follow it down to the board.
Every hop keeps its source version.
04 · Component
To a single part.
Where the dependency stops being abstract.
05 · Material
To the material inside it.
Gallium. Germanium. The element, not the vendor.
06 · Source
To where it comes from.
Then back up, with a named owner for the next check.
Illustrative imagery · synthetic chain
A dependency is a reason to investigate, not a prediction of failure.
Every claim traces to a stored row. Every gap stays visible. Every next check gets a named owner.
Try a guided investigationEarlier proof cases
Replays on authored timelines. Demonstrations, not predictive validation.
illustrative replay
A66 Brough–Bowes
Stainmore
ITV reported the snow closure. Rewind modeled signals up to the hatch — hindsight stays out of the draft.
Enter →
seeded flood replay
Eden Valley flood
Appleby · Osmotherley
Illustrative gauge-like signals, a warning, and route disruption on an authored timeline. Not live monitoring or proof of flood prevention.
Enter →
operator view
Lake District
Borrowdale · Wasdale · Coniston
The shift tool — same room, today's clock. Open after you sign the A66, or from the desk.
Enter →