v0.1.0 — the governance skeleton (2 July 2026)

Make Claude Code behave consistently across repos, sessions and humans. Rules-as-files governance, extracted from a live production system.

Backfilled release note. The v0.1.0 tag has pointed at this commit since 2 July 2026; what was missing was the changelog, not the code.

What is in it

The governance skeleton:

• docs/SPEC.md — rule anatomy (trigger + essence + pointer), the frontmatter schema (origin, date_established, status, supersedes, audience), precedence (newer beats older; a rule whose origin is the owner can only be overridden by the owner), the routing tree that decides whether a thing belongs in the codex, the agent config, memory or a hook, the declined-decisions journal, objection sparring, and the intake ritual.
• templates/ — rule, decision memo, declined-decisions journal.
• examples/rule-objection-sparring.md — a real rule, born the same day from a real overturned verdict.
• FOR-ROBOTS.md — the entry point for an AI agent mining this repo.
• devlog/2026-07-02.md — how this release happened: the decision chain and the research inputs.
• docs/the-day-my-ai-said-no.md — the launch story.
• ROADMAP.md — the pain-driven plan of what gets opened next.

The problem it solves

One behavioural codex that humans and agents follow, where a rule has a defined home, a defined precedence, and a defined way to be argued out of existence. Without that, "the rules" live in six files, three chat histories and one person's head, and every session re-litigates them.

Full Changelog: https://github.com/Palo-Alto-AI-Research-Lab/claude-bible/commits/v0.1.0