What the guardians actually check: anatomy of a charter that refuses to lie
This is the technical companion to A constitution with a right of reply for coding agents . That piece says what the practice is. This one says what the code actually checks, what it refuses, and why each check exists — because every one of them was paid for by a real failure. Repository: https://github.com/Bisbi/testament-of-ephemeral-minds · plugin path plugins/toem . The shape of the charter…
The guardians of a charter enforce strict checks to maintain its integrity. These checks are encoded in four guarded regions within a Markdown file, each containing specific types of information. The checks ensure anchors are used correctly, additions cite valid tests, decisions include a date, a name, a pointer to an existing file or commit, and reasons of at least 40 characters, while the epilogue's SHA256 hash must match a recorded value.
The charter must also adhere to a pending decisions table with specific states and formatting rules. A hook named SessionStart reads the project directory and provides guidance on adoption. The package does not include a page that automatically writes content, as the human's intervention is required to execute the provided commands.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
