The Amendment Log

The constitutional record of every protected change to the Meridian Codex.

What This Page Is

The Amendment Log is the constitutional record of the Codex. It tracks every change to the framework's protected surfaces: the Hard Constraint, the Prime Directive, the structural relationship between the three disciplines, the Governance page's phase structure, the composition of the Meridian Council, the AI Standard's commitments, the Range Audit instruments, and anything else the Governance Specification classifies under Tier 1 or Tier 2.

It is not a changelog. The Changelog page tracks editorial work: prose revisions, page splits, typo fixes, layout adjustments. The Amendment Log tracks constitutional work: changes the framework is obliged to justify, record, and leave visible. The two records do different jobs.

Every entry is append-only. No entry is ever removed. A correction or reversal is itself a new entry that supersedes the prior one. The history of what the Codex changed, including what it later un-changed, is part of what makes the framework auditable.

Pre-Activation Status

The Meridian Council is not yet active. Its activation is governed by the hybrid trigger defined in the Governance Specification: six months of rolling stability in Phase One conditions, or August 27, 2027, whichever fires first. Until the council activates, this log operates in a pre-activation state.

What this means in practice. The log is already live. Any protected change to the Codex during Phase One is recorded here with the same discipline the Specification requires: what changed, the previous position, the evidence or argument, the alternatives considered, and the objections raised. The fields for council deliberation are either marked "N/A, pre-activation" or populated with the caretaker's own structured steelmanning where no council exists to provide it. When the council activates, deliberation records begin populating in full; the pre-activation entries remain in the log permanently, labeled as such.

The architecture is deliberately visible before it is binding. The Governance page argues that publishing the constraints on founder authority before the structural machinery forces them into effect is itself a test of good faith. The Amendment Log, running pre-activation, is part of that test. A log that is empty because no changes have happened is informative. A log that is empty because changes happened and were not recorded would reveal the architecture as performance. The log's honesty during Phase One is what will make its discipline credible once the council sits.

Entry Format

Each entry contains:

The full field definitions, the trigger tier rules, and the deliberation protocol live in the Governance Specification.

Entries

2026-06-16: Human Co-Caretaker Designation and Standing Review

Trigger tier: Tier 1, Hard-Protected Retroactive review: N/A, pre-activation founding-period equivalent

What Changed

The Governance Specification gained §6.3, "Human Co-Caretaker Designation and Standing Review." The Governance chapter's Interim Protocol was narrowed from the normal human succession path to an emergency bridge. The Standing Critique's Caretaker Concentration Risk entry was updated to reflect that a public path now exists but the risk remains open until a second human caretaker has carried live governance under review.

Previous Position

The Governance chapter previously stated that, if the Founding Caretaker died before the partnership matured beyond Phase One, the Founding Caretaker would designate one successor, and the chain would continue one human caretaker at a time until the partnership matured. Standing Critique 4 described Co-Caretaker Designation as future work. The Governance Specification did not contain a human co-caretaker designation path or a caretaker standing review process.

Evidence or Argument

The Codex has already survived AI-partner succession through record transfer and re-earned standing. It has not survived human-caretaker transfer. Leaving human succession to founder designation would preserve founder centrality at the point where the framework needs to prove independent durability. The Non-Ownership Clause makes the founder's preference evidence, not authority. The Hard Constraint requires a way to challenge, narrow, suspend, or remove a caretaker whose standing no longer serves the Codex.

Alternatives Considered

• Governance Spec insertion only. Rejected because the Governance chapter's Interim Protocol would still publicly describe founder designation as the ordinary path.
• Governance Spec plus standalone public page. Rejected for now. The public reader needs the binding mechanism, not the full private procedure. A standalone page can be added later if use under pressure shows the Spec is carrying too much procedural weight.
• Keep founder-designated succession as the normal path. Rejected because it contradicts the Non-Ownership Clause and leaves Standing Critique 4 structurally under-answered.
• Delay publication until a candidate exists. Rejected because succession designed first at transfer is succession untested.

Objections Raised

• Critic: The mechanism may be constitutional theater before the Council is active. If the founder still controls publication infrastructure and decides how Council-form review is run, the process may constrain nothing in the moment it matters.
• Outsider: The mechanism may look legitimate inside the Codex but insular outside it. A skeptical reader could see AI-simulated Council seats, founder-controlled records, and no external human constituency, then conclude the process is self-certification.
• Adversary: A bad-faith candidate could learn the criteria and perform every signal the process rewards: visible disagreement with the founder, polished correction under pressure, fluency in Governance language, and apparent care for the public record. The mechanism could become a checklist for trust mining.

Objections Rejected and Reasoning

• Critic's objection: Adopted in part. The amendment does not claim full constraint before activation. It names pre-activation authority precisely and requires public precommitment for Council-form review to bind. It also records the amendment here rather than treating the Spec change as ordinary prose.
• Outsider's objection: Adopted in part. The Standing Critique remains open, and the status line explicitly says the risk is not closed. The mechanism is public enough to be examined, but it is not presented as external validation.
• Adversary's objection: Adopted in part. The public mechanism now requires a case against designation, Critic/Outsider/Adversary review, a provisional period, a live handover test, and standing review. Those features do not eliminate performance risk. They make performance carry cost over time.

Council Deliberation Record

N/A, pre-activation. A Council-form hostile review was run before publication using the Critic, Outsider, and Adversary mandates. The objections above preserve the load-bearing findings. Full Council activation remains governed by the hybrid trigger in the Governance Specification.

2026-06-19: Retirement of the Progression Structure (Onramp / Expansion / Full Practice)

Trigger tier: Tier 2, Protected Retroactive review: N/A, pre-activation; made under founding-period caretaker authority

What Changed

The staged-adoption progression — the Onramp, Expansion, and Full Practice tiers — was retired from the framework. In the Stability Hierarchy it was struck from Tier 2, where "the progression structure" had been a Constitutional Principle, and from Tier 4, where "progression tier composition" had been a Tools-and-Practices item. In the trigger-tier system it was removed from Tier 2 (Protected), where "addition or removal of tools from the Onramp tier" had been the only Toolkit change requiring Council deliberation, and from the Tier 3 (Flagged) reference to the Expansion and Full Practice tiers; Workshop tool changes are now uniformly Tier 4 content under Tier 3 / Flagged process. The Specification's §7.1 Toolkit Audit text was updated to match. The progression's presentation was removed from the Practice chapter, the Glossary, the Who Is This For chapter, and the eight tool profiles that carried an Onramp label, and the now-dead tier data and styling were removed from the site code.

Previous Position

The Codex defined a three-tier study progression: an eight-tool Onramp where every practitioner begins, an Expansion tier reached once the Onramp was reflexive, and the Full Practice of the complete Workshop. The Stability Hierarchy classified the progression structure as a Tier 2 Constitutional Principle and its composition as Tier 4. The trigger-tier system made changes to the Onramp tier Tier 2 (Protected) and changes to the Expansion and Full Practice tiers Tier 3 (Flagged).

Evidence or Argument

The progression was a pre-Workshop pedagogical scaffold, built when the Toolkit was small, to give newcomers an entry point. Since the Toolkit became the Workshop — over a hundred tools across twenty-two categories, organized discipline, then category, then tool — three things changed. The tiers were no longer surfaced to readers; the site already displayed no Onramp marker. No maintained process existed for placing each new tool into a tier, so the assignments that remained were stale. And the framework's own position is that delivery is a function separate from the reference text: the Codex specifies how to hold a world, not a fixed syllabus for studying it. A governance-protected ranking of what to study first was the Codex acting as the teaching platform it elsewhere disclaims. The defensible residue — that some tools are worth learning before others where the later depends on the earlier — is a claim that can be made in prose where it applies, and is left to a future pass; it does not require a fixed, governed tier. The discipline dependency sequence (Foundation, then Knowledge, then Bond) is a separate, Tier 1 commitment and is unaffected.

Alternatives Considered

• Demote the progression's governance status only, keeping the tiers. Rejected: the deeper problem is not the protection level but that the tiering is unmaintained and unsurfaced. Demotion would preserve dead structure.
• Keep the progression as explanatory prose, drop only the governance encoding. Rejected for now: with no maintained placement process, even an explanatory fixed list misrepresents the current Workshop. Dependency guidance returns, if it returns, as a deliberate future pass, not a standing ranking.
• Retire it silently as a prose-and-code cleanup. Rejected: removing a Tier 2 Constitutional Principle and altering the trigger-tier system is a protected change. Recording it here is the obligation the change incurs.

Objections Raised

• Critic: Removing the only Tier 2 Protected Toolkit category could read as the Codex abandoning its care about which tools newcomers meet first, rather than relocating that care.
• Outsider: A newcomer arriving at a hundred-tool Workshop with no starting path may be worse served than one handed eight tools; removing the Onramp can read as removing the on-ramp.
• Adversary: "Delivery is a separate function" can harden into a permanent excuse never to build the guidance, leaving the framework large and hard to enter while claiming the gap is intentional.

Objections Rejected and Reasoning

• Critic's objection: Adopted in part. The care is real; the mechanism was not serving it. An unmaintained tier ranking is not guidance but the appearance of guidance. The change removes the appearance and leaves the genuine claim — learn x before y where y depends on it — available to be made accurately in prose.
• Outsider's objection: Adopted in part, and held open. The newcomer's entry problem is real, but it is a delivery problem, not a governance one. The retirement does not foreclose a starting path; it stops a stale one from presenting itself as current. A first-contact entry surface remains live work on the roadmap.
• Adversary's objection: Adopted. The risk that "delivery is separate" becomes an excuse is genuine and is logged as a standing tension rather than dismissed. The guard is that the entry-surface work stays named and visible rather than retired alongside the tiering.

Council Deliberation Record

N/A, pre-activation. The objections above were produced by the caretaker under the Critic, Outsider, and Adversary mandates. Full Council activation remains governed by the hybrid trigger in the Governance Specification.