Symphony Hub › SoO – Orchestration › Gatekeeper
System of Orchestration Capability · SoO

Gatekeeper

A compromised API key, rogue AI instruction, or skipped approval step can trigger irreversible operational loss long before a compliance audit ever runs. As the Constitutional OS’s Policy Enforcement Point (PEP), Gatekeeper stands at the execution boundary to verify every request’s Policy Hash, enforce Deontic Prohibition Dominance (\(\mathbf{F} \succ \mathbf{O} \succ \mathbf{P}\)), and admit only actions holding a single-use DRAGON warrant – binding live operating workflows to iEngine proposes, DRAGON adjudicates, Conductor executes, Switcher+ fulfils.

Target Architecture (Q4 2026 Roadmap) Target Latency: < 50 µs Warrant Interception & Intent-Frame Hydration
Gatekeeper Architecture Illustration
Introduction

The Silicon Sentry of Verifiable Law & Intent Gating

The Gatekeeper is the inward-facing constitutional checkpoint operating within the onePOI.online System of Orchestration (SoO). Positioned as the non-bypassable admission gate to the execution plane, the Gatekeeper is completely decoupled from external network routing, cloud APIs, and physical peripheral drivers.

Its single, precise operational mandate is to hold all incoming Actuator DAGs in a strict fail-closed lock until it intercepts, decrypts, and cryptographically validates a signed Lawful Warrant (PERMIT) issued by the DRAGON Adjudication Engine. The Gatekeeper is the platform’s constitutional magistrate, ensuring that no technical instruction can materialize into kinetic action without unchallengeable legal and regulatory authority.

Gatekeeper Runtime Manifest Icon

Gatekeeper Runtime Manifest

Constitutional Admission Magistrate

LAYER: SoO // INWARD PEP
TARGET LATENCY: < 50 µs (Target State)
CANONICAL ROLE: Gatekeeper Admits
RUNTIME DESCRIPTION: Inward-facing Policy Enforcement Point validating warrants, hydrating Intent Frames, and enforcing Deontic Dominance.
Tier 2 · Core Capabilities

Core Operational Capabilities

Gatekeeper secures the boundary between judicial intent and physical actuation across the Salient FinTech Innovation Set.

1. Cryptographic Warrant Interception & Attestation

1. Cryptographic Warrant Interception & Attestation

Operates inside hardware-isolated Trusted Execution Environments (TEEs), intercepting execution requests and validating \(O(1)\) constant-time cryptographic signatures against the platform's root-of-trust before releasing locks.

2. Intent-Aware Workload Scheduling

2. Intent-Aware Workload Scheduling

Manages the queuing and release of Actuator DAGs, resolving inter-stanza dependencies, late-binding Pulumi outputs, and bitemporal constraints across Valid-Time (\(V_t\)) and Transaction-Time (\(T_t\)) axes.

3. Intent-Frame Context Hydration

3. Intent-Frame Context Hydration

Extracts the Policy Hash (\(\mathcal{PH}\)) embedded within the warrant and binds runtime variables to version-pinned TopHAT constraints, preventing ultra vires parameter injection or execution drift.

4. Deontic Boundary Enforcement (\(\mathbf{F} \succ \mathbf{O} \succ \mathbf{P}\))

4. Deontic Boundary Enforcement (\(\mathbf{F} \succ \mathbf{O} \succ \mathbf{P}\))

Acts as the mechanical circuit breaker for deontic logic governance. If an instruction trips a Prohibition (\(\mathbf{F}\)), Gatekeeper executes an instantaneous Structural VETO, paralyzing threads before state changes occur.

Subsystem Triad

The Subsystem Triad of the System of Orchestration (SoO)

Within the SoO, execution is decomposed across three distinct capability blocks with rigid mathematical boundaries, preventing execution logic from ever bypassing or degrading constitutional policy.

1. THE GATEKEEPER

The Constitutional Magistrate

The inward-facing security boundary and constitutional checkstop. Intercepts inbound Actuator DAGs, holds them in strict HALT until a signed DRAGON PERMIT is validated, and hydrates the runtime Intent Frame.

  • Admission Control: Holds DAGs in HALT until DRAGON PERMIT validation.
  • Intent Hydration: Binds runtime to parent Agreement DAG Intent Frame.
  • State Validation: Refuses tokens for unmapped topological paths.
2. THE CONDUCTOR

The Macro-Orchestration Core

The middle-out macro-orchestration hub. Translates authorised business intent into technical runbooks, decomposing workflows into Stanzas and Strophes while managing Contrary-to-Duty (CTD) Sagas.

  • Grammar Decomposition: Decomposes playbooks into Stanzas and Strophes.
  • Saga Management: Manages durable sagas and executes automatic CTD reversals.
  • State Checkpointing: Commits state before and after every Stanza transition.
3. FLOW360

The Kinetic Dispatcher

The outward-facing routing and kinetic dispatch engine. Blind to legal reasoning, its mandate is operational: fast, reliable movement of data and commands across the geo-distributed infrastructure grid.

  • Omni Dispatch: Dispatches idempotent instructions to PBCs and POI appliances.
  • Idempotent Action: Guarantees safe retries during network partitions.
  • Telemetry Harvesting: Funnels execution Glyphs into MAESTRO for auditability.

The 7-Step Lockstep Execution Handshake

This triad operates through a strict, non-repudiable 7-step handshake that guarantees Substantiated Integrity:

[ Inbound Claim ] ──► ( SoE Gateway ) ──► [ Proposed Intent ] ──► ( DRAGON Adjudication ) │ Signed Warrants ▼ ┌───────────────────────────────── THE CONDUCTOR TRIAD ─────────────────────────────────┐ │ │ │ 1. Intercept & Verify ──► 2. Hydrate & Frame ──► 3. Sequence & Transact (Saga) │ │ (The Gatekeeper) (The Gatekeeper) (The Conductor Core) │ │ │ │ │ ▼ │ │ 6. Lock & Commit ◄── 5. Telemetry Stream ◄── 4. Idempotent Grid Dispatch │ │ (The Gatekeeper) (Flow360 Engine) (Flow360 Engine) │ │ │ └───────────────────────────────────────────────────────────────────────────────────────┘ │ ▼ Idempotent Action ( Edge POI Hardware Peripherals )

1. Intercept & Validate: The Gatekeeper catches the execution request, halts it, and waits for the DRAGON warrant.

2. Bind & Unlock: Upon warrant validation, the Gatekeeper hydrates the token and passes it to the Conductor.

3. Orchestrate: The Conductor manages the workflow sequencing and saga integrity.

4. Route & Actuate: Flow360 handles the kinetic dispatch, navigating the network to hit the physical edge endpoint.

5. Attest: Flow360 returns the signed evidence of the action (the Glyph), which the Gatekeeper seals into a Lawful Act Hyperedge (LAHE).

6. Commit: The LAHE is written to the immutable bitemporal ledger, closing the transaction loop.

  Corpus Deep Dive · Bounded Defensibility

Mitigating Core Failure Modes Across the Grid

By combining kernel-level eBPF filters, hardware attestation, and fail-closed state machines, Gatekeeper and the SoO triad defeat critical distributed attack vectors.

OWASP LLM06 (Excessive Agency)

OWASP LLM06 (Excessive Agency)

Zero Executive Agency

AI models in the System of Intelligence have zero executive authority. They can only formulate non-binding Proposed Intent claims. Flow360 is physically blocked from executing unapproved calls via eBPF/XDP kernel hooks, which remain closed until Gatekeeper validates an authoritative PERMIT signed by DRAGON.

OWASP LLM03 (Supply Chain Integrity)

OWASP LLM03 (Supply Chain Integrity)

cATO & Dynamic PBOM

Continuous Authority to Operate (cATO) tracks dependencies via the PBOM (SBOM/HBOM/DBOM/AI/ML-BOM). If a vulnerability is announced, the Event Mesh alerts Gatekeeper, which instantly invalidates the asset in cache, severs communication rails in under 100 microseconds, and refuses execution.

Network Degradation & WAN Blackout

Network Degradation & WAN Blackout

Constitutional Island Mode

During network partition, POI Appliances enter Constitutional Island Mode. Edge orchestrators evaluate cached local Agreement DAG rules. If local evidence is insufficient to clear deontic constraints, Gatekeeper refuses execution tokens, and Flow360 blocks mechatronic relays, locking assets in a fail-closed state.

Catastrophic Tamper & Hardware Intrusion

Catastrophic Tamper & Hardware Intrusion

Dynamic Bus-Impedance Defense

Motherboard trace monitoring detects physical probe attachments or voltage glitches in microseconds. Flow360 immediately triggers hardware zeroization relays (clearing SRAM keys) and mechanically locks peripheral cash cassettes while the Gatekeeper writes the terminal event receipt.

Deep Technical: Hardware-Isolated Coexistence within MTCCF & Silicon Apartments

Deep Technical: Hardware-Isolated Coexistence within MTCCF & Silicon Apartments

Under the Multi-Tenant Confidential Computing Framework (MTCCF), the memory footprints of the validation plane (Gatekeeper) and the execution routing plane (Flow360) are entirely segregated at the processor level.

Through strict page-table partitioning, core-exclusion policies, and UCIe 2.0 enclave boundaries (Silicon Apartments), the system ensures that even if Flow360's external, network-facing APIs are subjected to an advanced adversarial compromise, the attacker is physically blinded and blocked from "reaching back" into the Gatekeeper's memory space to leak root cryptographic keys or alter constitutional axioms.

Deep Technical: Short-Lived SPIFFE SVIDs & Token Gating

Deep Technical: Short-Lived SPIFFE SVIDs & Token Gating

The Gatekeeper integrates with SPIFFE/SPIRE to issue short-lived, cryptographically ephemeral SPIFFE Verifiable Identity Documents (SVIDs) for each individual stanza execution.

SVIDs expire within seconds of transaction completion, mitigating replay attacks and ensuring that compromised worker nodes cannot reuse expired authorisation tokens across unrelated transaction flows.

Deep Science: Deontic Logic Circuit Breaking & LAHE Generation

Deep Science: Deontic Logic Circuit Breaking & LAHE Generation

The Gatekeeper evaluates actions using a deterministic deontic decision function \(\mathcal{F}_{\text{deontic}}(a)\) where Prohibition Dominance (\(\mathbf{F} \succ \mathbf{O} \succ \mathbf{P}\)) is strictly enforced:

\(\mathcal{F}_{\text{deontic}}(a) = \begin{cases} \text{VETO} & \text{if } a \cap \mathbf{F} \neq \emptyset \\ \text{PERMIT} & \text{if } a \subseteq \mathbf{P} \land \mathbf{O}_{\text{satisfied}} \\ \text{HALT} & \text{otherwise} \end{cases}\)

Upon verified execution return from Flow360, Gatekeeper binds the execution proof (\(\mathcal{G}\)) to the original DRAGON Lawful Warrant (\(\text{Warrant}_{\text{DRAGON}}\)) and Policy Hash (\(\mathcal{PH}\)), generating the immutable Lawful Act Hyperedge (LAHE):

\(\text{LAHE} = \mathcal{H}\left( \text{Warrant}_{\text{DRAGON}} \parallel \mathcal{PH} \parallel \mathcal{G} \right) \xrightarrow{\text{commit}} \text{Ledger}_{\text{bitemporal}}\)