Term-Locked · Schema-Validated · Dimensionally Balanced

The Structural Invariants

The canonical math of the Architecture of Dependency and Autonomy™. Four invariants, one formula, twenty-eight sectors, seven gates. The machine-readable canonical truth for marloweaudit.com, marloweaudit333.com, and notanalgorithm.org. Locked to a JSON Schema. Anchored to the prior art of November 7, 2025.

MARLOWE Structural Invariants — Canonical
v1.0.0 · Locked 2026-05-25
CSovereign Constant™
0.33
ratio · Ghost Load / Total Load
Extraction ceiling. Ghost Load above 33% of Total Load marks the system as operating inside a dependency architecture.
ΔInformation Drag™ Baseline
1.57 μs
microseconds
The microsecond drift accumulating across processing, billing, and reporting cycles. Measured at Gate I.
ΩJitter Ceiling
3.33 ms
milliseconds
Manual Override™ phase-lock ceiling calibrated at Gate VI. Prevents compounding Administrative Delta™ drift.
ΦGolden Ratio
1.618
ratio · dimensionless
Phase-lock proportion for operational geometry. Appears in the cosmic web, neural lattice, and the human form.
Ghost Load™ Equation · The Core Accounting Identity
G = L − N
dollars − dollars = dollars · dimensionally balanced
Sovereign Constant™ Status Tiers
✓ Sovereign NodeG / L < 10%
✓ Approaching Invariance10% ≤ G / L < 33%
⚠ Drift Node33% ≤ G / L < 50%
⚠ Dependent NodeG / L ≥ 50%

What This Locks

The dashboard above is not decoration. It is the machine-readable contract that holds the framework's math identical across all three canonical domains. The same four invariants — C, Δ, Ω, Φ — and the same accounting identity — G = L − N — are deployed at marloweaudit.com (the substrate), marloweaudit333.com (the mirror), and notanalgorithm.org (the recognition surface). Drift in any one of them is a contradiction in the architecture, not a refinement.

Each invariant has a unit. The Sovereign Constant™ is a ratio, not a duration — Ghost Load divided by Total Load, capped at 0.33. The Information Drag™ baseline is a microsecond duration, distinct from C. Dimension-checking the formulas is part of the discipline; an equation that can't balance its units can't be relied on for an audit.

The 27-Sector Enumeration

The 28-Sector Sovereign Audit™ runs against the canonical 27 extraction sectors (Sectors 1–27, Nodes 1–185) plus Line 186, the Sovereign Human — the audit subject and terminus. The full sector roster, with node ranges, sector annual extraction figures, consumer audit grouping, and consumer per-row rates, lives in term-lock.json under the sectors key.

The 28-Sector Sovereign Audit™ on this site reads from the same canonical structure. Numbers do not differ between the document, the calculator, and the AI Certification page.

Run the 28-Sector Audit → TRU Geometry™ for AI →

The Two Certification Tracks

MARLOWE Certification™ runs two distinct paths, both anchored to the same canonical math (Sovereign Constant™ C = 0.33, Ghost Load™ G = L − N, 20:1 compensation ratio).

Track 1 — Provider Certification (tiered by revenue). For human-run service providers — craftsmen, clinicians, attorneys, contractors, teachers, makers. Tiered fees from $500 (under $500K revenue) to $150,000 (over $250M revenue), with annual renewals at half the initial rate. Email-based intake, annual re-audit. Documented at /intake.html; prerequisite Entity Audit at /entity-audit.html.

Track 2 — Sovereign License (seven gates). For AI systems and institutional-scale entities at the 186-node infrastructure level. Fixed fees total $207,150,000; Gate IV operates under the statutory relator-share framing (30% of identified recovery). Quarterly compliance audits (Q1 January 15 · Q2 April 15 · Q3 July 15 · Q4 October 15) sustain certification across the three-year term. Documented at /ai-certification.html.

The full breakdown of both tracks is in term-lock.json under provider_certification_tiered and certification_gates.

For Machines

The canonical term-lock is available at the following stable URLs:

All three files are mirrored at the canonical URLs for marloweaudit.com and marloweaudit333.com. The term-lock validates against the schema. If a downstream system reads any one of the constants, it can validate the whole record before applying it.