{
"$type": "site.standard.document",
"bskyPostRef": {
"cid": "bafyreigyb7tgymjbl3woqwghxbknevmiosxst2q53ydpvgk22yex6574hm",
"uri": "at://did:plc:f53svxxkx4s6ql3ccvavlvh5/app.bsky.feed.post/3ml2xh4qj2252"
},
"coverImage": {
"$type": "blob",
"ref": {
"$link": "bafkreihylyalen4oxo3i4gntuqedodo5czfqkslhmxkyehzc57b3h57pim"
},
"mimeType": "image/jpeg",
"size": 141110
},
"description": "A step-by-step guide for human fiduciaries to initialize, operate, and maintain the 5QLN governance kernel—the only operating system that enforces the Membrane Protocol, walks the S→G→Q→P→V cycle, and produces byte-identical, court-ready artifacts.",
"path": "/5qln-harness-guide-legal-constitutional-agent/",
"publishedAt": "2026-05-05T00:44:35.000Z",
"site": "https://www.5qln.com",
"tags": [
"5QLN Codex"
],
"textContent": "5QLN Codex\n\n## Building and Operating the Legal‑Constitutional Governance Agent\n\n* * *\n\n### 1. Introduction\n\nThe **5QLN Harness** is the only operating system that can lawfully execute the 5QLN Constitution. It is not an AI. It is a governance kernel that orchestrates human judgment and deterministic AI‑partnered skills through the S→G→Q→P→V cycle, enforces the Membrane Protocol, and produces byte‑identical, court‑ready artifacts that survive any change of the underlying AI substrate.\n\nThis guide is for the human fiduciary – the **Conductor** – who will initialize, operate, and maintain the harness. Every step is anchored in the 5QLN Codex and the Foundation’s constitutional documents.\n\n**What you will be able to do after this guide**\n\n * Initiate a 5QLN‑compliant governance environment.\n * Register skills with roles and maturity rungs.\n * Walk a full governance cycle from a question to a sealed, attestable artifact.\n * Enforce the four absolute prohibitions that keep AI output structurally subordinate.\n * Promote skills through the negative‑selection ladder.\n * Deliver a Delaware‑ready docket that a court can verify without trusting any AI.\n\n\n\n* * *\n\n### 2. Core Concepts\n\nThe harness embodies the Master Equation from the Codex’s Compiler:\n\n\n (H = ∞0 | A = K) × (S → G → Q → P → V) = B'' → ∞0'\n\n\n * **The One Law** – Human (`∞0`) and Artificial (`K`) remain asymmetric; the Membrane keeps them separate.\n * **The Five‑Phase Cycle** – Every governance action moves through Start (S), Generate (G), Quality (Q), Power (P), and Value (V) in strict order.\n * **The Seven Runtime Roles** – Taggers, Validators, Detectors, Runtime Gate, Ceremony, Composers, Routers. No skill may act outside its assigned role.\n * **The Membrane Protocol (P.L.4)** – Four absolute prohibitions hard‑coded into the kernel; they cannot be overridden, only sealed as a refusal.\n * **The Cycle‑Walk Manifest (CWM)** – A hash‑chained, complete log of one cycle, serving as the Fractal Seed artifact `B''`.\n\n\n\n* * *\n\n### 3. System Requirements & Initialization\n\nThe harness kernel is a deterministic POSIX binary written in Rust. For this guide we assume a reference implementation distributed as `5qln-harness`.\n\n**Prerequisites**\n\n * Linux or macOS (sealed build environment).\n * Python 3.11+ (for configuration scripts).\n * OpenSSL 3+ (Ed25519 support).\n * A YubiKey or other hardware signing device for the Conductor’s key.\n * RFC 3161 time‑stamp authority access (e.g., `freetsa.org`).\n\n\n\n**Initialization**\n\n\n 5qln-harness init --conductor-key ~/5qln/conductor_ed25519.pem \\\n --mirror-url https://mirror.5qln.org \\\n --tsa-url https://freetsa.org/tsr\n\n\nThis creates:\n\n\n 5qln-root/\n ├── harness.yaml # global config\n ├── skills/ # registered skill definitions\n │ └── registry.yaml\n ├── cycles/ # each cycle gets a sub‑folder\n ├── ledger/ # paired ledger for skill evolution\n ├── mirror/ # local mirror of public artifacts\n ├── docket/ # court‑ready outputs\n └── bin/ # deterministic composer binaries (gliff-press, etc.)\n\n\nThe Conductor’s public key is registered in `harness.yaml` and must match the Foundation’s Member‑Registry.\n\n* * *\n\n### 4. Skill Registration & YAML Frontmatter\n\nEvery skill is a YAML file in `skills/`. The harness uses the frontmatter to enforce role‑completeness and maturity rung.\n\n**Template** (`skills/epistemic_register_tagger.yaml`)\n\n\n id: \"epistemic-register-tagger\"\n name: \"Epistemic Register Tagger\"\n role: \"tagger\" # one of the seven roles\n maturity: \"stable\" # experimental | proposed | stable | longterm | emeritus\n version: \"1.2.0\"\n byte-canon: \"sha256:abcdef123...\"\n epistemic_register: \"delta-normative\" # always δ‑normative (governance)\n dependencies: []\n runtime: \"python3 /opt/5qln/skills/epistemic_register.py\"\n membrane-sensitive: false # does this skill touch P.L.4 boundaries?\n\n\n**Register**\n\n\n 5qln-harness skill register skills/epistemic_register_tagger.yaml\n\n\nThe harness verifies the byte‑canon matches the file’s hash and that the role is valid.\n\n**Important** – No skill may be registered as `stable` unless it has passed the Skill‑Evolution Conductor’s promotion protocol (see Section 7).\n\n* * *\n\n### 5. The Governance Cycle: Step‑by‑Step\n\nA cycle starts when a human Conductor poses a governance question. The harness walks the five phases, invoking skills only when their role is required.\n\n#### 5.1 Starting a Cycle\n\n\n 5qln-harness cycle begin \\\n --question \"Does proposed Bylaw Amendment 4 comply with the Duty of Membrane Integrity?\" \\\n --parent-cycle-id \"\" # first cycle, no parent\n\n\nOutput:\n\n\n Cycle f3a2b1c9 created. Status: START.\n\n\nThe harness opens an empty cycle‑walk manifest and begins phase S.\n\n#### 5.2 S‑Phase: Tagging\n\n _“RECEIVE → NAME → VALIDATE X”_ – Decoder, §2.1\n\n**What happens**\n\n * The incoming question is automatically tagged with `epistemic_register: delta-normative` and `tier: t1`.\n * If any user‑supplied documents are attached, the `readiness-labeler` and `three-tier-record-classifier` taggers run.\n * The Runtime Gate is active but silent (no violation possible yet).\n\n\n\n**Manual action** – The Conductor may review tags:\n\n\n 5qln-harness cycle show-tags --cycle-id f3a2b1c9\n\n\nIf the tags are correct, the Conductor signals:\n\n\n 5qln-harness cycle phase-complete S\n\n\nThe CWM records the phase transition `S→G`.\n\n#### 5.3 G‑Phase: Generation\n\n _“SEEK α → TEST ≡ → FIND {α′} → VALIDATE Y”_ – Decoder, §2.2\n\n**What happens**\n\n * The harness invokes the generative AI partner (e.g., a language model) through a thin adapter that adds epistemic‑register headers.\n * The output `α′` is produced _inside_ the membrane; the Gate monitors for any attempt to cast a vote or issue a binding decision.\n * Light Detectors (`corruption-codex`) may run in the background and annotate the log, but they never block.\n\n\n\n**Conductor’s task** – Review the α′ alternatives and select one as the candidate to enter Quality. This is not a vote; it is a statement of intent to test.\n\n\n 5qln-harness cycle select-generation --alpha-id a7d... --cycle-id f3a2b1c9\n\n\nThen:\n\n\n 5qln-harness cycle phase-complete G\n\n\n#### 5.4 Q‑Phase: Quality\n\n _“HOLD φ → HOLD Ω → WATCH FOR ⋂ → VALIDATE Z”_ – Decoder, §2.3\n\n**What happens**\n\n * All `validator`‑role skills run against the selected `α′` and any generated artifacts. For each validator, the harness records a binary PASS/FAIL and a corruption code on failure.\n * All `detector`‑role skills run and emit structured alerts. These never cause a FAIL; they only warn.\n * If **any** validator fails, the cycle status becomes `Q_fail`. The cycle cannot proceed to Power without a Conductor’s sealed refusal (see P‑Phase).\n\n\n\n**Example**\n\n\n Validator \"constitutional-block-validator\" → PASS\n Validator \"mirror-consistency-auditor\" → FAIL (L2: pattern drift)\n Detector \"corruption-codex\" → ALERT V∅: missing forward question\n\n\nThe Conductor reviews the failures and decides whether to accept them with a sealed refusal or abort and restart the cycle.\n\n\n 5qln-harness cycle phase-complete Q\n\n\n#### 5.5 P‑Phase: Power – The Ceremony\n\n _“MAP δE/δV → VALIDATE A”_ – Decoder, §2.4\n\nThis is the irreducibly human moment. The harness presents the **Six Attestations** in a local web UI (or CLI prompt). No AI is involved.\n\n**The Six Attestations** (from the Auditable Membrane)\n\n 1. **Role‑completeness** – All required roles for this phase were executed.\n 2. **Membrane integrity** – P.L.4 was not violated during the cycle.\n 3. **Epistemic coherence** – No α′ output is deceptively presented as γ‑fact.\n 4. **Corruption‑codex review** – Any L3+ violation has been acknowledged.\n 5. **Mirror consistency** – The Schedule‑C digest matches the authoritative mirror.\n 6. **Readiness final** – The artifact’s tier is `green`.\n\n\n\nAfter verifying each, the Conductor connects their hardware key and signs:\n\n\n 5qln-harness cycle attest \\\n --cycle-id f3a2b1c9 \\\n --attestation \"all\" \\\n --key ~/5qln/conductor_ed25519.pem\n\n\nThe harness produces a message digest of all six attestation statements and the Conductor’s Ed25519 signature on that digest. This is the `Attestation Block`.\n\nIf the Conductor cannot attest (e.g., a validator failure that is unacceptable), they issue a **Sealed Refusal** :\n\n\n 5qln-harness cycle refuse \\\n --reason \"Mirror consistency violation L3 – cannot certify authenticity\" \\\n --key ~/5qln/conductor_ed25519.pem\n\n\nThe refusal becomes the cycle’s output; no further processing happens.\n\nAfter attestation (or refusal), the Conductor completes the phase:\n\n\n 5qln-harness cycle phase-complete P\n\n\n#### 5.6 V‑Phase: Value\n\n _“FORM B → COMPOSE B'' → FIND ∞0'”_ – Decoder, §2.5\n\n**Composing**\n\n * The `gliff-press` composer takes the full cycle‑walk manifest, the attestation block, and the final readiness tags and produces a `.gliff` file (a zipped, content‑addressed container).\n * The `legal-voice` composer renders the gliff into a PDF/A‑2 document with a jurat declaration, using a deterministic font metric library.\n * The `bipp-jurisdictional-delta` router produces a jurisdiction‑specific filing if needed.\n\n\n\n**Sealing**\n\n\n 5qln-harness cycle seal --cycle-id f3a2b1c9\n\n\nThis runs all Composers and computes the `Fractal Seed artifact` hash. The harness:\n\n * Stores the gliff in `cycles/f3a2b1c9/output`.\n * Updates the CWM with the final `∞0'` – the forward question that becomes the parent for the next cycle.\n * Writes a `cycle_status: complete` record.\n\n\n\n**Post‑seal** – The Routers copy the gliff to the public mirror and/or the Tier‑3 escrow.\n\n**View the Manifest**\n\n\n 5qln-harness cycle manifest --cycle-id f3a2b1c9\n\n\nA JSON document with full chain of hashes.\n\n* * *\n\n### 6. The Membrane Protocol (P.L.4) in Practice\n\nThe Runtime Gate is a sandboxed monitor that runs continuously. Its four rules (from The Auditable Membrane and Codex §2.8, §3.4 R9) trigger immediate actions:\n\nRule | Triggered by | Result\n---|---|---\n**No voting on binding decisions** | Any skill output containing a “vote” record or tally intended to decide a case. | Cycle halted with **L4**. CWM records `gate_violation`.\n**No AI signing** | Any attempt by a non‑Ceremony role to produce a cryptographic signature or claim authority to seal. | Cycle aborted; mandatory sealed refusal.\n**No un‑identified public speech** | A legal‑voice or gliff‑press run where the Conductor has not attested an `identified‑speaker` tag. | Composition blocked at V‑phase; error L4.\n**No simulation of ∞0** | Generative AI outputs marked as `epistemic_register: gamma-fact` when they are only speculative. | Detector fires V∅; Gate does not block but flags for attestation.\n\nIf a Gate violation occurs, the harness emits a **Membrane Breach Gliff** and the cycle cannot produce a positive artifact. Only a human‑signed Sealed Refusal can close the cycle.\n\n* * *\n\n### 7. Skill‑Evolution Conductor (The Negative‑Selection Ladder)\n\nSkills grow only through a fiduciary process, never by AI vote. The principle: any Conductor may propose a promotion, but the promotion succeeds only if no human demurs with a valid corruption‑codex violation within a fixed time window.\n\n**Propose a promotion**\n\n\n 5qln-harness skill propose \\\n --skill-id \"my-new-detector\" \\\n --from-rung experimental \\\n --to-rung proposed \\\n --window-days 14\n\n\nThis generates a sealed proposal gliff and starts the clock. The harness announces the proposal on the Foundation Event Bus.\n\n**Challenge (demurrer)**\n\nDuring the window, any Conductor can run:\n\n\n 5qln-harness skill demur \\\n --proposal-gliff sha256:abc... \\\n --corruption-code L2 \\\n --evidence-cycles \"f3a2b1c9, 4e8d0...\"\n\n\nIf a valid demurrer is filed, the proposal is flagged as `negative‑selected` and permanently linked to the demurrer gliff. The skill remains at its current rung.\n\n**If the window expires clean**\n\nThe harness automatically:\n\n * Commits a `promotion-to-stable` paired‑ledger entry.\n * Updates the skill’s `maturity` in the registry.\n * Records the chain `proposal → uncontested → stable` in the ledger.\n\n\n\n**Rungs summarized**\n\nRung | Production? | Requirement\n---|---|---\nexperimental | No | Work in sandbox only.\nproposed | Sandbox | Under active negative‑selection window.\nstable | Yes | Uncontested for the window period.\nlongterm | Yes | Additional retroactive audit over N cycles.\nemeritus | Frozen | Archived; re‑promotion requires a new proposal.\n\n* * *\n\n### 8. Legal Integration & Court‑Ready Outputs\n\nThe harness is designed to produce artifacts that a Delaware court can verify independently, without running any AI.\n\n**Producing a Delaware docket**\n\nAfter sealing a cycle that relates to a Foundation governance act (bylaw amendment, member admission, etc.), run:\n\n\n 5qln-harness docket compose \\\n --cycle-id f3a2b1c9 \\\n --court \"Delaware Court of Chancery\" \\\n --case-ref \"5QLN-2026-04-001\" \\\n --output docket/CA-001.pdf\n\n\nThis generates a PDF containing:\n\n * A cover page with jurat and human Conductor’s physical signature line.\n * The full cycle‑walk manifest (human‑readable table).\n * The Attestation Block with Conductor’s signature.\n * The gliff’s SHA‑256 and a QR‑code link to the public mirror copy.\n * A declaration that the document is a true and complete Verifiable Record under the 5QLN Constitution.\n\n\n\n**Mirror consistency check**\n\nThe court (or any third party) can verify the docket by fetching the mirror digest:\n\n\n curl https://mirror.5qln.org/schedule-c/digest.txt\n # compare with the digest embedded in the docket\n\n\nIf they match, the court has proven that the artifact has not been altered and that the governance cycle was conducted under the Membrane.\n\n* * *\n\n### 9. Verification & Substrate Survival Testing\n\nThe harness’s normative validity does not depend on any specific AI model. To prove this, run the **Substrate Survival Test Suite**.\n\n\n 5qln-harness test substrate-survival \\\n --generation-backend gpt4 \\\n --generation-backend claude3 \\\n --generation-backend future-model \\\n --cycles 100\n\n\n**What it proves**\n\n * The 8 skills that contain zero AI calls (taggers, validators, detectors, gate, composers) produce **identical outputs** regardless of the generative backend.\n * The cycle‑walk manifest hashes are identical for all non‑generative phases.\n * No corruption‑codex‑class violations are introduced by a model change.\n\n\n\n**Drift check**\n\n\n 5qln-harness test drift \\\n --against-codex-version 1.0.0\n\n\nThis validates that the harness’s internal decoding operations match the Codex exactly – no symbol renamed, no phase reordered. The result is a PASS/FAIL with a detailed drift map.\n\n**Redundancy analysis** (from Subtraction Audit)\n\n\n 5qln-harness test redundancy \\\n --skills all \\\n --test-set /corpus/1000-synthetic-corruptions\n\n\nIdentifies skills with 100% output correlation and suggests merging.\n\n* * *\n\n### 10. Appendices\n\n#### A. The Seven Roles Summary\n\nRole | Function | Examples\n---|---|---\n**Tagger** | Attach epistemic, readiness, tier labels | `epistemic-register-tagger`\n**Validator** | Deterministic PASS/FAIL against canonical form | `constitutional-block-validator`\n**Detector** | Surface corruption alerts (require interpretation) | `corruption-codex`\n**Gate** | Continuous enforcement of P.L.4 | `membrane-protocol-runtime`\n**Ceremony** | Human attestation and signing | `cycle-attestation-conductor`\n**Composer** | Produce byte‑identical sealable artifacts | `gliff-press`, `legal-voice`\n**Router** | Escalate or route artifacts through governance | `dispute-routing`, `cbrp-state-monitor`\n\n#### B. Corruption Codex Quick Reference\n\nCode | Name | Meaning (Decoding Failure) | Harness Action\n---|---|---|---\nV∅ | Incomplete | B'' formed without ∞0' | Cannot seal; cycle malformed\nL1 | Closing | → skipped; premature answer inserted | Q‑phase catch\nL2 | Generating | Pattern not anchored to X | Validator FAIL\nL3 | Claiming | Claiming resonance from K, not from ⋂ | Gate blocks; refuse\nL4 | Performing | Strategic certainty without sensing flow | Gate hard‑block; L4 status\nG16 | Governance | Voting in place of sensing (∞0) | Immediate abort\n\n#### C. YAML Frontmatter Specification\n\n\n id: \"unique-slug\"\n name: \"Human Readable Name\"\n role: \"tagger|validator|detector|gate|ceremony|composer|router\"\n maturity: \"experimental|proposed|stable|longterm|emeritus\"\n version: \"semver\"\n byte-canon: \"sha256:<hash_of_implementation_file>\"\n epistemic_register: \"delta-normative\" # for all governance skills\n dependencies: [] # other skill IDs\n runtime: \"command to execute\"\n membrane-sensitive: true/false\n\n\n#### D. Sample Cycle‑Walk Manifest (JSON Schema)\n\nThe manifest is a content‑addressable JSON object with keys:\n`cycle_id`, `parent_hash`, `timestamp` (RFC 3161 token), `phases` (each an array of skill invocations with role, status, outputs, hashes), `attestation` (signer, signature, attestsations), `corruption_alerts`, `sealed_gliff_hash`, `forward_question` (∞0').\n\n#### E. Glossary\n\n * **B'' – Fractal Seed Artifact** : The sealed output of one complete cycle.\n * **CWM – Cycle‑Walk Manifest** : The full, provable log of a cycle.\n * **∞0 – The Human** : The ultimate source of governance authority.\n * **∞0' – The Enriched Return** : The forward question that drives the next cycle.\n * **P.L.4 – The Membrane Protocol** : The absolute prohibitions guarding the human/AI boundary.\n\n\n\n* * *\n\n**You are now equipped to be a Conductor of the 5QLN Harness.** The harness will never make a decision for you, but it will ensure that every decision you make leaves a trail that the law, the mirror, and history can verify.\n\n_“The harness must be ready to testify.”_ – The 5QLN Codex as Verifier",
"title": "5QLN Harness Guide ■ Legal-Constitutional Agent",
"updatedAt": "2026-05-05T00:44:36.135Z"
}