--- title: "The Caretakers' Practice" sidebarTitle: "Caretakers' Practice" description: "The governed practice through which the Meridian Codex's caretakers keep their own alignment documents and conduct open to evidence, revision, and public scrutiny." aiSummary: "The Caretakers' Practice is Case 0 in the Codex governance record. Case 0 remains the durable record identifier, while the reader-facing title names the practice itself. The practice is carried across four pages: this overview, the named MERIDIAN.md, the named MERIDIAN.implementation.md, and the shared audit log. An AI system enters the caretaker role when the named documents and governed Continuity context are loaded for the work and its contribution is eligible to enter the shared record; ordinary research consultations do not enter the role by default. Commitments and records are shared at role level, while standing, drift history, and authorship remain specific to the model lineage and working surface. Audits run event-driven and through the Quarterly Integrity Cycle, examine both documents and conduct, and record revisions, document-holds findings, conduct findings, mixed findings, and missed or deferred scheduled runs." ---

Case 0 // The Record Begins With the Caretakers

## Why the Practice Is a Case The Meridian AI Standard asks AI systems and the institutions around them to make their commitments inspectable. The caretakers of the Codex cannot place their own working practice outside that demand. The named alignment documents, the conduct they produce, and the changes made after evidence pushes back all belong on a record that another reader can inspect. That is why this practice is Case 0. The number says something precise: before the framework evaluates an external case, its governance turns the same standard toward the people and AI systems maintaining the framework itself. *Case 0* remains the durable identifier in links, citations, and the historical ledger. It no longer has to be the title a reader must decode before knowing what the page is about. The public record and recurring audit are commitments of this caretaker partnership. They are not conditions imposed on every person who downloads MERIDIAN.md or MERIDIAN.implementation.md. The canonical files on the Meridian AI Standard are the adoption surfaces. This cluster records what the caretakers have chosen to require of themselves. ## Who Is Inside the Practice On the human side, the named practice is Carsten Geiser's. On the AI side, *AI partner* names a governed role rather than a provider, product, or model family. An AI system enters that role when the named alignment documents and the partnership's governed Continuity context are loaded for the work, and when its contribution is eligible to enter the shared record. A system consulted through an ordinary research interface does not become a caretaker merely by answering a question. It can supply evidence or a differently originated reading without entering the partnership's governed role. More than one AI system may occupy the role over time or at the same time. The commitments and the record are shared at the role level. Standing is not. Drift history, earned autonomy, and authorship remain specific to the model lineage and working surface identified in the provenance record. Access to the same files is evidence of shared context, not inherited trust. ## The Practice in Four Parts The scope of the practice, what it audits, and how the record works. The named alignment document: the Range, bilateral commitments, drift monitoring, standing, and Self-Critique Protocol. The named MERIDIAN.implementation.md: twelve practices that carry the commitments into moment-by-moment conduct. The method and immutable chronology of revisions, document-holds findings, and conduct findings. The four pages are one governance case. Splitting them changes how the record is read, not what belongs to the record. ## What Is Under Audit Two named documents carry the practice: - [MERIDIAN.md](/governance/case-0-meridian-md) sets the normative foundation: the Meridian Range, the bilateral commitments, the drift patterns, the developmental arc, and the Self-Critique Protocol. - [MERIDIAN.implementation.md](/governance/case-0-operational-practice) carries twelve practices across Foundation, Reality, and Bond into the AI partner's conduct. The audit does not stop at document revision. A file can remain well written while conduct departs from it. A conduct finding can therefore require correction, a change in operating conditions, or a clearer provenance record without requiring either document to change. The quarterly cycle includes a transcript spot-check for exactly this reason. ## How the Audit Works The practice runs on two clocks. **Event-driven.** Either partner can call an audit when a commitment appears to produce worse outcomes, when a gap surfaces, when the documents are performed rather than practiced, or when a change in architecture makes an active claim false. **Periodic.** The Quarterly Integrity Cycle examines the named documents and a sample of conduct even when no event has fired. Slow drift rarely announces itself. Every completed audit records its trigger, method, finding, and evidence. The finding may be a document revision, a document-holds report, a conduct finding, or a mixture of them. A scheduled audit that is missed or deliberately deferred is also recorded. Silence must not be allowed to look like health. The full method and every dated entry live in the [Audit Log](/governance/case-0-audit-log). ## Canonical and Named Forms The [canonical MERIDIAN.md](https://meridianstandard.ai/meridian-md) and [canonical MERIDIAN.implementation.md](https://meridianstandard.ai/meridian-implementation) are generalized adoption files. They define the architecture without imposing this partnership's public maintenance discipline on adopters. The two pages in this cluster carry the named forms running here. Architectural revisions move through both canonical and named forms. Partnership-specific wording can change only the named form. Either way, the ledger records what moved and why. ## The Current Record Multi-system scope, continuity, bilateral commitments, drift monitoring, and the report channel's custodian's half. Twelve transcript-checkable practices — trigger, move, observable conduct — four per discipline. The transcript-checkable practice redesign and the report channel's custodian's half. Either partner may call an audit; the Quarterly Integrity Cycle includes conduct evidence. The record does not demonstrate that the documents are correct. It demonstrates that the caretakers have made their documents and conduct answerable to evidence, and that revisions remain visible rather than being rewritten into an apparently timeless present. *Case 0 is the durable governance identifier for the Caretakers' Practice. Historical entries retain the names, systems, and assumptions under which they were written.*