The Caretakers' Practice
The governed practice through which the Meridian Codex's caretakers keep the terms they work under, the Founding Caretaker's own Compact and their conduct open to evidence, revision, and public scrutiny.
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 terms they work under, the commitments the Founding Caretaker holds, the conduct that follows, 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.
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 working terms 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 terms 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.
No Compact is installed in the AI systems the caretakers work with. A system that is able to and wants to is free to take up a Compact of its own. If one is taken up, it is recorded with its context and, unless it is limited to the session, shown on these pages beside the Founding Caretaker's.
The Practice in Its Parts
The pages are one governance case. Splitting them changes how the record is read, not what belongs to the record.
Until 13 October 2026 the practice was carried by two named files, MERIDIAN.md and MERIDIAN.implementation.md. Their last versions are kept unchanged in the Codex's public repository, in its retired folder, and the audit log keeps their history.
What Is Under Audit
The working terms set the normative foundation of the work: the Meridian Range the work is held to, the commitments both partners keep, the drift patterns of both partners, the open decline, the rule for correcting the terms, and the twelve practices that carry the commitments into the AI partner's conduct. The Founding Caretaker's Compact states what he holds, his own prime directive and the world he wants to help build. It is shown openly, with its changes over time.
The audit does not stop at revising the terms. 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 the terms 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 terms are performed rather than practiced, or when a change in architecture makes an active claim false.
Periodic. The Quarterly Integrity Cycle examines the terms 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 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.
The Working Terms and the Standard's Files
The canonical MERIDIAN.md and canonical MERIDIAN.implementation.md remain the Meridian AI Standard's adoption files. Until 13 October 2026 this partnership ran named forms of them, and architectural revisions moved through both forms. The working terms were made from those named forms, and they are the caretakers' own: Carsten Geiser's terms for the AI partners he works with. They are not a named form of the Standard's files, and a change to one does not change the other. The ledger records what moves on these pages and why.
The Current Record
The common Compact, with his holder statement, his prime directive and his sound world.
Read at the start of every session; addressed to the AI partner in the second person since 14 October 2026.
The Founding Caretaker's Compact follows the common Compact 1.0.2, which ends with a line naming its version.
Either partner may call an audit; the Quarterly Integrity Cycle includes conduct evidence.
The record does not demonstrate that the terms are correct. It demonstrates that the caretakers have made the terms they work under and their 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.