Developer argues coding rules must be machine-enforceable, not just documented prose

A software developer has shared a workflow shift in which repository coding rules are only considered valid if they can be automatically enforced by CI pipelines, not merely written in documentation like AGENTS.md. The approach stems from repeated pull request violations where well-written rules were ignored, not always by agents acting in bad faith, but because prose-only rules lack mechanical accountability. The developer published a tool called Agents Playbook, which lets teams run specific executable gates — such as a no-any TypeScript check — both locally and in CI with consistent results. The system also supports inline exceptions with documented justifications, distinguishing legitimate edge cases from silent bypasses. The core argument is that deterministic, syntax-level rules belong in automated gates, while contextual design decisions should remain in review checklists.