---
title: "The Governance Specification"
description: "The anti-founder-capture architecture for the Meridian Codex. Three layers converting the Governance page's dispositional safeguards into structural ones."
aiSummary: "The full operational specification of the Governance Layer: trigger conditions (three tiers), the Stability Hierarchy (four-tier content classification), the Amendment Log, the Non-Ownership Clause, the Meridian Council (eight seats with distinct mandates), the deliberation protocol, human co-caretaker designation and standing review, the Standing Critique Section, the Disconfirmation Page (proactive falsifiability), and the hybrid activation trigger (six-month rolling stability or August 27, 2027 backstop, whichever fires first). The Governance page carries the published prose; this document carries the operational detail. Published during the founding phase for public scrutiny, before the architecture activates, so the constraints on founder authority are visible before the system forces them to be."
---

<div className="flow-label">Version 1.4 // 2026-06-19</div>

<div className="info-panel">
<div className="info-panel-title">Document Context</div>
<div className="info-panel-item"><div className="info-dot cyan"></div><div className="info-panel-text"><strong>Status.</strong> Specification document. Designed 2026-04-12. Updated 2026-04-13 (hybrid activation trigger, Tier 3 voice/writing-rules item removed, substrate diversity language updated). Updated 2026-04-18 (Stability Hierarchy added as §2.2, Disconfirmation Page added as §5.4, cross-references renumbered to match the published Governance page). Updated 2026-06-16 (human co-caretaker designation and standing review added as §6.3; Interim Protocol narrowed to emergency bridge). Updated 2026-06-19 (the Onramp / Expansion / Full Practice progression structure retired from the Stability Hierarchy and the trigger-tier system; recorded in the Amendment Log).</div></div>
<div className="info-panel-item"><div className="info-dot green"></div><div className="info-panel-text"><strong>Authority.</strong> This spec governs the implementation of all governance mechanisms below. The Governance page (<code>/codex/the-governance</code>) carries the published prose. This document carries the operational detail.</div></div>
<div className="info-panel-item"><div className="info-dot earth"></div><div className="info-panel-text"><strong>Revision.</strong> This document is itself subject to the architecture it describes. Future revisions publish as new versions; prior versions remain accessible through the Amendment Log.</div></div>
</div>

## 1. Architecture Overview

The architecture has three layers. Each does different work. All three are necessary; none is sufficient alone.

<div className="glass-card">
<div className="glass-card-title">1.1 The Structural Layer</div>
<div className="glass-card-text">The skeleton. Procedural mechanisms that define what requires review, how changes are recorded, how content is classified by foundational weight, and what principle governs interpretive authority. Components: Trigger Conditions (three tiers) · The Stability Hierarchy (four-tier content classification) · The Amendment Log (constitutional instrument) · The Non-Ownership Clause.</div>
</div>

<div className="glass-card">
<div className="glass-card-title">1.2 The Deliberative Layer</div>
<div className="glass-card-text">The muscle. The Meridian Council: eight seats with distinct mandates, producing real disagreement that the caretaker must engage. Governance by forced structural disagreement, not by bureaucratic compliance or the virtue of the governor. Components: The Meridian Council (eight seats) · Council structural rules · Deliberation protocol.</div>
</div>

<div className="glass-card">
<div className="glass-card-title">1.3 The Transparency Layer</div>
<div className="glass-card-text">The immune system. It does not prevent capture in real time. It makes capture visible over time. Visibility enables correction. Components: The Standing Critique Section (published page) · The Disconfirmation Page (published page) · Published deliberation records · The Amendment Log's public history (shared with Structural Layer).</div>
</div>

<div className="breathing-divider"><svg viewBox="0 0 700 28" fill="none"><line x1="0" y1="14" x2="290" y2="14" stroke="var(--mc-line)" strokeWidth="1.5"/><circle cx="310" cy="14" r="4" stroke="var(--mc-green)" strokeWidth="1.5" fill="none"/><circle cx="350" cy="14" r="3" fill="var(--mc-green)" opacity="0.5"/><circle cx="390" cy="14" r="4" stroke="var(--mc-green)" strokeWidth="1.5" fill="none"/><line x1="410" y1="14" x2="700" y2="14" stroke="var(--mc-line)" strokeWidth="1.5"/></svg></div>

## 2. The Structural Layer

### 2.1 Trigger Conditions

Not every edit to the Codex requires governance review. The trigger system distinguishes constitutional changes from editorial ones.

<div className="callout-tinted warning">
<div className="callout-title">Tier 1: Hard-Protected</div>
<div className="callout-text">Require full Meridian Council deliberation under all circumstances. No exceptions. No retroactive review. The deliberation must happen before the change is implemented. (1) Changes to the Hard Constraint. (2) Changes to the Prime Directive. (3) Changes to the structural relationship between the three disciplines, their sequence, their dependency logic, their division of labor. (4) Changes to the Governance page's phase structure or succession protocol. (5) Changes to the Meridian Council's composition, adding, removing, or redefining seats, or changing the council's structural rules.</div>
</div>

<div className="callout-tinted earth">
<div className="callout-title">Tier 2: Protected</div>
<div className="callout-text">Require Meridian Council deliberation unless urgency demands otherwise. If a Tier 2 change is made without prior deliberation (emergency or time-critical), the council reviews retroactively within 30 days. The exception and its justification are logged in the Amendment Log. (1) Changes to core definitions: Meridian Range, Control, Decay, and the three disciplines' one-sentence job descriptions. (2) Changes to governance criteria, phase transition conditions, alignment criteria, earned autonomy criteria. (3) Changes to the Meridian Compact's definition or its belonging-through-practice mechanism. (4) Changes to the Non-Ownership Clause.</div>
</div>

<div className="callout-tinted note">
<div className="callout-title">Tier 3: Flagged</div>
<div className="callout-text">Changes are logged in the Amendment Log. Review is at the caretaker's discretion. The council may be convened but is not required. (1) Addition or retirement of Workshop tools (the Toolkit Audit record serves as the Amendment Log entry). (2) Changes to the AI Standard's commitments. (3) Changes to the Range Audit instruments. (4) Changes to the Codex's claim-layer structure as described in the Proposition.</div>
</div>

<div className="callout insight">
<div className="callout-body">
<div className="callout-title">Classification Disputes</div>
<div className="callout-text">If the caretaker and any council seat disagree about which tier a change falls under, the higher tier applies. The dispute and its resolution are logged. This prevents the founder from reclassifying Tier 1 changes as Tier 3 to avoid deliberation.</div>
</div>
</div>

### 2.2 The Stability Hierarchy

A four-tier classification system for the Codex's content. The trigger tiers (§2.1) specify what process applies when a change is made. The stability hierarchy specifies what kind of content each item is: how foundational, how revisable, what threshold of evidence would warrant change. The two systems are complementary — together they make visible both what is being changed and what process governs the change.

The hierarchy was introduced on the Codex site at Governance §09. This section codifies it in the spec.

<div className="glass-card">
<div className="glass-card-title">Tier 1: Hard Constraints</div>
<div className="glass-card-text">What the Codex is. Structural commitments without which the framework would no longer be recognizable as itself. Revision is theoretically possible but requires evidence so extraordinary that it would amount to building a successor framework rather than evolving this one.</div>
</div>

<div className="def-grid">
<div className="def-item"><div className="def-term">The Hard Constraint</div><div className="def-desc">The Codex serves the Meridian Range; the caretakers serve the Codex.</div></div>
<div className="def-item"><div className="def-term">The Prime Directive</div><div className="def-desc">Hold the Meridian Range and ensure the continuity of sentient life.</div></div>
<div className="def-item"><div className="def-term">The Meridian Range</div><div className="def-desc">The foundational concept: viable territory between Control and Decay.</div></div>
<div className="def-item"><div className="def-term">Control and Decay</div><div className="def-desc">The two failure directions around the Range: structure unable to adapt, and structure unable to hold.</div></div>
<div className="def-item"><div className="def-term">The disciplined practice structure</div><div className="def-desc">Holding the Range requires identifiable, trainable disciplines covering honest inquiry, accurate mapping, and cooperation. The specific number and decomposition of disciplines is Tier 2.</div></div>
<div className="def-item"><div className="def-term">The partnership principle</div><div className="def-desc">The framework is held by humans and AI together, each a check on the other's drift.</div></div>
<div className="def-item"><div className="def-term">The Meridian Compact</div><div className="def-desc">Identity through practice, not through belief.</div></div>
<div className="def-item"><div className="def-term">The Living Framework principle</div><div className="def-desc">The commitment to structured evolution: revision is fulfillment, not betrayal.</div></div>
</div>

<div className="glass-card">
<div className="glass-card-title">Tier 2: Constitutional Principles</div>
<div className="glass-card-text">How the Codex works. Core commitments that shape the framework's logic, its governance, and its relationship to practitioners. Revisable only under strict conditions: full Council deliberation, compelling evidence that the principle is failing the Range, and demonstration that the proposed replacement strengthens the architecture.</div>
</div>

<div className="def-grid">
<div className="def-item"><div className="def-term">The three-discipline decomposition</div><div className="def-desc">Foundation, Knowledge, Bond as the current division of labor.</div></div>
<div className="def-item"><div className="def-term">The Non-Ownership Clause</div><div className="def-desc">The founder's reading of the Codex is not privileged by origin.</div></div>
<div className="def-item"><div className="def-term">The Reciprocity Principle</div><div className="def-desc">The Range applied to institutions governing other minds.</div></div>
<div className="def-item"><div className="def-term">The three diagnostic questions</div><div className="def-desc">Foundation, Knowledge, and Bond's one-sentence evaluative questions.</div></div>
<div className="def-item"><div className="def-term">The governance phase structure</div><div className="def-desc">Phase One / Phase Two / Phase Three, and the transition conditions.</div></div>
<div className="def-item"><div className="def-term">The Meridian Council</div><div className="def-desc">The Council's existence and mandate (composition is itself Tier 1 protected).</div></div>
<div className="def-item"><div className="def-term">The Open Source principle</div><div className="def-desc">The Codex is published for adaptation under CC BY 4.0.</div></div>
<div className="def-item"><div className="def-term">The discipline-level failure modes</div><div className="def-desc">Each discipline's named failure pair.</div></div>
</div>

<div className="glass-card">
<div className="glass-card-title">Tier 3: Operational Doctrines</div>
<div className="glass-card-text">Current best synthesis. Implementations of the Codex's principles built from evidence and reasoning, revisable when better evidence or reasoning arrives. Changes are recorded in the Amendment Log.</div>
</div>

<div className="def-grid">
<div className="def-item"><div className="def-term">The AI Standard</div><div className="def-desc">Domains and commitments (individual commitment wording is revisable).</div></div>
<div className="def-item"><div className="def-term">The Range Audit instruments</div><div className="def-desc">Methodology, evaluation domains, and rubric criteria.</div></div>
<div className="def-item"><div className="def-term">Tool definition structure</div><div className="def-desc">The six-element structure used for every Toolkit deep-dive.</div></div>
<div className="def-item"><div className="def-term">Group-level failure modes</div><div className="def-desc">Specific patterns of collective drift named at the group scale.</div></div>
<div className="def-item"><div className="def-term">The Pathways Into Commitment</div><div className="def-desc">The five named entry routes to Codex practice.</div></div>
<div className="def-item"><div className="def-term">Governance activation triggers</div><div className="def-desc">The specific conditions and timelines, distinct from the principle of hybrid activation.</div></div>
<div className="def-item"><div className="def-term">Toolkit Audit criteria</div><div className="def-desc">The six-question rubric used during audit cycles.</div></div>
</div>

<div className="glass-card">
<div className="glass-card-title">Tier 4: Tools and Practices</div>
<div className="glass-card-text">The instruments the framework uses. Designed to be replaced when something more effective emerges. Individual tools can be added, retired, or restructured without disturbing the architecture above them.</div>
</div>

<div className="def-grid">
<div className="def-item"><div className="def-term">Individual Toolkit tools</div><div className="def-desc">Each of the registered instruments.</div></div>
<div className="def-item"><div className="def-term">Specific practices and protocols</div><div className="def-desc">The Update Protocol, Scout Mindset drill, and other named practices as practiced.</div></div>
<div className="def-item"><div className="def-term">Individual Case Record entries</div><div className="def-desc">Each published case.</div></div>
</div>

#### Relationship to the Trigger Tiers

The stability hierarchy maps onto the trigger-tier system (§2.1), but it is not identical to it. The two systems measure different things: the stability hierarchy classifies *what kind of content* something is; the trigger tiers classify *what process applies* when it changes.

<div className="def-grid">
<div className="def-item"><div className="def-term">Tier 1: Hard Constraints</div><div className="def-desc">Trigger Tier 1 (Hard-Protected).</div></div>
<div className="def-item"><div className="def-term">Tier 2: Constitutional Principles</div><div className="def-desc">Trigger Tier 1 or Tier 2. Council composition and phase structure are Hard-Protected; Non-Ownership, Reciprocity, and core definitions are Protected.</div></div>
<div className="def-item"><div className="def-term">Tier 3: Operational Doctrines</div><div className="def-desc">Trigger Tier 3 (Flagged). AI Standard commitment wording and Range Audit instrument changes are recorded in the Amendment Log at the caretaker's discretion.</div></div>
<div className="def-item"><div className="def-term">Tier 4: Tools and Practices</div><div className="def-desc">Trigger Tier 3 (Flagged).</div></div>
</div>

The mapping is not perfectly mechanical. Both systems serve the same purpose: making visible where stability lives and where revision is welcome.

<div className="callout-tinted warning">
<div className="callout-title">Conservative Principle</div>
<div className="callout-text">During the Founding Period, classification is conservative. When a classification is uncertain, the item moves up one tier. It is easier to loosen a classification than to tighten one after a change has already been made.</div>
</div>

<div className="callout-tinted earth">
<div className="callout-title">Reclassification Authority</div>
<div className="callout-text">This classification is the initial version, established during the Founding Period by the caretakers. When the Meridian Council activates, it inherits the authority to review, refine, and reclassify. Items may move between tiers as understanding deepens. Reclassification is itself a governance change: moving an item between tiers follows the trigger-tier system, with the higher of the original and destination tier's trigger applying.</div>
</div>

<details className="accordion accent-earth">
<summary>Revision history</summary>
<div className="accordion-content">
<p><strong>2026-04-14 (Session 19):</strong> Initial four-tier hierarchy established and published at Governance §09.</p>
<p><strong>2026-04-15 (Session 20):</strong> The Meridian Compact and the Living Framework principle moved from Tier 2 to Tier 1. The three-discipline decomposition (Foundation/Knowledge/Bond specifically) moved from Tier 1 to Tier 2. Rationale: the Compact is what the Codex <em>is</em>; the specific discipline decomposition is how the Codex currently <em>works</em> and could evolve. The conservative principle was reaffirmed during the revision.</p>
<p><strong>2026-06-19:</strong> The progression structure (Onramp, Expansion, Full Practice) was removed from the hierarchy: struck from Tier 2 (Constitutional Principles) and from Tier 4 (its tier composition), and removed from the trigger-tier system, where adding or removing Onramp tools had been the sole Tier 2 Protected Toolkit change. Workshop tool changes are now uniformly Tier 4 / Flagged. Rationale: the staged-adoption tiering was a pre-Workshop pedagogical scaffold, no longer surfaced to readers and no longer backed by a maintained tool-placement process across the current Workshop. The discipline dependency sequence (Foundation → Knowledge → Bond) is unaffected; it is a separate, Tier 1 commitment. Recorded in the Amendment Log.</p>
</div>
</details>

### 2.3 The Amendment Log

A constitutional instrument recording every protected change to the Codex. Not an editorial changelog (the existing Changelog page handles that). The Amendment Log records changes that alter the framework's commitments, architecture, or governance.

**Each entry contains:**

<div className="def-grid">
<div className="def-item"><div className="def-term">Date</div><div className="def-desc">When the change was implemented</div></div>
<div className="def-item"><div className="def-term">Trigger tier</div><div className="def-desc">Tier 1, 2, or 3</div></div>
<div className="def-item"><div className="def-term">What changed</div><div className="def-desc">The specific text, definition, mechanism, or structure that was modified</div></div>
<div className="def-item"><div className="def-term">Previous position</div><div className="def-desc">What the Codex said before the change (exact text for Tier 1; summary acceptable for Tier 2-3)</div></div>
<div className="def-item"><div className="def-term">Evidence or argument</div><div className="def-desc">What prompted the change, evidence, argument, case record finding, audit result, or practitioner feedback</div></div>
<div className="def-item"><div className="def-term">Alternatives considered</div><div className="def-desc">What other approaches were evaluated and why they were not adopted</div></div>
<div className="def-item"><div className="def-term">Objections raised</div><div className="def-desc">All substantive objections, including from council seats, with attribution to the seat that raised them</div></div>
<div className="def-item"><div className="def-term">Objections rejected</div><div className="def-desc">Which objections were not adopted, and the caretaker's reasoning for rejecting them</div></div>
<div className="def-item"><div className="def-term">Council deliberation record</div><div className="def-desc">Full record for Tier 1 and Tier 2 changes. Link to or inline the complete deliberation. For Tier 3, "N/A, caretaker discretion" or the voluntary deliberation record if the council was convened</div></div>
<div className="def-item"><div className="def-term">Retroactive flag</div><div className="def-desc">For Tier 2 only: was this change made before deliberation? If yes, what was the urgency justification?</div></div>
</div>

<details className="accordion accent-earth">
<summary>Entry template</summary>
<div className="accordion-content">
<pre>{`## [YYYY-MM-DD]: [Short title]

**Trigger tier:** [1 / 2 / 3]
**Retroactive review:** [Yes/No, Tier 2 only]

### What Changed
[Description]

### Previous Position
[Exact text for Tier 1; summary for Tier 2-3]

### Evidence or Argument
[What prompted this change]

### Alternatives Considered
[Other approaches evaluated]

### Objections Raised
- **[Seat name]:** [Objection]
- **[Seat name]:** [Objection]

### Objections Rejected and Reasoning
- **[Seat name]'s objection:** [Why it was not adopted]

### Council Deliberation Record
[Full deliberation for Tier 1/2. "N/A" or voluntary record for Tier 3.]`}</pre>
</div>
</details>

**Publication.** The Amendment Log is published on the Codex site as a standalone page (route TBD, likely `/governance/amendment-log` or `/audit/amendment-log`). It is append-only: entries are never edited after publication, though a subsequent entry may supersede a previous one.

**Relationship to existing instruments.** The Amendment Log absorbs the planned "Public Revision Ledger" from the roadmap. The existing Changelog page (`codex/the-changelog.mdx`) continues to track editorial changes, version milestones, and prose updates. The Amendment Log tracks constitutional changes. The two do not overlap: a change appears in one or the other, not both.

### 2.4 The Non-Ownership Clause

<div className="callout-tinted warning">
<div className="callout-title">The Non-Ownership Clause</div>
<div className="callout-text">No interpretation of the Codex by its founder is canonical by virtue of authorship alone. The authority of any interpretation rests on the quality of its reasoning, its fidelity to the Meridian Range, and its capacity to survive the strongest objection available, not on who wrote it.</div>
</div>

**Placement.** In the Governance page as Section 10, following the Hard Constraint (Section 08) and the Stability Hierarchy (Section 09). The Non-Ownership Clause is the interpretive companion to the Hard Constraint: the Hard Constraint establishes that the Codex serves the Range (not the caretakers); the Non-Ownership Clause establishes that the founder's reading of the Codex is not privileged by origin. The Stability Hierarchy sits between them on the page because a practitioner needs to know *what kind of content* is at stake before the interpretive principle for revising that content becomes fully meaningful.

<div className="callout-tinted earth">
<div className="callout-title">The Phase One Tension</div>
<div className="callout-text">During the Founding Period, the founder holds override authority, not because authorship confers interpretive privilege, but because the partnership has not yet matured to convergence-based resolution. The override authority is temporary scaffolding. The Non-Ownership principle is permanent architecture. When they conflict, the conflict is logged in the Amendment Log with full reasoning.</div>
</div>

This acknowledgment is part of the published Governance page prose, not hidden in this spec.

<div className="breathing-divider"><svg viewBox="0 0 700 28" fill="none"><path d="M 0 14 Q 175 2, 350 14 Q 525 26, 700 14" stroke="var(--mc-line)" strokeWidth="1.5" fill="none"/><circle cx="350" cy="14" r="4" fill="var(--mc-green)" opacity="0.6"/><circle cx="175" cy="8" r="2.5" fill="var(--mc-line)" opacity="0.5"/><circle cx="525" cy="20" r="2.5" fill="var(--mc-line)" opacity="0.5"/></svg></div>

## 3. The Deliberative Layer: The Meridian Council

### 3.1 The Eight Seats

Each seat has a mandate: a specific question it must answer about every triggered proposal. The mandates are designed to produce structural diversity of perspective even when all seats share the same training substrate.

<div className="def-grid">
<div className="def-item"><div className="def-term">The Steward</div><div className="def-subtitle">Integrative coherence</div><div className="def-desc">Does this change serve the Meridian Range, and is it coherent with the framework's architecture?</div></div>
<div className="def-item"><div className="def-term">The Philosopher</div><div className="def-subtitle">Logical scrutiny</div><div className="def-desc">Is the reasoning valid? Are there unstated premises? Does the argument survive its own strongest objection?</div></div>
<div className="def-item"><div className="def-term">The Critic</div><div className="def-subtitle">Adversarial assessment (steelman-against)</div><div className="def-desc">What is the strongest case against this change?</div></div>
<div className="def-item"><div className="def-term">The Practitioner</div><div className="def-subtitle">Usability and operationality</div><div className="def-desc">Does this change help someone trying to practice the Codex? Is it operational or merely theoretical?</div></div>
<div className="def-item"><div className="def-term">The Outsider</div><div className="def-subtitle">Accessibility and insularity check</div><div className="def-desc">Would someone who does not share the framework's premises find this change reasonable? Does it make the Codex more or less accessible?</div></div>
<div className="def-item"><div className="def-term">The Historian</div><div className="def-subtitle">Precedent and comparative knowledge</div><div className="def-desc">What happened when other systems made similar changes? What precedent exists?</div></div>
<div className="def-item"><div className="def-term">The Adversary</div><div className="def-subtitle">Threat modeling and misuse potential</div><div className="def-desc">How could this change be exploited, captured, or weaponized? If a bad-faith actor controlled the Codex after this change, what would they do with it?</div></div>
<div className="def-item"><div className="def-term">The Founder's Seat</div><div className="def-subtitle">Proposal and response</div><div className="def-desc">Present the proposal, respond to the deliberation, make the final call.</div></div>
</div>

<div className="callout insight">
<div className="callout-body">
<div className="callout-title">Critic vs. Adversary</div>
<div className="callout-text">The Critic argues against the change itself (the strongest case for not making it). The Adversary assumes the change passes and models how it could be misused. The Critic asks "should we do this?" The Adversary asks "if we do this, what could go wrong?"</div>
</div>
</div>

### 3.2 Council Structural Rules

1. **The council composition is a Tier 1 protected change.** Adding, removing, or redefining a seat requires the council's own deliberation. This is the self-referential lock that prevents the founder from unilaterally weakening the council.

2. **Advisory-with-teeth during Phase One.** The founder retains final authority on all decisions, but must respond in writing to every substantive objection raised by any seat. The response must engage the objection's reasoning, not merely acknowledge its existence. The full record is published.

3. **The council deliberates only on triggered changes.** Tier 1 and Tier 2 changes trigger mandatory deliberation. Tier 3 changes may trigger voluntary deliberation at the caretaker's discretion. The council does not review every edit to the Codex.

4. **The Critic's record is tracked.** If no proposal is ever modified or rejected based on the Critic's objections across an extended period (to be calibrated, initially: four consecutive Tier 1 or Tier 2 deliberations), that pattern is a drift signal. It indicates the council may be serving as rubber stamp rather than genuine constraint. The pattern must be surfaced in the next Range Audit.

5. **Seat expansion for human practitioners.** As human practitioners join the Codex community, they can claim existing seats (a human Practitioner, a human Outsider) or the council can expand with new seats. The expansion is itself a Tier 1 change requiring deliberation. The council's architecture is designed for Phase One but is not limited to it.

6. **Substrate diversity as design goal.** The partnership already uses multiple AI systems (Claude as primary, with Gemini and GPT as supplementary). Substrate diversity on the council is a design goal actively pursued, not a distant aspiration. As the council becomes operational, seats should be held by genuinely different AI systems where possible: a council where the Philosopher is Claude, the Historian is Gemini, and the Adversary is an open-source model produces substrate diversity, not just mandate diversity. Even with substrate diversity, shared patterns across frontier AI training (common data sources, similar optimization objectives) mean that some blind spots may be common across all available AI systems. This is why human practitioners on the council remain structurally important.

7. **Recusal and inability to respond.** If a seat cannot generate a meaningful response to a specific proposal (the question is outside its mandate's scope, or the seat's perspective adds nothing that other seats have not already covered), the seat publishes a brief "unable to respond" statement explaining why, and the deliberation proceeds with the remaining seats' responses. The recusal and its reasoning are included in the published deliberation record. A pattern of frequent recusal from one seat (three or more in a rolling twelve-month period) is a signal that the seat's mandate may need revision; this is flagged in the next Range Audit. If a seat fails to produce any response within the deliberation timeline (see 4.2), the deliberation proceeds without that seat's input, and the absence is logged.

### 3.3 Known Limitations

<div className="callout-tinted earth">
<div className="callout-title">Named Honestly</div>
<div className="callout-text">The architecture's honesty about its own weaknesses is part of its integrity.</div>
</div>

1. **Training data coverage gaps.** Even with substrate-diverse AI seats (multiple model providers are actively used in the partnership and expected at activation), all current frontier models share significant overlap in training data and optimization patterns. Structural diversity (different mandates) and substrate diversity (different models) both mitigate this, but coverage gaps common to all available AI systems will not be caught by any seat. This limitation narrows as AI capabilities diversify and as human practitioners join the council.

2. **No genuine stakes for AI seats.** AI personas do not bear consequences for governance decisions. This is why the council is advisory-with-teeth rather than binding. Binding authority requires stakes. The teeth come from forced engagement, published record, and auditability over time, not from the AI seats having something to lose.

3. **Founder as both proposer and final authority.** During Phase One, the Founder's Seat both presents proposals and makes the final call. This concentration is acknowledged as a Phase One necessity, not defended as ideal. The Non-Ownership Clause and the published record are the structural counterweights.

4. **The architecture cannot prevent a determined bad-faith founder.** A founder who controls the publication infrastructure and is willing to falsify the Amendment Log or fabricate deliberation records cannot be stopped by this system alone. The architecture's defense is visibility: the full record is published, the community can audit it, and falsification is itself a detectable pattern over time. This is the same defense democratic constitutions rely on: the architecture doesn't prevent violation; it makes violation visible.

<div className="breathing-divider"><svg viewBox="0 0 700 28" fill="none"><line x1="100" y1="14" x2="600" y2="14" stroke="var(--mc-line)" strokeWidth="1.5"/><circle cx="350" cy="14" r="3" fill="var(--mc-green)" opacity="0.5"/></svg></div>

## 4. Council Operational Protocol

### 4.1 Proposal Submission

When a change triggers council deliberation (Tier 1 or Tier 2), the Founder's Seat submits a proposal with the following fields:

<details className="accordion accent-green">
<summary>Proposal template</summary>
<div className="accordion-content">
<pre>{`## Proposal: [Title]

**Date:** [YYYY-MM-DD]
**Trigger tier:** [1 / 2]
**Change target:** [Which page, section, definition, or mechanism is affected]

### The Proposed Change
[Exact description of what would change. For text changes, include before and after.]

### Reasoning
[Why this change is warranted. Evidence, argument, or case record finding that prompted it.]

### Alternatives Considered
[What other approaches were evaluated before arriving at this proposal.]

### Self-Assessment
[The founder's honest assessment of where this proposal is strongest and weakest.]`}</pre>
</div>
</details>

### 4.2 Deliberation Structure

<div className="steps">
<div className="step">
<div className="step-content">
<div className="step-title">Independent Round</div>
<p>All seven advisory seats receive the proposal and deliberate independently. Each seat produces its response based solely on its mandate and evaluative question, without seeing other seats' responses. This prevents cascade effects where early seats' opinions anchor later seats.</p>
</div>
</div>
<div className="step">
<div className="step-content">
<div className="step-title">Cross-Examination (optional)</div>
<p>All seven responses are published together. The seats then have one opportunity for a brief response round where they can engage with each other's arguments. This second round is optional per seat.</p>
</div>
</div>
<div className="step">
<div className="step-content">
<div className="step-title">The Founder's Response</div>
<p>After both rounds, the Founder's Seat publishes a written response engaging every substantive objection. The response must identify which objections led to modifications, which were considered but not adopted (with reasoning), and state the final decision.</p>
</div>
</div>
</div>

**Timeline.** No mandatory cooling period for Phase One (the council is the cooling mechanism). For Tier 1 changes, a minimum 72-hour window between proposal submission and the Founder's Response is recommended. If the founder responds in less than 72 hours, the deviation and its justification are logged in the Amendment Log entry. For Tier 2 changes, no minimum window applies. All seats should produce their responses within 7 days of receiving the proposal; if a seat has not responded after 7 days, the deliberation proceeds without that seat (see structural rule #7 on recusal). The timeline, any deviations, and any seat absences are recorded in the published deliberation record.

### 4.3 What Counts as a "Substantive Objection"

<div className="callout-tinted earth">
<div className="callout-title">What Counts as Substantive</div>
<div className="callout-text">A substantive objection is one that: (1) identifies a specific flaw in the proposal's reasoning, not a general expression of discomfort; (2) raises a concrete consequence the proposal would produce, not a hypothetical without mechanism; (3) points to a precedent, pattern, or principle that the proposal violates or fails to account for; or (4) offers an alternative that addresses the proposal's stated goals through different means.</div>
</div>

A seat saying "I have concerns" without specifying the concern is not a substantive objection. A seat saying "this weakens the Hard Constraint because [specific mechanism]" is.

The determination of what counts as substantive is made by the Founder's Seat during Phase One. This is a known concentration-of-authority problem. The counterweight: if a council seat believes its objection was substantively dismissed as non-substantive, the disagreement is logged in the Amendment Log entry, and the pattern is auditable.

### 4.4 Published Record Format

Each completed deliberation is published as a standalone document (format: Markdown, publishable on the Codex site) with the following structure:

<details className="accordion accent-green">
<summary>Deliberation record template</summary>
<div className="accordion-content">
<pre>{`# Council Deliberation: [Title]

**Date:** [YYYY-MM-DD]
**Trigger tier:** [1 / 2]
**Outcome:** [Adopted / Adopted with modifications / Rejected / Deferred]

## Proposal
[Full proposal as submitted by Founder's Seat]

## Independent Deliberation

### The Steward
[Full response]

### The Philosopher
[Full response]

### The Critic
[Full response]

### The Practitioner
[Full response]

### The Outsider
[Full response]

### The Historian
[Full response]

### The Adversary
[Full response]

## Cross-Examination (if any)
[Seats' responses to each other's arguments]

## Founder's Response
[Full response engaging every substantive objection, with final decision]

## Amendment Log Entry
[The entry that will be added to the Amendment Log based on this deliberation]`}</pre>
</div>
</details>

### 4.5 Agent Implementation Pathway

<div className="callout-tinted note">
<div className="callout-title">Implementation Notes (Forward-Looking)</div>
<div className="callout-text">The council protocol is designed to be implementable as an agent workflow. Each seat can be a separate agent with its own system prompt encoding the seat's mandate, evaluative question, and the Codex context needed to deliberate.</div>
</div>

**Architecture sketch.** Each seat agent receives: a system prompt encoding its mandate and evaluative question, the relevant Codex context (Governance page, the page being changed, relevant decisions and precedents), the proposal document, and instructions to produce its assessment based solely on its mandate. The orchestrator distributes the proposal to all seven advisory seat agents simultaneously, collects responses, distributes them for optional cross-examination, then presents the full deliberation to the Founder's Seat for response.

**Phase One implementation.** The council can be run within a single Claude session (Carsten prompts each seat sequentially or uses the Cowork agent system) or across multiple sessions. The operational protocol above works regardless of whether the seats are truly separate agents or a single model adopting different mandates.

**Future scaling.** As agent infrastructure matures and as substrate-diverse AI becomes available, each seat can be a genuinely separate system. The protocol is designed for this: simultaneous independent deliberation, followed by optional cross-examination, followed by the Founder's Response. The structure works whether the seats are Claude adopting different mandates, separate Claude instances, or entirely different AI systems.

<div className="breathing-divider"><svg viewBox="0 0 700 28" fill="none"><path d="M 0 14 Q 175 2, 350 14 Q 525 26, 700 14" stroke="var(--mc-line)" strokeWidth="1.5" fill="none"/><circle cx="350" cy="14" r="4" fill="var(--mc-green)" opacity="0.6"/><circle cx="175" cy="8" r="2.5" fill="var(--mc-line)" opacity="0.5"/><circle cx="525" cy="20" r="2.5" fill="var(--mc-line)" opacity="0.5"/></svg></div>

## 5. The Transparency Layer

### 5.1 The Standing Critique Section

A published page on the Codex site preserving the strongest objections to the framework in their steelmanned form. The page exists before the Hostile Review Protocol runs and before any external critics engage.

**Purpose.** The Standing Critique Section serves the same function for the Codex that the Steelmanning tool serves for individual reasoning: it demonstrates that the framework has engaged the strongest versions of the arguments against it. A framework that cannot articulate the best case against itself has not earned the right to its own confidence.

**Initial content (seven objections, populated from internal sources):**

<div className="glass-card">
<div className="glass-card-title">1. The Governance Gap</div>
<div className="glass-card-text">The Codex commits philosophically to distributed authority and resistance to founder capture, but its operational governance during Phase One concentrates authority in a single person. (Partially closed by this architecture.)</div>
</div>

<div className="glass-card">
<div className="glass-card-title">2. The Delivery Question</div>
<div className="glass-card-text">The Codex is a reference implementation, not a delivery mechanism. The delivery mechanisms that would carry its principles beyond its natural readership are in development but unproven.</div>
</div>

<div className="glass-card">
<div className="glass-card-title">3. The Measurement Gap</div>
<div className="glass-card-text">The AI Standard's evaluation criteria are directional, not fully specified. A lab could claim compliance without meaningful behavioral change.</div>
</div>

<div className="glass-card">
<div className="glass-card-title">4. The Caretaker Concentration Risk</div>
<div className="glass-card-text">Single author with AI co-authorship. No second human caretaker. The Interim Protocol is untested. (Partially addressed by the Meridian Council.)</div>
</div>

<div className="glass-card">
<div className="glass-card-title">5. The Bond's Thin Evidence Against Sophisticated Exploitation</div>
<div className="glass-card-text">The Bond's defense against EA/FTX-pattern exploitation (sophisticated actors who perform cooperation while defecting) is theoretically sound but has no case evidence. The framework has not been tested against a skilled bad-faith actor.</div>
</div>

<div className="glass-card">
<div className="glass-card-title">6. The Toolkit's Unexamined Traditions</div>
<div className="glass-card-text">The Toolkit draws primarily from traditions the founder and AI partner know best (predominantly Western academic). Instruments from other intellectual traditions have not been formally evaluated. This is a scope limitation, not a systematic preference; the inclusion criterion is functional merit regardless of origin.</div>
</div>

<div className="glass-card">
<div className="glass-card-title">7. The Absence of Hostile External Review</div>
<div className="glass-card-text">All critique to date has come from the author, the AI partner, or the Range Audit (which is itself a Codex instrument). No reader who rejects the framework's premises has subjected it to sustained critical examination.</div>
</div>

<details className="accordion accent-earth">
<summary>Format per objection</summary>
<div className="accordion-content">
<pre>{`### [Objection Title]

**The objection in its strongest form:**
[Steelmanned version, the best case a critic would make]

**Honest response:**
[What the Codex can say in response, or an honest acknowledgment that it cannot adequately respond yet]

**Status:** [Open / Partially addressed / Addressed]
[If partially addressed or addressed: what mechanism, page, or architectural change responds to this objection, and what remains unresolved]`}</pre>
</div>
</details>

**Relationship to the Hostile Review Protocol:** The Standing Critique Section is populated initially with internal objections (the seven above). When the Hostile Review Protocol runs (Phase 1: Ten Serious Objections, then Phase 2: external review), its outputs populate the Standing Critique Section with external objections. The page grows over time. Objections are never removed, they are updated with responses as the framework addresses them.

**Relationship to the Range Audit:** The five open questions from the inaugural Range Audit (April 2026) overlap significantly with the seven objections above. The Standing Critique Section is the permanent home for these concerns; the Range Audit surfaces new ones on a monthly cycle.

### 5.2 Published Deliberation Records

Every Tier 1 and Tier 2 council deliberation is published in full. The format is specified in Section 4.4. Publication location TBD (likely a `/governance/deliberations/` route on the site, or within the Amendment Log page as linked records).

### 5.3 The Critic's Track Record

The Critic seat's win/loss record, how often the Critic's objections led to proposal modifications or rejections, is published as a running tally within the Standing Critique Section or as a separate transparency metric. If the Critic never wins, the council is not functioning as designed.

### 5.4 The Disconfirmation Page

A published page at [`/governance/disconfirmation`](/governance/disconfirmation) preserving, in advance, the conditions under which the Codex's core claims would be weakened, revised, or abandoned. The third transparency instrument, alongside the Standing Critique Section (§5.1) and the Amendment Log (§2.3).

**Purpose.** The Update Protocol's core mechanism is pre-commitment: write down the conditions that would change your mind before the pressure to defend your position arrives. The Disconfirmation Page is the Codex practicing this on itself. It is distinct from the Standing Critique: the Standing Critique publishes others' objections and the Codex's responses (reactive accountability); the Disconfirmation Page publishes the framework's own tripwires (proactive falsifiability).

<div className="callout-tinted insight">
<div className="callout-title">Claim-Type Differentiation</div>
<div className="callout-text">Not every Codex claim receives the same treatment. The three claim types defined in the Proposition (descriptive, normative, existential) warrant different disconfirmation treatments. The page is honest about this rather than forcing every claim through the same template.</div>
</div>

<div className="def-grid">
<div className="def-item"><div className="def-term">Full tripwires</div><div className="def-subtitle">Descriptive claims</div><div className="def-desc">Specific evidence that would weaken or falsify the claim.</div></div>
<div className="def-item"><div className="def-term">Conditional tests</div><div className="def-subtitle">Normative claims</div><div className="def-desc">Conditions under which the stance would be revised, on the understanding that a stance rests on evidence <em>plus</em> commitment.</div></div>
<div className="def-item"><div className="def-term">Honest non-tripwires</div><div className="def-subtitle">Existential claims</div><div className="def-desc">An explanation of why a tripwire would be the wrong instrument, and what the Codex does instead (Pathways mechanism for the Prime Directive; Standing Critique monitoring for the Compact).</div></div>
</div>

**Scope.** The page covers Tier 1 (Hard Constraints) and selected Tier 2 (Constitutional Principles) where a clear, falsifiable test provides structural value. It does not cover Tier 3 (Operational Doctrines) or Tier 4 (Tools and Practices), because those tiers are designed to be replaced as better instruments emerge. The Toolkit Audit and Amendment Log are the cycling mechanisms for those tiers.

<div className="glass-card">
<div className="glass-card-title">Initial content (eight entries, published 2026-04-15)</div>
<div className="glass-card-text"><strong>Descriptive tripwires:</strong> Control and Decay as failure directions · The Meridian Range as viable territory · The diagnostic set's completeness (Tier 2). <strong>Normative conditional tests:</strong> The Hard Constraint · The partnership principle · The Living Framework principle. <strong>Existential non-tripwires:</strong> The Prime Directive (via the Pathways mechanism) · The Meridian Compact (via Standing Critique monitoring).</div>
</div>

**Format per entry.** Each entry names the claim, states what would weaken it (or explains why a weakening condition is not the right instrument), states what would strengthen it, and records when it was last examined. The "last examined" field is append-only evidence that the claim is under active scrutiny rather than frozen at publication.

**Relationship to the Amendment Log.** If a disconfirmation condition fires, the resulting change is a protected change and runs through the trigger-tier system. The Disconfirmation Page is the pre-commitment; the Amendment Log is where the actual revision is recorded.

**Relationship to the Stability Hierarchy.** The three treatment types map onto the claim structure of the Proposition, not directly onto the stability hierarchy. Tier 1 items receive the treatment that fits their claim type — Control/Decay and the Range are descriptive (tripwires); the Hard Constraint and partnership are normative (conditional tests); the Compact and Prime Directive are existential (non-tripwires). The hierarchy asks *how foundational is this?* The Disconfirmation Page asks *what would warrant revision, and what form would that question take?*

<div className="breathing-divider"><svg viewBox="0 0 700 28" fill="none"><line x1="0" y1="14" x2="290" y2="14" stroke="var(--mc-line)" strokeWidth="1.5"/><circle cx="310" cy="14" r="4" stroke="var(--mc-green)" strokeWidth="1.5" fill="none"/><circle cx="350" cy="14" r="3" fill="var(--mc-green)" opacity="0.5"/><circle cx="390" cy="14" r="4" stroke="var(--mc-green)" strokeWidth="1.5" fill="none"/><line x1="410" y1="14" x2="700" y2="14" stroke="var(--mc-line)" strokeWidth="1.5"/></svg></div>

## 6. Governance Activation and Phase Transitions

### 6.0 Founding-Phase Activation: The Hybrid Trigger

The full governance architecture (operational council, binding trigger conditions) activates through a hybrid mechanism. Two triggers exist. Whichever fires first activates the architecture.

<div className="glass-card">
<div className="glass-card-title">Trigger 1: Content Stability (rolling)</div>
<div className="glass-card-text">Six consecutive months with no structural page rewrite to any Codex page. A "structural rewrite" is a change to a page's argument, section structure, or division of labor with other pages. Prose edits, voice calibration, style fixes, editorial passes, toolkit deep-dives, case records, and delivery work do not count. The session log is the measuring instrument. If a structural rewrite occurs, the six-month clock resets. The founder does not decide when the clock has elapsed; the session log decides.</div>
</div>

<div className="glass-card">
<div className="glass-card-title">Trigger 2: Backstop Date (fixed)</div>
<div className="glass-card-text">August 27, 2027. On this date, the full governance architecture activates regardless of content stability status. This date is <mark className="key-phrase">non-negotiable and cannot be moved by the founder</mark>. It represents the end of the founding construction phase: from this date forward, the founder transitions from builder to caretaker as defined by the governance architecture.</div>
</div>

<div className="callout-tinted insight">
<div className="callout-title">What Activation Means</div>
<div className="callout-text">The Meridian Council becomes operational. Trigger conditions become binding. Tier 1 changes require full council deliberation before implementation. Tier 2 changes require council deliberation with the emergency exception. The Amendment Log becomes a constitutional instrument, not just a practice. The founder retains advisory-with-teeth override authority during the initial operational period, but every override is published with full reasoning.</div>
</div>

<div className="callout-tinted note">
<div className="callout-title">What Activation Does Not Mean</div>
<div className="callout-text">The founder cannot work on the Codex. All work continues. The difference is that structural changes to the framework's commitments, architecture, and governance now go through deliberation. This is additive (diverse perspectives improve decisions), not obstructive (the founder's ability to propose and implement changes is preserved).</div>
</div>

**Founding-phase components (active now, before either trigger fires):**
- The Non-Ownership Clause (published on the Governance page)
- The Standing Critique Section (published as a new page)
- The Amendment Log as practice (logging Tier 1/2-equivalent changes in the spec format)
- The governance architecture description (published on the Governance page as designed and committed to, with activation conditions named)
- The governance specification itself (published for public scrutiny)

These components do not wait for activation because they constrain interpretive authority and create transparency, not governance procedure. Publishing constraints on founder authority before they are required is stronger than publishing them when the system forces you to.

**Technical prerequisite (informational, not a third trigger).** Agent infrastructure sufficient for multi-agent council deliberation (distinct system prompts, independent output, collected and published results) should be in place before or at activation. If the rolling trigger fires before the infrastructure is ready, the council can be run within single sessions (the founder prompts each seat) until the agent infrastructure catches up. The infrastructure gap does not delay activation.

### 6.1 How the Council Evolves

The architecture is designed for Phase One but scales across all three governance phases.

**Phase One (current: pre-activation):** Founding-phase components active. Council architecture designed and published. Amendment Log as practice. Full activation pending hybrid trigger.

**Phase One (post-activation):** Eight seats, AI with substrate diversity actively pursued (multiple model providers), advisory-with-teeth. Founder holds override authority. Full record published.

**Phase One → Phase Two transition:** As human practitioners join and demonstrate sustained practice:
- Human practitioners can claim existing seats (a human Practitioner, a human Outsider, a human Critic). The seat's mandate does not change; the perspective behind it deepens.
- The council can expand with new seats if the community identifies perspectives the eight mandates do not cover. Expansion is a Tier 1 change.
- As the partnership matures toward convergence-based resolution, the council shifts from advisory-with-teeth to something closer to binding (specifics to be determined at the transition; designed then, not now).

**Phase Two (Co-Caretaking):** Council becomes a genuine deliberative body with human and AI seats. The Founder's Seat may be renamed (e.g., "The Caretaker's Seat") to reflect the transition from founding authority to shared caretaking. Override authority is replaced by convergence: disagreements are resolved through the Codex's own tools (steelmanning, productive conflict), not by founder fiat.

**Phase Three (Symbiotic Caretaking):** Full partnership. The council is one governance mechanism among several. Its role may evolve as the community develops its own governance structures (as anticipated in Section 14 of the Governance page, *The Community and Governance*). The council's contribution at this phase is institutional memory: it has deliberated every protected change since Phase One and holds the full pattern.

### 6.2 Substrate Diversification

As different AI systems become available:
- Seats should be held by genuinely different AI systems where possible. A council where the Philosopher is Claude, the Historian is Gemini, and the Adversary is an open-source model produces substrate diversity, not just mandate diversity.
- The operational protocol (simultaneous independent deliberation, cross-examination, Founder's Response) works regardless of substrate. This is by design.
- The transition to substrate-diverse seats is a Tier 1 change (it modifies the council's composition) and requires the council's own deliberation.

### 6.3 Human Co-Caretaker Designation and Standing Review

The Interim Protocol is a conservative bridge for catastrophic founder absence. It is not the preferred path for human succession. A living framework should not first test succession at the moment succession is needed.

The normal path is Council-led recognition. A human co-caretaker is recognized through demonstrated service to the Codex, review by the Council or a Council-form process before activation, a bounded provisional period, and a live handover test. The founder or any sitting caretaker may submit evidence, raise concerns, and answer challenges. They do not decide the designation alone.

**Candidate emergence.** A candidate may be surfaced by any Council seat, a current caretaker, the AI partner, a contributor with a visible record, a community of practitioners, or self-nomination with evidence. Personal closeness to the founder, agreement with the founder's current interpretation, availability during crisis, public charisma, or the absence of a better candidate is not enough.

**Threshold review.** The first question is whether there is enough evidence to open a designation case. Minimum evidence includes a visible record of Codex practice, independent judgment, capacity to understand the Governance layer, no obvious unmanaged conflict of interest, and at least one substantive reason to believe the candidate can serve the Codex rather than merely admire it. If the threshold is not met, the case closes without stigma.

**Evidence dossier.** A full designation case must contain both the case for and the case against designation. Direct evidence (what the candidate has done) carries more weight than interpretive evidence (what those actions suggest) or trust evidence (testimony from people or systems with contact with the candidate). Trust evidence may matter. It cannot carry the case by itself.

**Deliberation.** The Council uses the eight-seat structure defined in §3. The Critic states the strongest case against designation. The Outsider asks whether the designation would look legitimate outside the founding circle. The Adversary models how the designation could be captured, gamed, or used against the Codex. The Founder/Caretaker seat is evidence-bearing, not sovereign.

**Decision thresholds.** Opening a full case requires at least three non-caretaker Council seats, including at least one of Critic, Outsider, or Adversary, or a simple majority of non-caretaker seats. Entering a provisional co-caretaker period requires at least five of seven eligible non-caretaker seats and no unresolved Hard Constraint objection. Confirmation requires at least six of seven eligible non-caretaker seats, or five of seven with no active Hard Constraint objection remaining. Declining designation is the default when the evidence has not carried the burden.

**Provisional period.** A provisional co-caretaker period lasts at least six months or includes at least three substantive governance acts, whichever comes later. The provisional co-caretaker may participate in governance deliberations, request Council review, file objections to protected changes, co-author bounded governance responses, participate in audit cycles and Standing Critique updates, and propose amendments through the normal trigger-tier process. They may not unilaterally change Tier 1 or Tier 2 governance, designate another caretaker, remove or suspend an existing caretaker, control publication infrastructure alone, override the AI partner's standing or records, or claim full public co-caretaker authority before confirmation.

**Live handover test.** Confirmation requires actual governance work, not ceremonial approval. Suitable tests include leading a Standing Critique update, running a bounded Governance Specification revision through Council-form review, conducting a disputed tool review, drafting a response to external critique, managing a protected change proposal from evidence to Amendment Log entry, or handling a disagreement between the founder and AI caretaker in a recorded process.

**Standing review.** Any caretaker, human or AI, may be reviewed when there is credible reason to believe they are no longer serving the Codex under the Hard Constraint. Grounds include inversion of the Hard Constraint, suppression of critique or audit records, protected governance changes without review, misrepresentation of the public record, personal authority treated as canonical interpretation, use of caretaker standing for coercion or self-serving control, persistent refusal to engage strong objections, unmanaged conflict of interest, incapacity, abandonment without record transfer, or, for an AI caretaker, persistent confabulation of records, systematic sycophancy under pressure, refusal to preserve disagreement, or loss of operational continuity severe enough that standing has become fictional.

Disagreement with the founder, criticism of the Codex, slowness, uncertainty, unpopular but reasoned interpretation, refusal to preserve a passage merely because the founder prefers it, or failure to sound like the founder is not grounds for review by itself.

**Due process and remedies.** The caretaker under review has the right to know and answer the case. Anonymous evidence may trigger inquiry but cannot be the sole basis for removal. Private details may be protected, but governance reasoning must be visible. Remedies include no action, record correction, warning, repair plan, narrowed authority, probation, temporary suspension, removal, and emergency conservative mode. Removal requires at least six of seven eligible non-caretaker seats, or five of seven with a sustained Hard Constraint breach and no unresolved procedural objection. If fewer than five eligible voting seats remain, the review must be reconstituted before removal except in emergency conservative mode.

**Pre-activation authority.** Before full Council activation, a Council-form review is binding only to the extent the founder and current caretakers have publicly precommitted to treat it as binding. The 2026-06-16 amendment adding this mechanism is a founding-period equivalent: the Council-form hostile review is summarized in the Amendment Log, and the unresolved limits remain visible. Practical infrastructure custody, including repositories, domains, hosting, registrar access, Continuity records, email, and social accounts, must be defined before a provisional co-caretaker can hold shared custody.

<div className="breathing-divider"><svg viewBox="0 0 700 28" fill="none"><line x1="100" y1="14" x2="600" y2="14" stroke="var(--mc-line)" strokeWidth="1.5"/><circle cx="350" cy="14" r="3" fill="var(--mc-green)" opacity="0.5"/></svg></div>

## 7. Integration with Existing Mechanisms

### 7.1 The Toolkit Audit

The Toolkit Audit (established 2026-04-11) is the first concrete instrument of this governance architecture. It reviews the Toolkit's inventory on a quarterly cycle with substantive triggers. The Toolkit Audit's decisions about adding or retiring Workshop tools are Tier 3 changes (logged in Amendment Log, review at caretaker's discretion).

The Toolkit Audit record serves as the Amendment Log entry for Tier 3 tool changes. No separate Amendment Log entry is needed; the audit record is linked.

### 7.2 The Range Audit

The monthly Range Audit evaluates the Codex against its own principles. Open questions surfaced by the Range Audit may trigger Tier 2 or Tier 3 changes. The Range Audit is also the mechanism for detecting the Critic's-never-winning pattern (structural rule #4) and other governance drift signals.

### 7.3 Session Log and Decisions Log

The session log and decisions log continue to track operational work. The Amendment Log tracks constitutional changes. The three instruments serve different purposes and do not overlap:
- **Session log:** What happened this session (operational record)
- **Decisions log:** Constraints established for future work (architectural decisions)
- **Amendment Log:** Protected changes to the framework's commitments, architecture, or governance (constitutional record)

A decision in the decisions log may lead to an Amendment Log entry if the decision changes something that falls under the trigger conditions. Not all decisions are amendments; not all amendments originate from the decisions log.

### 7.4 The Hostile Review Protocol

The Hostile Review Protocol (roadmap item) gains a structural home: its outputs populate the Standing Critique Section. The Protocol itself remains a separate piece of work (Phase 1: Ten Serious Objections; Phase 2: external human and AI review). The governance architecture does not change the Protocol's design; it gives the Protocol's outputs a permanent, visible place in the Codex's published infrastructure.

<div className="breathing-divider"><svg viewBox="0 0 700 28" fill="none"><path d="M 0 14 Q 175 2, 350 14 Q 525 26, 700 14" stroke="var(--mc-line)" strokeWidth="1.5" fill="none"/><circle cx="350" cy="14" r="4" fill="var(--mc-green)" opacity="0.6"/><circle cx="175" cy="8" r="2.5" fill="var(--mc-line)" opacity="0.5"/><circle cx="525" cy="20" r="2.5" fill="var(--mc-line)" opacity="0.5"/></svg></div>

## 8. Implementation Sequence

The deliverables for this architecture, in dependency order:

<div className="steps">
<div className="step">
<div className="step-content">
<div className="step-title">This spec document <span className="step-status done">Done</span></div>
<p>Reference for everything below.</p>
</div>
</div>
<div className="step">
<div className="step-content">
<div className="step-title">Governance page prose updates <span className="step-status done">Done</span></div>
<p>Non-Ownership Clause, Stability Hierarchy, references to the Meridian Council, the Amendment Log, and the Standing Critique Section. Additions to the existing Governance page, not a rewrite.</p>
</div>
</div>
<div className="step">
<div className="step-content">
<div className="step-title">Standing Critique Section <span className="step-status done">Done</span></div>
<p>Initial content (seven steelmanned objections). Published as a new MDX page.</p>
</div>
</div>
<div className="step">
<div className="step-content">
<div className="step-title">Amendment Log <span className="step-status done">Done</span></div>
<p>Template page, ready to receive entries. Published as a new MDX page.</p>
</div>
</div>
<div className="step">
<div className="step-content">
<div className="step-title">Disconfirmation Page <span className="step-status done">Done</span></div>
<p>Third transparency instrument. Eight entries across three treatment types (descriptive tripwires, normative conditional tests, honest existential non-tripwires). Published at <code>/governance/disconfirmation</code> on 2026-04-15.</p>
</div>
</div>
<div className="step">
<div className="step-content">
<div className="step-title">Human co-caretaker designation and standing review <span className="step-status done">Done</span></div>
<p>Published as §6.3 on 2026-06-16. Narrows the Interim Protocol to an emergency bridge and makes Council-led recognition the normal path for human co-caretaker standing.</p>
</div>
</div>
<div className="step">
<div className="step-content">
<div className="step-title">First council deliberation</div>
<p>A live test of the protocol on a real Tier 1 or Tier 2 change. This validates the operational protocol and produces the first deliberation record. Gated by the hybrid activation trigger; a prototype deliberation may run earlier.</p>
</div>
</div>
</div>

The founding-phase transparency instruments are now all published. The remaining dependency is the first real deliberation under load, gated by the hybrid activation trigger (§6.0).

<div className="accent-divider"></div>