From Passive Repositories to the Active Cryptographic "Music Stand"
In traditional enterprise IT and legacy DevSecOps environments, an artifact repository (such as Docker Hub, Artifactory, or a CMDB) is fundamentally a passive storage silo. It holds compiled binaries, container images, and software dependency manifests, but it lacks any semantic understanding of the legal constraints, operational mandates, or physical hardware roots-of-trust governing those artifacts.
Within the Salient Innovation Set, the Registrar is profoundly elevated from a passive file drive into an active, adjudicating state engine. Residing in the System of Record (SoR), it serves as the authoritative, bi-temporal "Music Stand" from which the Conductor (SoO) reads its execution directives and DRAGON (SoA) verifies constitutional compliance. It establishes the non-negotiable rule of digital physics: "No xBOM, No Deploy".
Fragmented ITAM, CMDB & Probabilistic SBOMs
Legacy systems split hardware inventory (ITAM), service configurations (CMDB), and software manifests (SBOM) across disconnected databases. When an AI agent executes or a zero-day exploit emerges, reconciling provenance takes days of forensic guesswork across unverified logs.
Unified xBOMs & Silicon-Anchored Provenance
The Registrar mathematically binds Hardware (HBOM), Software (SBOM), Model (AI/ML-BOM), and Data (DBOM) into a single composite Product Bill of Materials (PBOM). Every component is cryptographically signed, bitemporally indexed, and continuous authority to operate (cATO) is validated in real time.
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).
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.
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.
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.
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.
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).
Dynamic CIM Mapping
Static CIM schema classes are converted into live Lawful Act Hyperedges binding infrastructure elements to active constitutional rules.
No xBOM, No Deploy
Continuous Authority to Operate gates every execution thread. Unregistered code, modified weights, or ungrounded data are structurally blocked.
eBPF / XDP Interception
Operational intents are intercepted directly at the network layer on SmartNIC DPUs, eliminating operating system context switching.
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).
The Telemetry & Forensic Quad: From Static Inventory to Living Immune System
In the onePOI architecture, the Registrar does not merely catalogue software packages; it operates as the Genetic Ledger at the apex of the four-tier continuous governance quad. It manages the complete bitemporal lifecycle of all platform components across the locked 9-Category OWASP CycloneDX 2.0 xBOM taxonomy (Hardware HBOM, Software SBOM, Cloud Services SaaSBOM, Cryptography CBOM, Operations OBOM, Vulnerabilities VDR/VEX, AI Model AI/ML-BOM, Policy PBOM, and Data DBOM). Every entity is cryptographically anchored to a bitemporal Policy Hash (\(\mathcal{PH}\)), providing the root coordinates for continuous runtime verification.
The Genetic Code
Authoritative source of truth minting bitemporal product nodes across all 9 CycloneDX classes, establishing unbroken provenance from factory silicon to runtime execution.
Semantic Memory
Houses multi-domain ontologies cross-mapping BIAN v14.0 banking services and ISO 20022 schemas with MITRE ATT&CK, ATLAS, D3FEND, and MAESTRO 7-layer threat graphs.
Sensory Telemetry
High-velocity event processing point ingesting deep Linux kernel LSM syscalls (Cilium Tetragon), network packet streams (Cilium Hubble), and OpenID SSF signals.
Forensic Analytics
Executes Bitemporal Hypergraph Neural Network (BHNN) traversals across the live Control Flow Knowledge Graph (CFKG) to evaluate transitive risk and issue Cognitive Pre-VETOs.
The 5x5 Symmetric Architecture: Symphony ↔ Registrar xBOM Quintet
1:1 Mathematical Symmetry Between Runtime Execution Engines and Static CycloneDX 2.0 Configuration Baselines
Engagement & Silicon
Binds physical edge terminals, sensors, and human-machine interfaces directly to Hardware Bill of Materials (HBOM) silicon roots of trust and chassis tamper seals.
Agreement & Code
Maps compiled Agreement DAGs and deontic smart contracts to Software Bill of Materials (SBOM) binary hashes and verified inter-procedural callstacks.
Record & Lineage
Anchors bitemporal ledger states and transactional records in the Data Bill of Materials (DBOM), verifying streaming data contracts and vector embeddings.
Intelligence & Models
Couples JEPA world models and Liquid Edge LLMs to the AI/ML-BOM, attesting tensor weight hashes, training provenance, and hyperparameter bounds.
Trust & Cryptography
Unites TopHAT judicial oversight and hardware line-cuts with the Cryptography Bill of Materials (CBOM), enforcing post-quantum (ML-KEM / ML-DSA) key agility.
Registrar Runtime Manifest
SoR // BITEMPORAL PROVENANCE ENGINE
Continuous Assurance, Zero-Day Amputation & Regulatory Moats
For Chief Information Officers, Chief Risk Officers, and Enterprise Architects, the Registrar converts regulatory compliance from a costly retrospective audit exercise into an automated, real-time commercial moat. By formalising every asset's lineage into the constitutional substrate, organisations achieve mathematically provable governance.
Automated DORA & NIS2 Mapping
Instantly delivers dynamic, real-time topological mappings of financial ICT supply chains as mandated by DORA Articles 5 to 16, replacing multi-month manual audit engagements with wire-speed cryptographic proof.
Sub-400μs Zero-Day Amputation (target metric – Q4 2026 / 2027 roadmap)
When an upstream library or model weights corruption is identified, the Registrar computes the non-transitive dependency closure, instantaneously revoking execution authority across the fleet without service restart.
Basel IV Capital Optimisation
Deterministic component provenance and unalterable execution logs satisfy Tier 1 institutional requirements, unlocking verifiable operational risk mitigation and reducing regulatory capital reserve requirements.
Continuous Authority to Operate (cATO)
Transitions cyber security from annual compliance snapshots to continuous real-time attestations. Runtime memory hashes are verified against registered golden manifests with every single execution heartbeat.
The Four-Dimensional xBOM Topology
Traditional software manifests only look at application dependencies. The Registrar introduces a comprehensive four-dimensional ontology uniting Hardware, Software, AI Models, and Data into a unified Product Bill of Materials (PBOM).
HBOM · Hardware Bill of Materials
Captures physical device provenance down to microarchitectural serials, security chiplets (TPM 2.0, Apple T2, AWS Nitro enclaves, NXP SE050), and Platform Configuration Registers (PCRs). The HBOM validates that host silicon has executed an uncompromised measured boot sequence before accepting tenant workloads.
SBOM · Software Bill of Materials
Maintains full recursive directed acyclic graphs (DAGs) of all compiled binaries, container layers, and eBPF kernel probes. Builds are bit-for-bit reproducible, toolchain-attested, and signed. Any unauthorised dynamic linking or runtime binary injection violates the SBOM signature and triggers instant process quarantine.
AI/ML-BOM · Model Bill of Materials
Establishes unalterable provenance for autonomous agent weights, quantization schemes (FP8, INT4), fine-tuning checkpoints, and RLHF alignment boundaries. The AI/ML-BOM enforces mathematical bounds on cognitive drift ($\Delta \text{CD} \le 0.05$), ensuring neural agents cannot hallucinate outside their lawful parameter space.
DBOM · Data Bill of Materials
Guarantees the integrity, lineage, and sovereign jurisdiction of all data products entering the mesh. The DBOM tags datasets with cryptographic Policy Hash Roots (%PHR), privacy assertions (GDPR, EU Data Act, CCPA), and schema contracts, enabling zero-copy sharing under strict deontic law.
Bi-Temporal Ledgers, "Heartbeats of Integrity" & The Revocation Graph
How the Registrar turns static inventory declarations into high-frequency, tamper-proof execution guarantees across the distributed runtime mesh.
Dual-Axis Bi-Temporal Ledger
The Registrar tracks two independent time dimensions for every registered asset: Transaction Time (when a state fact was recorded) and Valid Time (when that fact was legally true in the real world). This enables historical time-travel audits and retroactive legal corrections without rewriting history.
Heartbeats of Integrity (cATO)
Continuous authority to operate (cATO) is enforced via periodic cryptographic heartbeats. Every executing container, model runtime, and eBPF hook regularly publishes its live memory digest to the Registrar. If any runtime drift occurs, authority collapses within milliseconds.
The Non-Transitive Revocation Graph
When an upstream component is flagged as compromised, the Registrar executes a wire-speed revocation traversal. By walking the dependency DAG, it revokes only the affected capability branches while preserving healthy, uncompromised tenant pipelines.
The Trust Engine for BIAN Standards & Real-Time Financial Rails
The overarching framework is the Salient Innovation Set, and at its foundational core lies the Salient FinTech Innovation Set. Every phygital, civic, healthcare, retail, or agentic transaction ultimately resolves into a lawful value exchange, identity binding, or fiduciary settlement. The Registrar provides the non-negotiable trust engine and cryptographic ledger that makes this sovereign ecosystem viable for all incoming Tenant Cohorts.
BIAN Service Domain Alignment
Direct semantic integration with Banking Industry Architecture Network (BIAN) service domains: Clearing, Settlement, Position Keeping, Payment Execution, and Token Gantry value custody.
Real-Time A2A & SEPA Instant Rails
High-frequency account-to-account (A2A) settlement with sub-second finality. The Registrar validates counterparty capability tokens and cryptographic keys prior to value transfer execution.
Token Gantry & Fiduciary Isolation
Binds cryptographic tokens to verified xBOM manifests, ensuring assets transferred across tenant boundaries carry unalterable audit trails and mathematical non-repudiation proofs.
Dynamic Carbon Accounting & The Runtime Carbon VETO
Sustainability is not an afterthought in the Salient Innovation Set; it is hard-coded into the xBOM topology. The Registrar continuously couples computational resource consumption with certified ESG metrics, delivering real-time carbon governance for enterprise workloads.
Embodied & Operational Carbon Indexing
HBOM manifests capture the embodied carbon of silicon fabrication and chassis assembly, while SBOM and AI/ML-BOM manifests record active runtime compute watt-hours and cooling overheads across cloud and edge nodes.
The Runtime Carbon VETO
If regional electrical grid carbon intensity ($g\text{CO}_2e/\text{kWh}$) surges above policy thresholds, the Registrar triggers a constitutional Carbon VETO – automatically rescheduling non-urgent batch AI training or data re-indexing to periods of peak renewable generation.
Summary Matrix: Legacy Registries vs. The Sovereign Registrar
How the Sovereign Registrar fundamentally transforms enterprise trust, asset lifecycle control, and regulatory compliance.
| Dimension | Legacy Registries (Docker Hub, CMDB, Git) | The Sovereign Registrar (Constitutional OS) |
|---|---|---|
| Primary Role | Passive file storage for compiled code & packages | Active bi-temporal "Music Stand" for the Symphony of Systems |
| Asset Scope | Software packages or isolated CMDB hardware records | Unified 4D xBOM (HBOM + SBOM + AI/ML-BOM + DBOM = PBOM) |
| Temporal Indexing | Single timestamp (created/updated date) | Bi-Temporal B-Tree (Transaction Time ⊗ Valid Time) |
| Attestation Model | Point-in-time annual audit checklists & manual scans | Continuous Authority to Operate (cATO) with live memory heartbeats |
| Revocation Speed | Manual incident triage & redeployment (hours to days) | Sub-400μs Zero-Day Amputation via dependency graph traversal (target metric – Q4 2026 / 2027 roadmap) |
| Regulatory Assurance | Subjective self-attestation & sample reporting | Deterministic compliance (DORA, NIS2, EU AI Act, Basel IV) |
Cryptographic Attestation Chains & Bi-Temporal Science
Deep Technical: Measured Boot Cryptographic Chains & PCR Registers
Silicon attestation sequence, TPM 2.0 extensions, and CRTM verification
Deep Technical: Measured Boot Cryptographic Chains & PCR Registers
Silicon attestation sequence, TPM 2.0 extensions, and CRTM verification
The measured boot sequence anchors software state into immutable silicon registers. When a host node powers on, the Core Root of Trust for Measurement (CRTM) computes a cryptographic hash of the UEFI firmware before executing it. Each subsequent stage measures the next layer into the Platform Configuration Registers (PCR):
The Registrar verifies the attestation quote against registered golden manifests stored in the HBOM before enrolling the node into the live tenant execution cluster.
Deep Science: Bi-Temporal Interval Algebra & Graph Revocation Complexity
Allen's interval algebra, bitemporal index structures, and sub-millisecond graph closures
Deep Science: Bi-Temporal Interval Algebra & Graph Revocation Complexity
Allen's interval algebra, bitemporal index structures, and sub-millisecond graph closures
Bi-temporal indexing models state transitions as 2D orthogonal rectangles across Transaction Time $[t_{tx\_s}, t_{tx\_e})$ and Valid Time $[t_{val\_s}, t_{val\_e})$. Querying the exact legal status of any component at historical transaction coordinate $T_{tx}$ for valid business date $T_{val}$ is executed via spatial R-Tree index bounds:
This mathematical model guarantees that retroactive compliance revisions (e.g., discovering a counterfeit component months after deployment) preserve complete immutable forensic auditability without corrupting active real-time operations.
Cryptographic Policy Hash Roots & Silicon Provenance Proofs
Policy Hash Root (%PHR) derivation, immutable bitemporal proofs, and silicon-anchored measured boot architectures have been fully codified in the Salient Innovation Set Deep Tech Series.
From the Operational Quintet ($\mathcal{Q}_5$) to the Complete 9-Category CycloneDX + onePOI xBOM Taxonomy ($\mathcal{R}_9$)
In accordance with the authoritative Registrar xBOM Taxonomy Lock, Registrar (elem-comp-registrar) governs the complete, non-extensible Nine-Category xBOM Allowlist ($\mathcal{R}_9$): the Seven Canonical OWASP CycloneDX BOM Capabilities (SBOM, SaaSBOM, HBOM, AI/ML-BOM, CBOM, MBOM, and OBOM) united with the Two Sovereign onePOI Constitutional Extensions (PBOM and DBOM). The 5-tuple Operational Quintet ($\mathcal{Q}_5 = \{\text{SBOM}, \text{HBOM}, \text{AI/ML-BOM}, \text{DBOM}, \text{PBOM}\}$) evaluated at wire speed by Posture 360 is proved in the STRM Crosswalk to be a strict mathematical subset ($\mathcal{Q}_5 \subset \mathcal{R}_9$, $|\mathcal{Q}_5 \cap \mathcal{R}_9| = 5$, $|\mathcal{R}_9 \setminus \mathcal{Q}_5| = 4$) of the full 9-category Registrar state vector.
| # | xBOM Category | Authority & Origin | Constitutional Scope & Cryptographic Binding | STRM Partition |
|---|---|---|---|---|
| 01 | SBOM (Software BOM) | OWASP CycloneDX | WASM modules, container layers, dependency trees, and NIST SP 800-218 SSDF provenance hashes. | Q_5 ∩ R_9 |
| 02 | SaaSBOM (SaaS BOM) | OWASP CycloneDX | External cloud services, third-party API endpoints, data-flow topology, and DORA Art. 28 ICT third-party concentration register. | R_9 \ Q_5 |
| 03 | HBOM (Hardware BOM) | OWASP CycloneDX | POI Appliance silicon steppings, UCIe 2.0 chiplets, TPM 2.0 / Pluto roots of trust, and firmware digests. | Q_5 ∩ R_9 |
| 04 | AI/ML-BOM (ModelOps BOM) | OWASP CycloneDX | Model weights, hyperparameters, LoRA adapters, training corpus lineage, and EU AI Act Art. 11/12 model cards. | Q_5 ∩ R_9 |
| 05 | CBOM (Cryptography BOM) | OWASP CycloneDX | Post-quantum algorithms (ML-KEM-1024, ML-DSA-87), key lengths, TLS cipher suites, and FIPS 140-3 Level 4 quantum-readiness posture. | R_9 \ Q_5 |
| 06 | MBOM (Manufacturing & Formulation BOM) | OWASP CycloneDX | Reproducible compiler flags, Tekton/Cosign build pipelines, enclave attestation recipes, and deployment formulation provenance. | R_9 \ Q_5 |
| 07 | OBOM (Operations BOM) | OWASP CycloneDX | Live runtime configurations, eBPF/LSM policy hashes, environment variables, and active service-mesh posture. | R_9 \ Q_5 |
| 08 | PBOM (Policy & Deontic BOM) | onePOI Extension | Compiled Agreement DAGs, Deontic Quivers ($\mathcal{F} \succ \mathcal{O} \succ \mathcal{P}$), Z3/Lean 4 proofs, and STRM Axis 3 Regulatory Residue bindings. | Q_5 ∩ R_9 |
| 09 | DBOM (Data Lineage BOM) | onePOI Extension | Bitemporal ($T_v \otimes T_t$) dataset provenance, GDPR Art. 9 consent receipts, Soil-to-Gut telemetry, and clinical cold-chain hashes. | Q_5 ∩ R_9 |
AI/ML-BOM vs CycloneDX MBOM vs Physical Manufacturing BOM
Registrar enforces strict ontological disambiguation across three frequently conflated terms: (1) AI/ML-BOM governs neural weights, training datasets, and ModelOps lineage; (2) CycloneDX MBOM governs software build formulation, compiler reproducibility, and deployment pipeline recipes (absorbing all deployment formulation metadata without ever introducing an unauthorised tenth category); and (3) Physical Manufacturing BOM remains protected domain terminology for physical industrial and EPC material assemblies.
STRM × LACE Cross-Sector Anchor (SEAM-01, SEAM-04 & SEAM-07)
The 9-Category xBOM Allowlist is constitutionally locked across the architecture until the formal ratification of OWASP CycloneDX 2.0, which serves as the sole architectural review trigger. Across cross-sector deployments, Registrar (SUPERSET_OF LACE Service 1) powers AGR ⟷ FSI Green Sukuk xBOM Securitisation (SEAM-2026-10-22-04) and NGO ⟷ PSL S05 Triadic Custody Separation (SEAM-2026-10-22-07) alongside Notary and KeyMESH.
Sliced-Coordinate (SCoO) 512-Bit Bitmask Compilation, 4D Root Hash Anchoring & Dynamic Auto-VEX Streaming
To evaluate the Locked 9-Category OWASP CycloneDX + onePOI xBOM Ecosystem ($\mathcal{R}_9$) at line rate without graph pointer-chasing stalls, Registrar (elem-comp-registrar, Ranked #8 Infomap Gatekeeper bridging 11 communities) compiles hierarchical CycloneDX / ECMA-424 dependency graphs into dense hardware bitmasks.
Single-Cycle Bitwise Set Intersections
Processed by the Policy Integration & Mapping Engine (PIME) and validated in Z3 SMT, all 9 xBOM topologies flatten into 512-bit Sliced-Coordinate (SCoO) sparse bitmask matrices that load directly into 512-bit vector registers on the DRAGON ASIC for single-cycle AND, OR, and XNOR set evaluations.
Hierarchical 9-xBOM Sub-Tree Binding
Global platform identity anchors on the 4D Cryptographic Root Hash: $$\mathcal{PH} = \text{Hash}(\mathbf{HBOM} \parallel \mathbf{SBOM} \parallel \mathbf{AI/ML\text{-}BOM} \parallel \mathbf{DBOM})$$ while the remaining five dimensions (SaaSBOM, CBOM, OBOM, MBOM, and PBOM) attach as cryptographically bound Merkle sub-trees via RFC-8141 BOM-Link URNs.
Reachability Tensor Suppression R(p) = 0
When a component reports a CVE exposure whose call path is structurally unreachable inside the compiled Control Flow Knowledge Graph (CFKG), Registrar asserts a mathematical non-reachability proof ($R(p) = 0$), emitting a signed Auto-VEX record and streaming live NIST OSCAL System Security Plans (SSPs) to regulators.
Every transaction sealed by Registrar links its 9-Category xBOM Policy Hash ($\mathcal{PH}$) to a $<2.5\text{ KB}$ Minimum Viable Evidence Bundle (MVEB), enabling independent auditors to replay historical supply-chain and policy compliance offline without accessing raw tenant logs.
Ex-Ante Hardware Interdiction (< 20 ns XDP_DROP), 8-into-1 Composite PBOM Passports, & Opaque Frontier AI Quarantine Enclaves
To satisfy EU AI Act Article 10 (Data Governance), Article 11 / Annex IV (Technical Documentation), and EN 18286:2026 Clause 7 & Clause 8, the Registrar enforces the physical invariant of “No xBOM, No Deploy”. Before any software container, microservice, or neural weight tensor is permitted to populate execution memory, the platform verifies a boot-time hardware fingerprint and compiles all eight upstream OWASP CycloneDX 2.0 manifests (SBOM, HBOM, AI/ML-BOM, CBOM, OBOM, SaaSBOM, MBOM, and DBOM) into the master 8-into-1 Composite Product Bill of Materials (PBOM):
Boot Fingerprinting & Sanction Interdiction
If an un-attested binary, unauthorised firmware stepping, or hardware component originating from a sanctioned entity (NDAA / UFLPA) is detected, Registrar immediately revokes the node’s Attestable Trust Envelope. The SmartNIC DPU and DRAGON engine assert a non-maskable < 20 ns XDP_DROP Hardware Line-Cut VETO and zeroise cryptographic keys before host DRAM populates.
4D xBOM Passports & 1:1 BIAN v14.0 Lineage
Prior to deployment, the Formal Verification Engine (FVE) executes an SMT reachability pass across the Control-Flow Knowledge Graph (CFKG) of the composite PBOM. Returning UNSAT proves mathematically that zero non-compliant execution paths exist and mints a signed 4D xBOM Passport (with DBOM Passports mapped 1:1 to BIAN v14.0 Service Domains). Returning SAT triggers an immediate Build VETO.
Black-Box Adapter Quarantine Enclaves
When tenants consume closed-weight commercial frontier models or external APIs whose vendors do not disclose raw neural weights (AI/ML-BOM), the connector is encapsulated inside a hardware Quarantine Enclave bound to a SaaSBOM manifest. Stripped of signing keys and ledger write access, its egress is filtered by PIME data-minimisation contracts and every output completion is sanitised inline in < 45 μs by the DRAGON triadic gate.