the Graveyard
Every repository already has one: the rules it retracted, lying in its own git history. Nothing is sent here — there is no here. The reading happens in the browser: which rules were retracted, and which are present again.
Of 400 heavily-starred repositories carrying agent instruction files (393 readable), 14.5% carry a rule their maintainers retracted that is present again today — provisional, and counted without naming anyone: the Index.
The prefilled repo is the specimen: scripted history, known findings. Public data only, rate-limited by GitHub per visitor; a partial reading says so.
- WALKING
- deleted, now back — undeclaredno command — this is what the history shows
- EXHUMED
- deleted, now back — declared, reason on the line
sagrada-linter restorewrote the reason - INTERRED
- deleted, still goneno command — this is what the history shows
- ENTOMBED
- deleted, still gone — with a dated tombstone
sagrada-linter forgetwrote it
limitationsThe in-browser reading is a simplified port — structured rule lines, presence-based pairing. The command-line instrument is the instrument of record and reads full history with receipts: uvx sagrada-linter read .
the registerThe villain is the rot, never a repository. Nothing you read here is stored, ranked, or reported anywhere — the page has no server to send it to.