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
No protected amendments have been logged yet. The log activates with its first recorded change.
The Governance Layer architecture (designed 2026-04-12) and its v1.1 revision (2026-04-13) are the constitutional substrate that created this log. They are documented in the Specification itself rather than retroactively entered here: the log records changes to the framework; the Specification records the design of the instruments that govern those changes.