LAKHOWAL

THE GAMMA STACK

Five Layers. One Boundary.

Deterministic execution authority, from action classification to ledger commitment. Total overhead: 90 milliseconds. No model code changes required.

LAYER BREAKDOWN

How the Stack Works

Layer 1LUIPM·Kernel

The core permit-management substrate. Receives proposed actions, classifies them, resolves predicate sets, and computes Γ. The central enforcement point.

Latency Budget5ms
Layer 2LAS·Stability

Consistency and integrity under load. Runs predicates in parallel, monitors Integrity-Flux (I_φ) drift, maintains coherence under adversarial conditions.

Latency Budget40ms
Layer 3LFC·Federation

Coordinates distributed agents and environments. Maintains permit validity across sovereign boundaries with attested concurrence.

Latency Budget10ms
Layer 4RCC·Context

Manages contextual state, currency, and drift signals. Feeds the Internal Coherence Score (ICS) for every evaluation cycle.

Latency Budget25ms
Layer 5Reverse Law·Evidence

Produces the immutable hash-linked record. Constructs and commits the ERTuple to the Hydra Ledger. TEE-backed signing. Proof-Before-Action enforced here.

Latency Budget8ms

Total end-to-end latency: 88ms (10ms headroom to 100ms budget).

ARCHITECTURAL CONSTRAINTS

The Three Invariants

Non-Compensatory Rule

Γ = 0 is the only state that permits actuation. Any Γ > 0 — even one failed predicate — forces SAFE_STATE. No passing predicate compensates for one failure. No human override unlocks the gateway.

Proof-Before-Action

The ERTuple must commit to the Hydra Ledger before the Gamma Permit token is released. If the ledger commit fails for any reason, the system enters SAFE_STATE — even if every predicate passed.

Causal Independence

The AI cannot grant its own permit. Authority is external to the model. Memory, hardware, and software logic boundaries are physically and logically separate.

CANONICAL SEQUENCE

The 7-Step Gamma Authorization Pipeline

1.Capability Isolation — the proposed action enters the Gamma Interceptor at LUIPM with zero inherent authority.
2.Predicate Evaluation — the action is classified and its predicate set is evaluated in parallel (LAS, LFC, RCC contribute).
3.Non-Compensatory Γ — Γ (gamma) is computed as the maximum predicate deviation; any single failure makes Γ > 0.
4.Execution Binding — the action is bound to its evaluation context and its candidate ERTuple.
5.Dual Permit Gate — Permit-to-Act and Permit-to-Adapt are checked; the gate opens only when Γ = 0.
6.Fail-Closed Resolution — any Γ > 0 (or a failed ledger commit) forces SAFE_STATE and the Execution Gateway stays closed.
7.Proof-Before-Action Logging — the signed (TEE-backed) ERTuple is committed to the Hydra Ledger hash chain before actuation.

All steps complete in ≤ 100ms.

DEPLOYMENT OPTIONS

Four Topologies, Same Guarantee

Shadow Mode

Non-blocking observer. Deployable in 5–10 business days. Zero model code changes. Watch permits before enforcement.

Inline Gateway

Fail-closed enforcement in customer VPC. Blocks actions that fail predicate checks. Full deterministic control.

SDK-Wrapped Action

For embedded agents and autonomous tools. Wraps the action call in the Gamma Interceptor. Language agnostic.

Air-Gapped / Sovereign

No outbound network dependency. Hydra Ledger runs on-premise. Full data residency compliance.