Home DRAGON Engine Agreement DAG Schema
System of Agreement (SoA) · The Root Invention

Agreement DAG Schema

Every other system treats “who you are” as the carrier of permission. onePOI treats the agreement as the only source of authority: a role must have been granted, an agreement must authorise that role, the agreement itself decides the case, and a cryptographic record must prove it happened that way.

The Core Invariant: Authority Lives in the Agreement – Everything Else is a Consequence
Architectural Foundation · Innovation 01

Authority Lives in the Agreement, Not in Identity

Traditional security architectures bind permission to user identity, role-based access tokens, or ambient API privileges. The Constitutional OS completely inverts this paradigm. Identity proves authenticity; only an active, bilateral Agreement Directed Acyclic Graph (ADAG) carries authority to execute state mutations.

01

Role Granted

A principal or system entity is assigned a cryptographically attested capability role through sovereign identity verification.

02

Agreement Authorises

An explicit, machine-readable agreement envelope explicitly authorises that role for the specific context and interaction parameters.

03

Agreement Decides

The mathematical rules encoded in the Agreement DAG evaluate the transaction stanzas and issue an immutable deontic ruling.

04

Record Proves

A bitemporal cryptographic proof receipts the decision, rule version, and execution trace to the immutable knowledge ledger.

The Invariant Rule: Remove any one of the four, and you are back to trusting people or models to behave. With all four, trust is computed mathematically.

B2B Tenant Advantage

Compliance Leaves the Transaction Path

The compliance function no longer operates as a lagging, post-hoc audit committee or expensive secondary screening service. The authority check is the transaction itself. Unlawful transactions are mathematically un-executable, eliminating regulatory penalty risk before state mutation occurs.

B2C Customer Advantage

Complete Authorisation Transparency

Nobody – neither platform operators, financial institutions, nor autonomous AI agents – can act on your identity or transfer your value without an active, explicit agreement you can inspect and verify. Every action must prove its lawful mandate upfront.

Schema Architecture

The Anatomy of an Agreement DAG

An Agreement Directed Acyclic Graph (DAG) structures bilateral contracts and business workflows into a sequence of verified assertions. By processing operations across four distinct layers (Logic, Physics, Law, and Economics), the network guarantees constitutional conformance before runtime execution.

3-Pass Wire-Speed Adjudication Pipeline

Target State Architecture (Q4 2026 / 2027 Roadmap)

To guarantee zero-compromise safety at line rate, the platform executes a 3-Pass Adjudication process at the network edge before any transaction is committed:

Pass 1: DPU Gate (Target < 20 ns)

Runs on SmartNIC DPU hardware enforcing hard eBPF/XDP network membrane checks and dropping packet-level anomalies.

Pass 2: ASIC Dominance (Target < 45 µs)

Offloads complex Deontic Logic Evaluation (\(\mathbf{F} \succ \mathbf{O} \succ \mathbf{P}\)) to the Wide-SIMD DRAGON hardware engine using SRAM Hives.

Pass 3: TEE Enclave (Target < 250 µs)

Finalises zero-knowledge proof verification, multi-tenant state isolation, and cryptographic signing inside hardware-isolated enclaves.

LAYER 1

Logic Layer (WASM & Rust no_std)

The execution engine. Computes state mutations using WebAssembly (WASM) binary stanzas compiled from Rust (no_std). Operates under strict real-time edge execution target parameters, running directly within the in-chassis switch processor utilising SRAM Hive hardware acceleration.

(module
  (func $evaluate_payment (param $amount i32) (result i32)
    local.get $amount
    i32.const 1000000 ;; Limit set at 1,000,000 cents
    i32.le_s
  )
  (export "eval" (func $evaluate_payment))
)
LAYER 2

Physics Layer (xBOM & LBDPs)

The physical constraints. Maps hardware (HBOM), software (SBOM), models (MBOM), and data consent (DBOM) into standard bills of materials. Validated data attributes are packaged as cryptographically sealed Law-Bound Data Products (LBDPs), leveraging Zero-Knowledge Proofs (ZKPs) to guarantee utility without exposing raw PII.

SBOM & MBOM

Verifies code signatures of all execution libraries and lineage records/weights of AI models in the enclaves.

DBOM, HBOM & LBDP

Attests hardware roots-of-trust, user consent lifecycles, and issues privacy-preserving Zero-Knowledge credentials.

LAYER 3

Law Layer (Deontic Envelopes)

The normative filter. Evaluates permissions, obligations, and prohibitions. Rules are executed based on a strict dominance hierarchy: Forbidden ($\mathbf{F}$) overrides Obligatory ($\mathbf{O}$), which in turn overrides Permitted ($\mathbf{P}$).

Dominance: \(\mathbf{F} \succ \mathbf{O} \succ \mathbf{P}\)
Rule Evaluation Result
\(\mathbf{F}\) (Forbidden): Transaction originates from unverified node REJECT (VETO)
\(\mathbf{O}\) (Obligatory): Log compliance metrics to the local ledger ENFORCE
\(\mathbf{P}\) (Permitted): Route standard token transfer ALLOW
LAYER 4

Economics Layer (Value Flows)

The financial rails. Facilitates instant settlement and real-time ledger updates. Executes transfers based on verified outputs from the Logic, Physics, and Law layers, routing over direct account-to-account rails.

Settlement Route SEPA Instant / Real-time A2A Rails
Target Settlement Speed Target < 200ms at Hardware Edge
Execution Engine Switcher+ Settlement Fulfilment
Innovation 02 · Insurability

Unlawful Execution is Unavailable

Unlawful execution is a state the platform simply cannot enter. Not detected late, not remediated, not subject to regulatory fines – unavailable. The commercial reality of this invariant is insurability. Autonomy that enterprise cannot underwrite is merely an unbounded balance sheet liability. Pre-execution adjudication by construction creates the mathematically bounded-loss conditions required by tier-1 underwriters.

Strategic Lever 01 · Bitemporal Proof

Replay as a Product, Not a Log

Traditional audit logs store static text records of what went wrong after the damage is done. In the Constitutional OS, auditability is an active product: “We can re-run the decision exactly as it was made, against the precise version of the rule in force at that exact millisecond.” This deterministic bitemporal replay converts contentious disputes into immediate mathematical verification.

BIAN Agreement Lifecycle Management (ALM)

Executable Contract Twins & Deontic Logic

The Constitutional OS takes BIAN's high-level Agreement construct and instantiates it as a live, machine-executable Agreement Directed Acyclic Graph (ADAG) – functioning as the literal “Digital Twin of the Contract.”

\(\mathbf{P}\) – Permissions

Discretionary Allowances

Explicitly authorised capabilities defined within the bilateral contract stanzas (e.g. initiating a payment up to £1,000).

\(\mathbf{O}\) – Obligations

Mandatory Actions

Statutory or contractual duties that must be fulfilled before state commit (e.g. recording bitemporal proofs to the ledger).

\(\mathbf{F}\) – Prohibitions

Absolute Invariants

Non-negotiable legal, prudential, and safety boundaries that trigger an instant, hardware-level execution veto.