Defense & Aerial SecurityLayer 02 · Defense Layer
Protective behaviour structured and authorised at the defense layer, with an accountability path into governance.
4 public profiles
Technology map
Where each part of the estate actually sits.
A structural view rather than a catalogue: which architectural layer each cluster operates at, how far each reaches across sectors, and where a relationship crosses a cluster boundary. Everything shown is read from the published portfolio, not maintained separately.
Position
Each cluster, and the layer it works at.
The estate is organised into clusters commercially and into layers architecturally. The two views describe the same technologies from different directions.
Sovereign AI InfrastructureLayer 05 · Operating Layer
Runtime authority and orchestration primitives, engaging the orchestration layer above it.
5 public profiles
Governance & ComplianceLayer 03 · Governance Layer
Obligation expressed technically, so that what a system did and under whose authority remains examinable.
4 public profiles
Human Capital & Value RightsLayer 06 · Identity and Control
Attribution and continuity of human-originated contribution across automated production.
3 public profiles
Communication SovereigntyLayer 03 · Governance Layer
Jurisdictional control over where processing and transit occur, governed at the same layer as policy.
1 public profile
Reach
How far each cluster extends.
Sectors are read from the sector attribution on each published profile. A sector appearing under more than one cluster indicates an architectural problem that recurs across the estate.
AerospaceAutomotiveCritical InfrastructureDefenseGovernmentMaritimeRail
Critical InfrastructureDefenseEnterpriseGovernmentLegal
Critical InfrastructureDefenseEnterpriseGovernmentRegulatorySocial Media Platforms
EducationEnterpriseFinancial SectorGovernmentLegal
EnterpriseGovernmentRegulatory
Structure
Where the clusters connect.
Published relationships whose two ends sit in different clusters. These are the points at which the estate holds together as one architecture rather than five separate groups.
CIV-ROS → CIVNETSovereign AI / Governance
BX-AI → SHAIVISovereign AI / Human Capital
CIVACE → GSMLACSGovernance / Sovereign AI
CIVNET → MLIGDPGovernance / Defense
SLCI → SPGICommunication / Governance
This map describes published architectural relationships only. It does not represent filing structure, family structure, or claim architecture, and no relationship shown here implies one. Publicly available patent records may be independently verified through USPTO systems where applicable. Information concerning non-public applications is provided through controlled verification procedures to qualified counterparties.
Architecture
Follow the structure down.
The architecture page describes each layer in its own terms; the portfolio catalogues every published profile.