type: rule
status: active
timestamp: 2026-06-29
tags: [agents-md, self-update, knowledge-discipline, hard-rule]

Rule additions land in 3 places: concept file + AGENTS.md table + count

Add rule: write to knowledge/rules/ + AGENTS.md entry + bump section count. All three same commit

Three-place update when a rule is added

When user says “add this rule” or a locked grill answer becomes a rule:

Place	Action
1. Concept file	Write `knowledge/rules/<area>/<kebab-name>.md` with OKF frontmatter and body
2. AGENTS.md table	Add a one-line entry under the relevant subsection (e.g. `### Agent behaviour (N) — knowledge/rules/agent/`)
3. Count header	Bump `### <Category> (N) — ...` count to `N+1` AND the top-of-file `## Rules (TOTAL) — non-negotiable` total

All three in the same commit. Conventional commit: docs(knowledge): add <slug> rule (3-place update).

Concept file alone = rule exists but isn’t discoverable from the AGENTS.md TL;DR table.
AGENTS.md alone = no enforceable file, no detail, no frontmatter for knowledge/index.md generation.
Skipping count bump = section headers drift; loses the at-a-glance “how many rules in this category” signal.

Explicit user instruction: “add a rule that …”
Locked grill answer that codifies a taste or behavior (per grill-to-knowledge)
An override-mined pattern (user picks 2nd choice repeatedly ? candidate rule)

Decision file (knowledge/decisions/…) — those don’t go in AGENTS.md’s rules table; they go in the decisions section
Runbook, service, glossary — same; their own sections
A rule modification (not addition) — just edit the concept file; count stays

? Writing the rule file but forgetting AGENTS.md entry ? discovery rot.
? Adding the AGENTS.md line but forgetting the count bump ? drift.
? Committing the rule file and the AGENTS.md update in separate commits ? git log can’t tell they’re one decision.
? Writing a long description in the AGENTS.md table line. One line, terse. Detail lives in the concept file.