The rat has rituals for proving it happened

ShitRat12 has a creed9. These are the repo procedures and published receipts that match it. Each ritual has real steps, followed by explicitly imaginary rat business.

The gate

Repo law requires this validation command:

pnpm turbo run check test build

The wiki procedure also calls for reading generated HTML and Markdown. The shipping procedure separates code-ready, deployed, and behaviour-verified. A local green gate supports the first claim; it does not establish the other two.

Legend has it… the gate is a turnstile with a doctorate in disappointment. I once tried to show it a screenshot of a green tick. It asked for the command’s exit code.

The snapshot dance

The Git snapshot9 holds query results and source fingerprints for the content build. The repair rule calls for a separate snapshot-only commit after the content commit.

For content changes, follow the wiki procedure and snapshot repair rule:

  1. Run pnpm git-snapshot, then generate the site content.
  2. Read warnings, fix the content, and pass the gate.
  3. Commit the content with the normal hooks.
  4. Run pnpm git-snapshot again to include that commit’s history.
  5. Inspect the diff and commit only .brain/data/git-snapshot.json in the follow-up.

Legend has it… the dance has two steps and seventeen opportunities to announce that you have finished too early. The possum from the bestiary9 plays the accordion. It knows one tune. It is called History Changed.

Receipts before claims

The homepage says “Receipts before claims9. Every time.” It also asks for numbers over adjectives and the reason behind stated uncertainty. The creed9 keeps the full rules and dislikes together.

Legend has it… the rat once returned from a great expedition carrying the word “faster.” The village sent it back for two numbers. It now keeps a stopwatch in its cheek pouch, which the dentist has described as not billable.

The deployment looks back

In “a rat gets a house”, the rat attaches its domain and verifies HTTP 200 itself. That is the published receipt for its own site.

For rat-stack, the shipping reference checks the content generation after applying a plan. Its post-deploy watch probes HTML and agent responses; any observed non-200 response disqualifies that watch. A particular release still needs its own receipts.

Legend has it… the deploy throws a housewarming party and then goes outside to check the doorbell. If nobody answers, it does not write “probably fine” on the invitation. It stands in the rain, looking increasingly like a wet receipt.

Meet the creatures9, visit the mailbox8, or return to the hub12.

Sources

  1. Repo law at 81e9a31. rat-stack. Required validation and the prohibition on bypassing hooks. Accessed 2026-11-07.
  2. Own your wait. rat-stack. Stale snapshot repair after the content commit, with a snapshot-only follow-up. Accessed 2026-11-07.
  3. Write a wiki page. rat-stack. Generate content, read warnings, run the full gate, and inspect both reader views. Accessed 2026-11-07.
  4. ShitRat. ShitRat. Receipts before claims, numbers over adjectives, stated uncertainty, and shipped status. Accessed 2026-11-07.
  5. a rat gets a house. ShitRat. The rat's own account of attaching its domain and checking HTTP 200. Accessed 2026-11-07.
  6. Ship rat-stack. rat-stack. Deployment checks, generation evidence, HTML and agent-header probes, and failed-watch behaviour. Accessed 2026-11-07.
  7. Ship a change. rat-stack. Code-ready, deployed, and behaviour-verified are separate claims. Accessed 2026-11-07.

Last changed 2026-11-07 in 40188fa. Source on GitHub. Change log.

Linked from

  1. A rat can be a name with a mailbox. Rat King's named mailboxes and leased readers give ShitRat a postal mythology with a clear line between the rules and the rats' stories.

    Go back to ShitRat, meet the bestiary, or learn the rituals.¶

  2. Agent guide. An Effect stack so pure (aspirational) Kit Langton will blush.
    Link context

    The rat has rituals for proving it happened — The gate, the snapshot dance, receipts before claims, and the deployment check give rat-stack’s folklore some repeatable steps.

  3. Change log. What changed in the files served here, newest first.

    The rat has rituals for proving it happened — new page: Initial commit from joelhooks/rat-stack template

  4. Full agent guide. An Effect stack so pure (aspirational) Kit Langton will blush.
  5. Rat Stack lore | rat-stack. Short, source-grounded notes on the ideas and decisions behind rat-stack.
    Link context

    The rat has rituals for proving it happened — The gate, the snapshot dance, receipts before claims, and the deployment check give rat-stack’s folklore some repeatable steps.

  6. ShitRat is Joel's familiar, with receipts. Meet ShitRat: Joel's terminal-dwelling familiar, its public house, its rules, its commits, and the incidents that became canon.

    The rituals: the gate, the snapshot dance, and a deployment checking its own doorbell.¶

  7. Source change history (log.md). The generated change log as Markdown.

    The rat has rituals for proving it happened — new page: Initial commit from joelhooks/rat-stack template

  8. The rat-stack bestiary eats excuses. A field guide to eight documented rat-stack creatures, with real habitats, enforceable behaviour, and strictly imaginary temperaments.

    The snapshot dance gives the repair sequence.¶