Skip to content

[Docs] full rule-audit table at docs/rule-audit.md #19

@atlas-apex

Description

@atlas-apex

Context

AgDR-0001 captured the design decisions for the 4 rule-mechanization hooks shipped in #13, but the full audit table — every MUST across all rule files with its mechanization status (mechanized / advisory / deferred) — was explicitly deferred.

This ticket produces that table as a standalone artifact at `docs/rule-audit.md`. Pure documentation, no hook work.

Acceptance Criteria

  • `docs/rule-audit.md` lists every MUST / NEVER / HARD-STOP rule from:
    • `CLAUDE.md`
    • `.claude/rules/*.md` (all 8 rule files — agdr-decisions, code-standards, git-conventions, pr-quality, pr-workflow, role-triggers, ticket-vocabulary, workflow-gates)
    • `workflows/*.md` (sdlc, code-review, deployment)
  • Each row has columns: rule (short name), source file + section, currently-enforced-by (hook filename / "prose"), mechanizable? (yes / no / deferred), proposed hook (for mechanizable-but-not-yet) OR reason advisory (for "no").
  • Rules that are advisory by design (e.g. "testing pyramid 70/20/10", "not Friday afternoon") are explicitly marked "advisory — not mechanizable in a shell harness" or similar.
  • Rules that are deferred to future tickets link to those tickets.
  • CLAUDE.md "Quick Reference" table adds a link to the audit.
  • Table entries are short (one-liner each), reasoning goes in footnotes or linked AgDRs.

Non-goals

  • Does NOT add new hooks. This is pure documentation.
  • Does NOT change any existing rule files.
  • Does NOT fold into AgDR-0001 — that AgDR is historical and should not be rewritten.

Links

Metadata

Metadata

Assignees

Labels

P2Medium — plan-worthy, not urgent

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions