Skip to the content

Global Supply Chains

Reconstruct the network that actually exists.

Supply-chain intelligence rebuilt from observable structure and behaviour: the corporate, operating, economic and dependency system behind a company, and the changes moving through it.

The method is reverse engineering in its analytical sense — reconstructing how a system works from what can be examined, when its design and documentation are incomplete or unavailable.

Supply chain infrastructure

The principle

Reconstruct how a system actually works by examining its observable structure and behaviour, even when its original design, documentation or internal logic is unavailable.

A reconstruction is a probable model, not a recovered design. Every one of them therefore separates what was confirmed from what was inferred, and states what remains unknown.

  1. 01Reconstruct the system
  2. 02Understand the economics
  3. 03Map the dependencies
  4. 04Detect the changes
  5. 05Test the forecast
  6. 06Find the opportunity

The engines

One layer, six engines, shared by every domain.

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.

The application

Five models, one company, held together.

Supply-chain intelligence begins with supplier identification and does not end there. For a selected company the system reconstructs the operating logic of the network, then connects the five readings rather than filing them as separate reports.

01

Corporate structure

Model 01

Who actually owns and controls the operating system?

  • ·Parent and ultimate parent
  • ·Subsidiaries and affiliates
  • ·Business units
  • ·Documented ownership relationships

A corporate relationship map, with the ownership links the record establishes and the ones it implies kept apart.

Ownership that the disclosure does not reach is reported as not established, never filled from a filing's plausible reading.

02

Operating structure

Model 02

What physically happens, where, and through whose hands?

  • ·Facilities and their function
  • ·Products and production steps
  • ·Distribution arrangements
  • ·Transport and logistics providers

An operating and supply-chain map: the sequence from input to delivered output.

A facility that has been announced is not a facility that is running, and the map states which it is.

03

Economic structure

Model 03

What generates the revenue, and what does it cost to generate?

  • ·Revenue sources and segments
  • ·Disclosed costs
  • ·Capital investment
  • ·Contracts that carry the model

An economic reconstruction that connects the operating map to the money it produces.

An undisclosed margin is not estimated into the model. The gap is named.

04

Dependency structure

Model 04

What would have to fail for this to stop?

  • ·Critical suppliers
  • ·Concentration
  • ·Shared upstream dependencies
  • ·Alternative sources
  • ·Points of operational failure

A dependency and risk assessment, each exposure stated with what would confirm it.

An apparent alternative is flagged, not recommended: certification, specification, capacity and contractual eligibility decide whether it can actually substitute.

05

Change and opportunity structure

Model 05

What moved, who is affected, and what does it open?

  • ·Material developments
  • ·Affected suppliers and customers
  • ·Shifts in concentration
  • ·The decisions those shifts bear on

A chronological change history and the commercial questions it raises.

An acquisition is not automatically a risk. The record states what would have to be true for it to be material.

How the layers meet

A dependence is not complete until all three layers are read.

Take a manufacturer that depends on an external platform to coordinate procurement and movement. Any one layer understates the exposure; the reading is the three together.

01

Corporate layer

The platform provider and its corporate relationships: who owns it, who controls it, what it is part of.

02

Operational layer

The manufacturer's documented dependence on that platform for procurement and movement, and what fails with it.

03

Technical layer

Where sufficient evidence exists, the components behind the platform and the security issues recorded against them.

A recorded vulnerability is not a supply-chain disruption. The finding has to establish that the affected component is actually used, that the issue applies to this deployment, and what the operational consequence would be before any of the three layers is called exposed.

System Intelligence Representation

Two different objects, one way of stating them.

A shared representation, not one universal table. Different entity types carry different attributes and different validation rules; what is shared is that a finding from one engine can be read by another without being re-argued.

  • EntityManufacturerSoftware module
  • RelationshipPurchases components fromImports or depends on
  • InputRaw materialsFunction arguments or data
  • ProcessManufacturing operationProgram operation
  • OutputFinished productComputed result or service response
  • DependencyCritical supplierExternal library
  • ConditionProduction capacity constraintRuntime or configuration condition
  • EventSupplier acquisitionSoftware update
  • Failure scenarioComponent shortageComponent vulnerability or service failure
  • EvidenceFiling or contract recordDocumentation or authorized analysis result
  • ConfidenceStrength of documented relationshipStrength of technical finding

Verification

Six standings, and no seventh.

A finding is either verified, reported, inferred, estimated, a hypothesis, or unknown. There is no unclassified middle, because that is where a reconstruction quietly becomes an assertion.

Verified fact

01

Directly supported by reliable evidence.

The source says it, and the source is the record itself.

Reported claim

02

Attributed to a source, not independently verified.

Somebody asserted it. That is all that is established.

Strong inference

03

Supported by multiple consistent pieces of evidence.

No single document states it; the evidence converges on it.

Estimate

04

An approximation, numerical or qualitative, resting on stated assumptions.

Change an assumption, and it moves. The assumptions are printed with it.

Hypothesis

05

A plausible explanation requiring further evidence.

It could be true, and nothing yet distinguishes it from its rivals.

Unknown

06

Cannot currently be established from permitted evidence.

Stated as unknown. Never left blank, and never filled with a reading.

Recorded beside every material finding

  • ·Source reliability
  • ·Evidence freshness
  • ·Contradictory evidence
  • ·Assumptions used
  • ·Alternative explanations
  • ·Confidence rationale
  • ·The evidence that would confirm or disconfirm the finding

The boundary

Authorization comes before analysis.

Technical reconstruction is performed on systems the client owns or is authorized to examine, and only under the terms stated at engagement. The capability is defensive throughout: inventory, dependency, documentation, vulnerability correlation and architecture reconstruction.

Established before any analysis

  • OwnershipWhether the client owns the system or holds written authorization to analyze it.
  • ScopeWhich artifacts, environments and time periods are inside the engagement.
  • TechniqueWhich analysis methods are permitted, stated before any is used.
  • RestrictionLicensing, contractual, privacy and export limits that attach to the material.
  • ProtectionHow sensitive evidence and findings are held, and who may read them.
  • IsolationWhether the analysis must run in a separated environment.
  • RetentionHow long material and findings are kept, and in what form.

Outside the remit

  • No circumvention of licence terms or protective mechanisms.
  • No unauthorized access to any system or account.
  • No modification of a third party's software or records.
  • No analysis of an artifact on the assumption that public reachability implies permission.

What a reconstruction does not establish

  • ·A reconstruction is a probable model. It is not a recovered design.
  • ·A dependency is not a risk, and a vulnerability is not a disruption.
  • ·Two suppliers serving one buyer are not interchangeable until certification, specification, capacity and contract say they are.
  • ·A change that has not been observed is not a change that has not happened.
  • ·Nothing here states what will happen; it states what the structure makes possible.

Build sequence

Each phase has a test, not a date.

  1. Phase 1

    Foundation

    Evidence repository, entity resolution, versioned relationship graph, confidence framework.

    Test · A material corporate or supplier relationship can be traced to its evidence and read as it stood at each point in time.

    In place
  2. Phase 2

    Supply-Chain Reconstruction

    Corporate, operating, economic and dependency models, connected rather than filed separately.

    Test · A selected company's supply network can be reconstructed, its unresolved dependencies identified, and their commercial significance explained.

    In place
  3. Phase 3

    Historical Pattern Intelligence

    Event histories, change detection, scenario development, forecast evaluation against a defined baseline.

    Test · The indicators that preceded a documented event can be shown, and forecast performance reported rather than asserted.

    Developing
  4. Phase 4

    Software and Technical Intelligence

    Public dependency data, security-advisory correlation, authorized artifact analysis.

    Test · Relevant technical dependencies and documented risks are identified without overstating exploitability or operational significance.

    Commissioned
  5. Phase 5

    Commercial Intelligence

    Reconstructed systems connected to customer discovery, procurement opportunity and supplier alternatives.

    Test · A client can identify, prioritise and track a specific opportunity, and read back what came of it.

    Developing

Command Series SC

Reconstruction, commissioned.

A supply network rebuilt from observable evidence: its corporate, operating, economic and dependency structure, the changes moving through it, and the decisions those changes bear on.

A request raised against a command enters the commercial pipeline under its code. No request is an engagement, and no amount here is a guaranteed outcome.

CMD-SC01Strategic Diagnostic

Supply-Chain Structure Map

Examines
The named company's corporate and operating structure, from filings, disclosures and documented operating relationships.
Hands over
A relationship map separating confirmed ownership and supply links from inferred ones, with the evidence behind each.
CMD-SC02Strategic Diagnostic

Dependency & Concentration Assessment

Examines
What the operation relies on, where reliance concentrates, and which failures would travel.
Hands over
A dependency map with each exposure stated, the validation it needs, and the consequence where a substitute is absent.
CMD-SC03Strategic Diagnostic

Supplier Alternative Verification

Examines
An apparent alternative supplier against certification, specification, capacity and contractual eligibility.
Hands over
A substitution finding: what the alternative can actually carry, and what would have to be verified before it is used.
CMD-SC04Institutional Design

Operating & Economic Reconstruction

Examines
The full path from input to delivered output, and the economics that path produces.
Hands over
The five connected models — corporate, operating, economic, dependency, change — as one reconstruction rather than five reports.
CMD-SC05Sovereign Program

Supply-Chain Reconstruction Program

Examines
A portfolio of suppliers, facilities or counterparties, held and revised over the engagement.
Hands over
A standing reconstruction with change history, verification standing, unresolved questions and a commissioned opportunity register.
CMD-SC06Strategic Diagnostic

Software Dependency Assessment

Examines
Public dependency and package metadata, software bills of materials and advisory records for a system the client owns or is authorized to examine.
Hands over
A component and dependency finding correlated with advisory data, stating whether the affected version and configuration actually apply.
CMD-SC07Executive Retainer

Reconstruction Monitoring

Examines
A held reconstruction, re-read against new disclosures, filings, awards and advisories.
Hands over
Change notices as they become observable, each with the dependency affected and the question it raises.

$6,500/month

Request this work