The layer does not replace the supply-chain, financial or corporate functions. It is the method they use, so a finding produced for one can be read by another without being re-argued.
Engine A
Artifact and Evidence Analysis
What can lawfully be examined, and what does each item carry with it?
Filings, disclosed financial statements, procurement notices and awards, corporate and technical documentation, public repositories and package metadata, software bills of materials, advisories, and — where supplied under authorization — artifacts and configuration records.
Produces · An evidence repository in which every material conclusion has a traceable source.
Each item keeps its source, acquisition date, publication date, the period it speaks to, and its permitted-use conditions. An item without those is not evidence.
Engine B
Structural Reconstruction
What are the components, and how do they relate?
Companies, subsidiaries, facilities, suppliers, customers, contracts and business functions; or modules, libraries, interfaces, dependencies, runtimes and documented interactions.
Produces · A structured model of components and relationships.
A confirmed relationship and an inferred one are held apart on the model, never merged into one line.
Engine C
Behaviour and Workflow Reconstruction
How does the system appear to operate, as distinct from how it says it does?
The documented and observed path between procurement, production, movement, distribution and revenue; or the observed inputs, outputs, execution traces and interface behaviour of a technical system.
Produces · A behaviour model with its supporting evidence, its open questions and its confidence.
Documentation is a claim about behaviour, not a description of it. Where the two differ, both are held and the difference is reported.
Engine D
Dependency and Failure Analysis
What does the system rely on, and how would a failure travel?
A single critical component supplier; several suppliers sharing one upstream producer; a dependence on one logistics provider or one external service; an outdated or vulnerable library; an operation with no documented alternative.
Produces · A dependency map, the failure paths it implies, and the validation each path needs.
A dependency is not a risk. It becomes one only when the evidence shows the exposure, the absence of a substitute, and the consequence.
Engine E
Change Detection
What has changed since the last reconstruction, and when did it become observable?
Acquisitions and divestitures, supplier substitutions, facility closures, shifts in financial condition, dependency updates, newly disclosed vulnerabilities, changed interfaces, altered operational behaviour.
Produces · A time-stamped record of the change, the moment it became observable, and why it may matter.
Versions are preserved, never overwritten. A reconstruction that silently replaces its predecessor loses the only evidence of what moved.
Engine F
Analytical Reconstruction and Explanation
Can the model be explained to someone who has to decide something?
Which components were identified; how they interact; which relationships are verified and which inferred; what evidence supports the model; what uncertainty remains; what further evidence would improve it.
Produces · An explainable system model the other engines can use.
An explanation that cannot name its own uncertainties is a narrative, and is not accepted as a reconstruction.