Rulebook

Every team has rules its agents keep breaking: never force-push, always run the migration check, leave the generated client alone. Rulebook is where those live. A rule is written once, filed in a rulebook, and reaches every agent session through the coding-agent hooks — so the convention shows up in the work rather than in a document nobody opens.

A rulebook is the unit of policy, and its membership is its scope. That separates who is bound by a rule from who can read a brain, so an org-wide standard and one team's local convention are the same kind of object with different audiences. Anyone added to one is told, and given a way out.

Rules have a life. They are proposed, activated, paused, dismissed, retired, or superseded by a newer rule that names exactly which one it replaces — so the list stays the rules you actually follow, not an archive of everything anyone ever suggested.

Fire history is the half that makes it honest. Every fire links back to the session and the message where it happened, so you can see which rules earn their place and which are just noise. Filter to Applies to me and you get the answer an engineer actually wants: what is enforced on me, and what has it done.