Salient Innovation Set · Sovereign Supply-Chain Assurance · FinTech Core

The Registrar & xBOM Portfolio

Continuous Supply-Chain Verification · “No xBOM, No Deploy” · Q4 2026 / 2027 Roadmap

Regulated firms can no longer defend production environments with static asset spreadsheets and retrospective incident hunts across disconnected tools. Backed by the Salient Innovation Set and the Salient FinTech Innovation Set at its core, the Registrar anchors Constitutional ServiceOps under a Sovereign Framework and Living Manifesto – binding every Hardware, Software, Model, and Data component into a cryptographically signed Bill of Materials (xBOM). By unifying DMTF CIM telemetry with Lawful Act Hyperedges (LAHEs) in KnowledgeHUB and backing sub-45µs hardware VETO rules (target state architecture – Q4 2026 / 2027 roadmap), cohorts gain Continuous Authority to Operate (cATO) while sequencing physical hardware rollouts to cohort phase readiness.

Registrar Icon
SBOM

Software Bill
of Materials

xBOM

Extended Bill
of Materials

cATO

Continuous Authority
to Operate

MVEB

Min. Viable
Evidence Bundle

Sovereign Framework · FinTech Trust Core

The Sovereign Foundation: Identity, Payment, Data & AI Sovereignty

The Registrar guarantees that sovereignty across every incoming Tenant Cohort is registered, mathematically grounded, and perpetually verifiable. Embedded in the Salient Innovation Set – anchored by the Salient FinTech Innovation Set at its core – the Registrar enforces a thoroughly architected near-term target state architecture where compliance is not an afterthought, but an immutable property of the runtime fabric (target state architecture – Q4 2026 / 2027 roadmap).

Pillar 01 · Trust

Identity Sovereignty

Decoupled from centralised identity brokers. High-assurance eIDAS 2.0 Qualified Trust Services, W3C Verifiable Credentials, and Zero-Data Vaults. Graph Topological Entanglement prevents Sybil manipulation without collecting or storing central PII.

Zero Centralised PII Exposure
Pillar 02 · Settlement

Payment Sovereignty

Direct Account-to-Account (A2A) rails (SEPA Instant, Faster Payments) bypass 1.5% to 3.5% card scheme interchange tolls. Bare-metal BIAN v14.0 execution and Token Gantry late-binding provide deterministic, sub-cent flat-fee clearing across all commercial interactions.

Zero Card Interchange Tolls
Pillar 03 · Privacy

Data Sovereignty

Constitutional Data Mesh with Law-Bound Data Products (LBDP). Cryptographic key-shredding (PAIF) reconciles GDPR Right to Erasure with immutable bitemporal audit ledgers, while hardware TEE Silicon Apartments guarantee strict tenant isolation.

Hardware TEE & PAIF Shredding
Pillar 04 · Governance

AI Sovereignty

Authority-poor autonomous agents constrained by formal Deontic Dominance (\(\mathbf{F} \succ \mathbf{O} \succ \mathbf{P}\)). Monotonic delegation axioms prevent authority creep, single-use OBO warrants eliminate escalation, and Computable Blame enforces legal liability.

Bounded Action Space & OBO Tokens
Operational Runtime · Continuous Assurance

The Registrar xBOM & Constitutional ServiceOps: Replacing Reactive "Trust Theater" with In-Kernel Verification

Conventional service operations collapse into "Trust Theater" – relying on out-of-sync CMDBs, manual change tickets, and post-incident reviews that expose enterprise balance sheets to catastrophic compliance failures. The Constitutional ServiceOps Architecture transforms the Registrar into an active in-kernel operational engine. Distributed Management Task Force (DMTF) Common Information Model (CIM) definitions are mapped directly onto polyadic Lawful Act Hyperedges (LAHEs) inside KnowledgeHUB – elevating infrastructure nodes, AI models, and software packages into active graph entities governed by constitutional axioms.

Under the invariant "No xBOM, No Deploy," the Registrar unifies Hardware (HBOM), Software (SBOM), Model (AI/ML-BOM), and Data (DBOM) into a single composite Product Bill of Materials (PBOM). Every service modification, agent deployment, or policy patch must present a cryptographically verified Minimum Viable Evidence Bundle (MVEB) before receiving Continuous Authority to Operate (cATO). When an agent initiates an operational command, eBPF/XDP hooks on SmartNIC DPUs intercept the packet in under 8.2 microseconds. If the command violates a Prohibition (\(\mathbf{F}\)) under the Deontic Dominance Hierarchy (\(\mathbf{F} \succ \mathbf{O} \succ \mathbf{P}\)), hardware logic executes an instantaneous VETO dropping the packet in under 45 microseconds (target metric – Q4 2026 / 2027 roadmap).

Polyadic LAHEs

Dynamic CIM Mapping

Static CIM schema classes are converted into live Lawful Act Hyperedges binding infrastructure elements to active constitutional rules.

Continuous cATO

No xBOM, No Deploy

Continuous Authority to Operate gates every execution thread. Unregistered code, modified weights, or ungrounded data are structurally blocked.

<8.2μs Kernel Hook

eBPF / XDP Interception

Operational intents are intercepted directly at the network layer on SmartNIC DPUs, eliminating operating system context switching.

Sub-45μs VETO

Hardware VETO Override

Structural VETO drops non-compliant packets in under 45 microseconds upon Prohibition detection via software eBPF today, advancing to existing 3rd-party xPUs in Mid 2027 earliest, FPGA test runs in Early 2028, and First ASIC silicon Late 2028 to Mid 2029 earliest (target metric – phased hardware roadmap).

Governed Assurance: DMTF CIM · KnowledgeHUB LAHEs · Continuous Authority to Operate (cATO) Explore xBOM Marketplace
Under the Hood

How Identity Works on the Platform

For those who want to understand the architecture: oneWallet.online sits at the intersection of two distinct but connected identity models, governed by the Registrar & Notary.

Legal Party Identity

Humans & Organisations

Humans and organisations have legal personhood – the recognised capacity to enter legal agreements, bear rights, and face obligations. They are registered as first-class parties by the Registrar & Notary (a Meta-QTSP or Federation of cross-jurisdictional QTSPs) through high-assurance document verification and eIDAS 2.0 PID issuance.

Their oneWallet is the command centre for this legal identity – managing their agreement portfolio, consent records, and the AI agents and devices they own and authorise.

Agent Proxy Identity (NHI)

AI Agents & Devices

AI Agents and autonomous devices have no legal personhood. They operate as delegated proxies on behalf of legal parties in Agreement DAGs – machine-executable digital twins of legal agreements – with authority delegated through OBO (On-Behalf-Of) Tokens. Each token defines the proxy's Role, Authorisation, Policy, and Rules.

Liability rests entirely with the legal principal (the human or organisation) who issued the OBO Token. An agent can never exceed the authority of the principal who created it. DRAGON enforces this at the hardware level – no configuration required.

Feature Legal Party (Human / Org) Agent Proxy (AI / Device)
LiabilityBorne directly by the partyAlways rests with the legal principal

Registrar: Architecting Next-Generation Agentic Supply Chain Assurance (SSCA) and Cyber Supply Chain Risk Management (C-SCRM)

Critical Insight: In the Agentic Age, traditional software security frameworks collapse because autonomous AI agents formulate and execute commands at machine speed at the intent layer, rendering standard perimeter firewalls and post-hoc logging obsolete. The Registrar addresses this foundational flaw by moving from probabilistic "Assumed Trust" to deterministic "Substantiated Integrity". By expanding standard Software (SBOM) and Hardware (HBOM) metrics to incorporate Model (AI/ML-BOM) and Data (DBOM) architectures, the system locks law into silicon, ensuring that unauthorised or non-compliant actions are physically uncomputable and topologically unreachable.

1. The Imperative of Comprehensive SSCA & C-SCRM

The global digital economy operates on a dangerous paradox. High-velocity autonomous machine execution at the edge demands instant, unconstrained agency, yet modern compliance paradigms rely on "Assumed Trust" – manual audits, reactive patch cycles, and static documentation filed away in compliance portals. This legacy approach results in staggering inefficiencies, draining up to 35% of IT budgets on redundant ETL reconciliation and forcing engineering teams to waste significant resources on manual audit archaeology.

In the shifting landscape of Software Supply Chain Assurance (SSCA) and Cyber Supply Chain Risk Management (C-SCRM), the introduction of Horizon 2 Agentic AI causes this legacy framework to break down. When an autonomous agent hallucinates, suffers prompt injection, or drifts from its regulatory mandate, the failure occurs at the intent layer. To traditional security systems, the resulting traffic looks authenticated, valid, and encrypted.

To protect enterprise balance sheets from unbounded algorithmic liability, security architecture must shift from "Trust, then Verify" to "Verify, then Execute". This requires verifying not just the identity of an actor, but the genetic integrity of the entire digital artifact through a unified, recursive manifest managed by a definitive state engine: the Registrar.

End-to-End Supply Chain Assurance & Risk Management Map

SSCA & C-SCRM Architecture Specification

Registrar Supply Chain Assurance Map

Hardware & Firmware Attestation

Firmware attestation quotes from edge hardware, 3D IC chiplets, and POI appliances (HBOM) are verified via silicon root-of-trust and Measured Boot before execution leasing.

Models & Software Lineage

Software dependencies (SBOM) and dynamic neural weight adapters (AI/ML-BOM) are bound to explicit Control Flow Graphs and cryptographically signed Policy Hashes.

KeyMESH & Data Products

Law-Bound Data Products (DBOM) and Multi-Tenant Cryptographic Key Management (KeyMESH) enforce automated Remote Key Loading and continuous key rotation across edge clouds.

2. Productising Data and Models: The Canonical Nine-Category xBOM Portfolio

To resolve the governance gap in autonomous agentic commerce, the platform elevates legacy software inventory into a multi-dimensional, cryptographically sealed architecture. Aligned rigorously with OWASP CycloneDX, the Registrar operates a locked nine-category Bill of Materials portfolio – fusing silicon roots (HBOM), executable binaries (SBOM), SaaS dependencies (SaaSBOM), cryptographic primitives (CBOM), manufacturing and container formulations (MBOM), runtime environments (OBOM), neural model weights (AI/ML-BOM), and data products (DBOM) into an overarching Product Bill of Materials (PBOM). By design, no tenth category may ever be introduced or inferred.

Figure 1.1: Unified Product Bill of Materials (PBOM) Architecture 9-xBOM Locked Architecture
Figure 1.1: Unified Product Bill of Materials (PBOM) Architecture orchestrating all nine Bills of Materials: PBOM root, Registrar Quintet (HBOM, SBOM, AI/ML-BOM, DBOM), and foundational CycloneDX capabilities (CBOM, MBOM, OBOM, SaaSBOM)
Figure 1.1 – Unified PBOM architecture orchestrating all nine Bills of Materials: the Product composition root (PBOM), the core Registrar Quintet (HBOM, SBOM, AI/ML-BOM, DBOM), and foundational CycloneDX capabilities (CBOM, MBOM, OBOM, SaaSBOM).

The Model Bill of Materials (AI/ML-BOM)

The AI/ML-BOM tracks and verifies the lineage, architecture, parameters, and tuning adapters (e.g., LoRA, PEFT) of AI and Machine Learning models. It mathematically tracks neural weights, preventing the "Clean Mind, Dirty Intent" vulnerability where an uncompromised model structure is subtly poisoned or manipulated into generating toxic outputs. The Registrar cryptographically binds these weights to a specific Policy Hash (PH) at execution time.

The Data Bill of Materials (DBOM)

The DBOM elevates passive datasets into managed, productised, and self-describing Law-Bound Data Products (LBDPs). Stored within the Registrar, a DBOM captures complete data lineage and provenance, cryptographic schema definition, transformation logic, EU LAU-1 or NUTS jurisdictional tags, and dynamic user consent status. This structure ensures data injected is legally admissible for that exact operational context.

Authoritative Registrar Standard · OWASP CycloneDX Locked Taxonomy

The Canonical Nine-Category xBOM Portfolio

7 CycloneDX Core + 2 onePOI Extensions

The onePOI.online Registrar operates on a strictly locked, nine-category Bill of Materials taxonomy aligned with OWASP CycloneDX. In order to preserve unbroken cryptographic traceability across distributed tenant execution, exactly nine categories are recognised – no tenth category may ever be introduced or inferred. Deployment and container formulations are governed under the Manufacturing Bill of Materials (MBOM), while runtime variables reside inside the Operations Bill of Materials (OBOM).

SBOM CycloneDX #1
Software Bill of Materials

Component inventory, open-source libraries, transitive dependencies, licence chains, and SAST vulnerability tracking. No software artifact deploys without formal bisimulation verification.

Scope: Binaries, bytecode & packages
SaaSBOM CycloneDX #2
SaaS Bill of Materials

SaaS service endpoints, hosted API integrations, external cloud dependencies, and third-party operational service level commitments tracked under zero-trust bounds.

Scope: Cloud endpoints & hosted APIs
HBOM CycloneDX #3
Hardware Bill of Materials

Physical silicon roots, DRAGON ASIC stepping, PUF keys, TEE enclaves, TPM 2.0 chips, and SmartNIC DPUs. Verifies hardware attestation signatures (HAS) to preclude anti-rollback attacks.

Scope: Silicon roots, PUFs & enclaves
AI/ML-BOM CycloneDX #4
AI / Machine Learning BOM

Neural architectures, weights, LoRA adapters, hyperparameter configs, and ModelOps telemetry. Deterministically versions model states to eliminate hallucination drift and poison attacks.

Scope: Neural weights & ModelOps
CBOM CycloneDX #5
Cryptography Bill of Materials

Cryptographic algorithms, key lengths, certificates, zero-knowledge proof circuits, TR-31 key blocks, and post-quantum readiness (NIST FIPS 203 ML-KEM and FIPS 204 ML-DSA).

Scope: Ciphers, ZKPs & PQC readiness
MBOM CycloneDX #6
Manufacturing & Build BOM

Software build, container packaging, Helm formulation, and deployment formulation pipelines. Strictly denotes manufacturing formulation, disambiguated from AI/ML models.

Scope: Build pipeline & deployment manifests
OBOM CycloneDX #7
Operations Bill of Materials

Operational runtime configurations, host kernel tuning, environmental parameters, active service mesh routes, and live infrastructure orchestration constraints.

Scope: Live runtime environment & topology
PBOM onePOI Extension #1
Product Bill of Materials

Master product composition, tenant packaging, commercialisation parameters, composite capability bundles, and complete governed product lifecycle from admission to decommission.

Scope: Sovereign tenant product composition
DBOM onePOI Extension #2
Data Bill of Materials

Law-Bound Data Products (LBDPs), cryptographic schema proofs, transformation DAGs, GDPR/FiDA residency tags, and dynamic user consent states bound to the DToP.

Scope: Data products, lineage & consent
Strict Taxonomy Lock & Zero Tenth Categories: Constructs such as standalone deployment BOM, Infrastructure BOM, or Release BOM are strictly barred across the architecture. Deployment manifests and packaging pipelines are canonically governed within MBOM, while runtime parameters are attested within OBOM. The forthcoming official OWASP CycloneDX 2.x specification serves as the sole external review trigger.

3. The Recursive xBOM Topology

The cornerstone of next-generation agentic assurance is the structural flexibility of the Extended Bill of Materials (xBOM) graph. Rather than acting as flat, isolated lists, xBOMs utilise a nested, recursive topology where one Bill of Materials can contain, reference, or wrap another.

Cross-BOM Compliance Coupling Matrix

Structural Interdependency · Automated Invalidation Cascades

Unlike static enterprise registries where inventories remain decoupled, the Registrar enforces Cross-BOM Compliance Coupling. Invariants across BOM layers are cryptographically bound together inside the Control Flow Knowledge Graph (CFKG). A mutation or breach in one layer immediately triggers automated, deterministic cascades across dependent systems:

Rule 1: Data → Model DBOM → AI/ML-BOM
Lineage Expiration Invalidates AI Warrant

If training dataset consent expires, a GDPR right-to-be-forgotten request is registered, or synthetic data licensing drifts in the DBOM, the Registrar instantly revokes the runtime warrant of every dependent AI/ML model. Execution terminates without requiring manual operator intervention.

Rule 2: Software → Admission SBOM → Capability
Bytecode Drift Triggers Re-Admission

Any microcode stepping change, container base-image modification, or package dependency patch demotes the active capability from Certified to Provisioned. Automated formal verification proofs must re-evaluate bisimulation against Agreement DAGs before line-rate cATO is restored.

Rule 3: Silicon → Financial Rails HBOM → FinTech Rails
Attestation Breach Halts Settlements

If DRAGON ASIC hardware attestation fails, PUF signatures diverge, or chassis tampering is detected, SmartNIC eBPF filters sever network connectivity at wire speed. The node is barred from accessing BIAN banking services, SEPA Instant rails, or oneWallet settlement gantries.

Formal Admission Substrate · CANON REG-REGISTRAR-001

The Capability Manifest & Attestation Lifecycle

Within onePOI.online, capabilities are never admitted into production as loose code, unvetted binaries, or unanchored containers. Every capability must present a cryptographically sealed Capability Manifest spanning five discrete dimensions, advancing through a four-stage formal state machine before earning line-rate operational authority:

Dimension 1
Multi-Tier Lineage

Cryptographic binding of all nine xBOM components: PBOM, SBOM, HBOM, AI/ML-BOM, DBOM, CBOM, MBOM, OBOM, and SaaSBOM hashes.

Dimension 2
Agreement DAGs

Formally verified Ricardian contracts, deontic logic constraints ($F \succ O \succ P$), and statutory regulatory bindings compiled by the PIME.

Dimension 3
Interface Contracts

Typed category-theoretic morphisms, BIAN v14.0 Service Domain semantic models, and strict ISO 20022 message schemas.

Dimension 4
Operational Owners

Sovereign tenant DID identity, designated TopHAT human supervisor authorities, and contractual Service Level Objectives (SLOs).

Dimension 5
MVEB Obligations

Minimum Viable Evidence Bundles proving bisimulation, automated audit compliance, and non-repudiable transaction replayability.

The Four-Stage Attestation State Machine

Deterministic Authority Transitions Under SMT Verification

1. Provisioned
Artifact Staged in CDE
→ FVE SMT Proof →
2. Attested
Bisimulation & Signatures Valid
→ HAS Silicon Heartbeat →
3. Certified
cATO Active · Line-Rate Warrant
→ Invariant Breach →
4. Revoked / Quarantined
Zero-Day Blackhole (<100ms)
Admission Calculus: Formal Bisimulation

Before advancing from Provisioned to Attested, the Formal Verification Engine (FVE) executes symbolic execution runs in Z3/CVC5. It establishes mathematical bisimulation (1:1 semantic isomorphism) between the executable bytecode and the compiled Ricardian Agreement DAG, guaranteeing zero undocumented code execution.

Wire-Speed Revocation Calculus

If runtime telemetry detects illegal control flow, expired user consent, or PUF heartbeat failure, the Registrar demotes the capability to Revoked / Quarantined. Targeted revocation payloads propagate across the eBPF data plane, dropping ingress packets and blackholing endpoints in a target metric of under 100 milliseconds (target state architecture – Q4 2026 / 2027 roadmap).

Total System of Record (SoR) Governance Domain

The Six Governed Lifecycles

The Registrar is the universal governor of state across the platform. Rather than limiting governance to software deployments or IT asset inventories, the Registrar manages six continuous, interlocked operational lifecycles:

1. Party Lifecycle

Authoritative onboarding, identity binding, credential issuance, and offboarding for all ecosystem entities: human citizens, tenant enterprises, AI autonomous agents, and physical edge appliances.

2. Agreement Lifecycle

Negotiation, multi-party cryptographic co-signing, PIME compilation into deontic Agreement DAGs, runtime execution monitoring, dispute resolution, and formal novation or termination.

3. Product Lifecycle

Tenant capability packaging, PBOM composition, pricing tier compilation, market listing in the sovereign cohort ecosystem, version deprecation, and sunsetting.

4. Tenant Lifecycle

Prospective cohort discovery, sovereign CDE workspace provisioning, dedicated TEE "silicon apartment" isolation, delegated administrator onboarding, and tenancy revocation.

5. xBOM Lifecycle

Continuous ingestion, topological linking, cross-BOM coupling validation, vulnerability enrichment (VEX/VDR), and immutability anchoring into the bitemporal hypergraph ledger.

6. Service Lifecycle

Qualification against SLA/SLO baselines, issuance of time-bounded runtime warrants ($W_{run}$), live telemetry tracing, auto-remediation, and wire-speed quarantine upon drift.

Architectural Disambiguation: Official EUDI Registrar vs. onePOI xBOM Registrar

ARF 1.4 Regulatory Standard Alignment · Invariant Separation

In European and global digital identity literature, the term Registrar often refers to the statutory public registry maintaining Trusted Lists of Qualified Trust Service Providers (QTSPs) and Electronic Attestation of Attributes (EAA) providers under eIDAS 2.0 / ARF 1.4. Within the Salient Innovation Set, the onePOI Registrar serves a distinct, complementary, and internal architectural mandate: it is the bitemporal trust and composition registry that enforces xBOM provenance, capability manifests, and hardware-rooted attestation across tenant execution threads. When an external citizen or institutional wallet presents an eIDAS verifiable credential, the onePOI Registrar ingests and verifies the credential against the official EUDI trust list, thereafter binding the attested claims into the sovereign Party Knowledge Graph (Party_KG) and Digital Twin of the Person (DToP) for line-rate execution.

4. Driving ServiceOps, AI, and Data Governance in the Agentic Age

This recursive xBOM topology enables a highly resilient, automated operational paradigm for enterprise ServiceOps, AI, and Data governance.

Category Theory & Jurisdictions

By leveraging category theory, every Packaged Business Capability (PBC) is modelled as an exclusive authority boundary mapped directly onto the platform’s multi-layered legal constitution – the Axiom MESH. Each PBC maps one-to-one to a canonical BIAN service domain and serves as the single-writer owner of that domain's data state. AI agents are admitted temporarily, rendering shadow IT or privilege escalation structurally impossible.

Separation of Powers

To prevent generative models from corrupting executable business logic, the Constitutional Operating System (COS) enforces a strict structural separation of powers:

  1. The Legislature (TopHAT): Establishes the core non-negotiable legal prose and symbolic axioms.
  2. The Judiciary (DRAGON Engine): Adjudicates every proposed machine intent using Triadic Adjudication in constant time ($O(1)$).
  3. The Executive (System of Orchestration): Translates approved intents into actual workflows via Actuator DAGs.

Zero-Privilege Interns

AI agents are treated as "Zero-Privilege Interns." They are intelligence-rich but authority-poor; they can construct a complex "DAG-of-Thought" but possess zero direct execution privileges. To interact with a data product or move capital, the agent must be granted a short-lived, single-purpose On-Behalf-Of (OBO) Token that cryptographically projects the authority of a verified human Principal.

Governance Layer Legacy AI & Data Management (Probabilistic) Registrar-Anchored Framework (Deterministic)
Verification GatePost-hoc manual sampling and log analysisPre-execution Runtime Attestation ($O(1)$ constant time)
AI Control ModeUnbounded model behaviour, reactive guardrailsNeuro-Symbolic Caging via explicit Agreement DAGs
Data Privacy (GDPR)Manual, lengthy data integration and pruning pipelinesUnder 2-minute automated erasure via Law-Bound Data Products
Risk ContainmentLateral exploitation and unbounded organisational liability"TEE Hardware-Isolated Enclaves" hardware isolation and structural VETOs

The Ultimate Assurance: Lawful Act Hyperedges (LAHE)

Every successfully adjudicated transaction or data access is recorded as a Lawful Act Hyperedge (LAHE) on a graph-native, Bi-Temporal Ledger. By tracking both Valid Time (the real-world activation of a policy) and Transaction Time (the nanosecond of recording), the platform unlocks Perfect Historical Replay. This creates an unalterable, court-defensible "receipt of reasoning" that explicitly distinguishes between an operational execution breach and a law design failure, converting compliance from a resource-draining regulatory liability into a high-yield capital asset.

Architectural Blueprint

The Dawn of Agentic ServiceOps

Modern digital enterprises suffer from an operational and regulatory governance deficit. By moving from probabilistic "Assumed Trust" to deterministic "Substantiated Integrity," the onePOI.online Constitutional Operating System (COS) translates multi-tenant natural language intents and relational agreements into deterministic, silicon-enforced execution states.

1 Core Architectural Integration: Registrar & KnowledgeHUB

The relationship between the Registrar and the KnowledgeHUB serves as the ultimate core foundation for the platform's System of Record (SoR) and its property of Substantiated Integrity.

Figure 1.2: Registrar & KnowledgeHUB Architectural Integration 9-xBOM Bitemporal Pipeline
Figure 1.2: Registrar & KnowledgeHUB Architectural Integration: Formal admission control, bitemporal hypergraph core, and dynamic 9-xBOM topology compilation
Figure 1.2 – Registrar admission control enforcing Capability Manifests and bitemporal proofs ($T_{\text{valid}} \le T_{\text{transaction}}$) with the KnowledgeHUB core, generating the complete nine-category xBOM graph topology.

1.1 Gatekeeper of Origin

The Registrar acts as the definitive trusted enrollment, admission control, and verification authority. It unifies ITAM, CMDB, and ModelOps into an axiom-governed single source of truth. No workload, human principal, device, or AI agent can exist unless explicitly registered, cryptographically signed, and continuously tracked.

1.2 Multi-Dimensional xBOMs

Every asset is decomposed into a composite Extended Bill of Materials (xBOM) topology: HBOM (physical silicon root-of-trust), SBOM (code dependencies & CVE state), AI/ML-BOM (model neural weights & tuning adapters), and DBOM (Law-Bound Data Product manifests & consent parameters).

1.3 Bi-Temporal Core

KnowledgeHUB materializes xBOM assets as a federated Data Mesh aligned with BIAN v13 and FIBO ontologies, implementing Bi-Temporal Fidelity across Valid Time ($V_t$: physical policy activation) and Transaction Time ($T_t$: nanosecond ledger recording).

2 Control Flow Knowledge Graphs (CFKG) & The Inspector

The dynamic interplay between static system topology and runtime intent is mapped by the Inspector via wire-speed Control Flow Knowledge Graphs (CFKGs).

Figure 2.1: Control Flow Knowledge Graph (CFKG) & Inspector Flight Pipeline SMT Solver & DRAGON ASIC
Control Flow Knowledge Graph and Inspector Flight Pipeline: Proposed Intent Vector through Syntactic Edge Scrub, CFKG, and LSRG Matrix
Figure 2.1 – Inspector engine flight compiling runtime intent into CFKG and LSRG matrices for DRAGON hardware execution (Target metric: sub-45μs hardware adjudication – Q4 2026 / 2027 roadmap).

2.1 Syntactic Scrubber

Intercepts infrastructure payloads and execution calls at wire-speed, verifying code modifications, regex formats, and data serialization payloads against DBOM/SBOM schemas before host kernel resources are exposed.

2.2 CFKG Construction

Merges xBOM states with Agreement DAGs under Deontic Logic operators: Permissions ($\mathbf{P}$), Obligations ($\mathbf{O}$), and Prohibitions ($\mathbf{F}$).

2.3 SMT Solver & DRAGON ASIC

Evaluates logical paths using SMT solver loops. Applying canonical dominance ($\mathbf{F} \succ \mathbf{O} \succ \mathbf{P}$), it compiles valid pathways into a Legal-State Reachability Graph (LSRG) loaded onto DRAGON ASIC static RAM for $O(1)$ hardware execution at line rate – achieving a target metric of sub-45μs triadic adjudication (target state architecture – Q4 2026 / 2027 roadmap).

3 Bitemporal Hypergraph & B-HGNN Neural Learning

Transactions persist as Lawful Act Hyperedges (LAHEs) in a global hypergraph ledger (Bitemporal Ledger). Bitemporal Hypergraph Neural Networks (B-HGNNs) run continuous Graph Data Science over the living ledger, evaluating causal graph learning and generating real-time predictive assurance vectors to detect systemic anomalies before execution.

4 Multi-Cloud Service Mesh & eBPF Kernels

Utilises a sidecarless Constitutional Service Mesh (CSM) driven by Cilium and eBPF. Network sockets pass via non-blocking ring buffers directly into Wasm sandboxes. Decouples security via SPIFFE/SPIRE workload identities and Lawful Warrants, while supporting Constitutional Island Mode for offline edge survival.

5 Next-Gen ServiceOps: Phygital Arbitrage & Zombie Agent Extermination

Phygital Service Arbitrage

Competitive tenant cohorts securely share multi-edge physical infrastructure. Micro-royalties and assurance fees are captured natively at execution via Lawful Act Hyperedges, dividing rewards between host, anchor, and legal engineers.

Neuro-Symbolic Shadow DAGs

System of Intelligence executes probabilistic planning via Supervisory Shadow DAGs, simulating proposed strategy changes against historical bitemporal hypergraph paths prior to real-world deployment.

Exterminating Zombie Agents

Short-lived OBO Tokens project human authority. When regulatory policies update, TopHAT pushes prohibition updates ($\mathbf{F}$). Because $\mathbf{F} \succ \mathbf{P}$, orphan "Zombie Agents" are instantly and structurally nullified at the eBPF kernel layer without code retraining.

Operational Objective / Metric Legacy ServiceOps Frameworks onePOI.online COS Integrated Architecture
Asset Identity & LineageDisconnected CMDB assets, fragmented code registries, unmonitored container blobs.Unified xBOM Framework (HBOM, SBOM, AI/ML-BOM, DBOM) continuously verified by the Registrar.
Audit & Forensic VerificationTime-consuming linear loops ($O(N)$) parsing mutable text log files to piece together past breaches.Constant-Time ($O(1)$) automated legal queries utilising non-repudiable Evidence Envelopes.
Network Interception ModelResource-heavy sidecar proxies running in user-space, injecting severe processing latency.Sidecarless kernel-level interception via eBPF handing traffic context over to Wasm sandboxes.
Autonomous AI GovernanceUnchecked API access tokens allowing probabilistic engines to execute unsafe ledger steps.Strict Separation of Law and Logic enforced via deterministic DRAGON ASICs and short-lived OBO Tokens.

Before any entity can participate in the ecosystem – whether a user wallet, any agent, or any device – it must be registered with a full provenance record.

PBOM

Product Bill of Materials

The overarching composition root of the Registrar Quintet. Aggregates hardware, software, AI models, and data products into a unified, commercialised tenant offering with full bitemporal lifecycle governance.

HBOM

Hardware Bill of Materials

Complete provenance of every physical component – silicon roots to edge appliances. TEE attestation certificates, firmware stepping hashes, and DRAGON PUF signatures guarantee hardware-level execution integrity.

SBOM

Software Bill of Materials

Full dependency graph, CVE mappings, licence chains, and formal bisimulation proofs. No software component deploys without an immutable SBOM entry verified by the Constitutional Foundry.

AI/ML-BOM

AI / ML Model Bill of Materials

Full AI model lineage – neural architecture, training datasets (via DBOM links), bias evaluations, LoRA adapter weights, and decision attribution records. Precludes semantic variance and prompt poisoning.

DBOM

Data Bill of Materials

Origin, classification, consent basis, transformation history, retention policy, and sovereignty jurisdiction of every Law-Bound Data Product. GDPR and FiDA residency compliance is structural.

xBOM+

Auxiliary CycloneDX Suite

Completing the 9-category taxonomy with CBOM (cryptography & PQC), MBOM (build & deployment formulation), OBOM (runtime environment), and SaaSBOM (hosted APIs).

All records anchored to the System of Record

All xBOM records are stored immutably in the System of Record's bitemporal ledger. Every update creates a new LAHE record. Together with the active Policy Hash and execution hardware signatures, these constitute a Minimum Viable Evidence Bundle (MVEB) – providing a deterministic audit trail that allows regulators to verify and replay the exact runtime state of any capability deployed.

Registrar & xBOMs

Every Capability Has a Birth Certificate

The Registrar is engaged as part of the onboarding sprint – scoping your SBOM requirements, mapping your xBOM architecture, and establishing the cATO pipeline that keeps your deployments continuously authorised.

Technical Specification & Formal Proofs

Registrar Provenance & Bitemporal Integrity

Explores SBOM/HBOM/AI/ML-BOM integrity checks, cryptographic heartbeats, and bitemporal historical audit trails.

The Ultimate Inventory for Complete System Trust

The Registrar acts as the system's official record keeper. It tracks the exact origin, version, and identity of every piece of hardware, software, and AI model in the network. By verifying that every part has a valid digital certificate before it runs, the Registrar keeps hackers from introducing unauthorised code or using compromised equipment. Note: the system guarantees execution of the programmed rules as written, but does not judge whether the rules themselves are good – that remains a human responsibility.

xBOM Supply Chain Provenance & Continuous Authority to Operate

The Registrar maintains complete supply chain assurance by enforcing an extended Bill of Materials (xBOM) registry tracking Software (SBOM), Hardware (HBOM), Model (AI/ML-BOM), and Data (DBOM) dependencies. To satisfy DORA's cyber-resilience guidelines, the Registrar compiles legislative intents and policies into a flattened Legal-State Reachability Graph (LSRG). The root of this graph is minted as a Policy Hash and cached directly on the DRAGON DCPU's hardware registers, enabling silicon-level enforcement where non-compliant states are physically uncomputable. Any firmware or configuration drift immediately invalidates the node's credentials.

Compliance Frameworks

Native compliance logic alignment mapping to PSD3, eIDAS 2.0, and DORA resilience guidelines.

Commercial Pooled ROI

Shared physical infrastructure distribution model reducing CapEx overhead by up to 80%.

Architectural Integration (Symphony of Systems)

The xBOM Registrar serves as the definitive, bitemporal authority of the System of Record (SoR) layer. It integrates directly with the System of Agreement (SoA) and System of Orchestration (SoO) by compiling legislative policy into a flattened Legal-State Reachability Graph (LSRG). This graph is hashed into a single Policy Hash, which is cached directly on the DRAGON DCPU's hardware registers. SVID identity leases generated from hardware quotes are verified against this Policy Hash in real-time, ensuring that any unauthorised code execution or hardware drift triggers an immediate, hardware-enforced Structural VETO.

xBOM Registries & Cryptographic Heartbeats
Unified xBOM Verification

Every node continuously validates its Software Bill (SBOM), Hardware Bill (HBOM), Model Bill (AI/ML-BOM), and Data Bill (DBOM) dependencies. A break in any link of this chain (e.g., swapping a RAM module or altering driver firmware without an authorised change order) triggers an immediate Structural VETO.

Measured Boot & Root of Trust

Boot sequence begins with the Core Root of Trust for Measurement (CRTM) etched in silicon ROM, extending hashes of BIOS, bootloader, kernel, and firmware into TPM Platform Configuration Registers (PCRs) via $PCR_{new} = \text{Hash}(PCR_{old} \mathbin{\Vert} \text{Hash}(new\_code))$, generating a signed Attestation Quote.

Continuous Attestation (cATO)

cATO heartbeats are submitted at randomised 30 – 120s intervals. Using privileged eBPF memory probes, they measure runtime memory pages, kernel page tables, and Control Flow Graphs (CFG). Any TOCTOU exploitation immediately invalidates the node's SPIFFE/SPIRE SVID cryptographic identity lease.

The Zero-Day Revocation Graph

Upon discovering a vulnerability (e.g., zero-day library exploit), the Registrar queries its highly connected xBOM graph to identify all running instances containing the library. It pushes a targeted revocation payload globally, blackholing and isolating affected nodes in under 100ms.

Bitemporal Monotonicity & SMT Solver Proofs

The system proves that historical records are immutable and cannot be rewritten by verifying bitemporal monotonic invariants.

Bitemporal Monotonicity Theorem

$$T_{valid} \le T_{transaction}$$

Asserting that Valid-Time ($T_{valid}$) must always be less than or equal to Transaction-Time ($T_{transaction}$) to prevent future-dated or historical tampering.

SMT Solver (Z3) Constraints

The Registrar database driver enforces bitemporal writing safety at the transaction boundary:

(declare-const t_valid Int)
(declare-const t_transaction Int)
(declare-const write_legal Bool)
; Bitemporal Monotonicity Invariant: Valid-Time must never exceed Transaction-Time
(assert (= write_legal (<= t_valid t_transaction)))
; Test if a future-dated write (where valid-time exceeds transaction-time) is permitted
(assert (and write_legal (> t_valid t_transaction)))
(check-sat)
; Expected result: unsat