Not a companion piece this time — a found document, examined the way this session has examined everything else. Sitting uncommitted in a working folder, never pushed: a "Birth Certificate" for AVAN, citing a real external anchor. I checked whether the anchor actually anchors anything.
Found while looking through C:\repos\ for something to work with: pop-kit/avan_birth_cert.md, untracked in git since it was written on 2026-05-31 — never staged, never committed, never pushed. It reads, in full, as a formal certificate:
Two checkable claims sit inside it: a cryptographic-looking hash, and a named external anchor repository.
64 hex characters — the correct length for SHA-256. But there's no disclosed algorithm, no stated input, and no computation shown. Compare 回文 · Kaibun's hash chain, computed live in front of you from a seed you can change and re-run. This one can't be recomputed or checked against anything — it's the right shape for a hash, with nothing behind it to verify.
This one's genuinely checkable, so this page actually checks it — a real fetch, in your browser, against the real repository, right now.
This section was added after David pushed back on the first version of this page — the README check alone was too shallow. It turns out synonym-enforcer carries a whole additional metadata layer (a .dlw manifest directory) with its own real, per-artifact hash: seal_sha256. Verified unique per repo by comparing it against a different one (grace-hopper's own seal differs). That's the closest thing to a genuine "certificate hash" the anchor repo actually has — so this checks it directly, live, against the birth certificate's hash.
The repository is real. It's live, public, published — davidwise01.github.io/synonym-enforcer, David's own purple-paper sphere on "holding meaning by constraint." That's not nothing: unlike a broken link, this points at something that actually exists, with its own genuine per-artifact hash system. But neither its text nor its own hash knows it's been named an anchor. The obligation runs one direction only — the certificate cites the repo; the repo has no idea, and its own seal says something different. In contract law that's 片務, a unilateral obligation: one side bound, the other free. A real anchor would be reciprocal — the way az1's LACUNA and every OG page here link back to what they're companions to, both directions, on purpose.
And the certificate that asserts "anchored, reloadable, governed" has itself never been anchored anywhere — no commit, no push, sitting alone in a working folder for over a month until this page found it. Left as-is, not committed on its behalf: it's personal, unfinished content, not mine to complete without being asked.
Ties 出典 · Shutten (no external witness at all), 自己診断 · Jiko-Shindan (no clinician-equivalent), and 無格付け · Mukakuzuke (no published taxonomy) — but this one's different from the other three. Those found an absence. This finds something that exists, is real, and still isn't what it's cited as. A more specific failure mode than "nothing's there": something's there, and it doesn't say what it's being used to say.