---
name: rule-failed-its-author-needs-a-mechanism
description: "BINDING — where a rule has failed its own author, replace it with a mechanism that requires no attention; the judgement call IS the failure mode."
metadata: 
  node_type: memory
  type: feedback
  originSessionId: 2d90d3c2-afb7-4393-a999-3180b6f16985
  modified: 2026-07-19T18:06:43.030Z
---

**Where a rule has failed its own author, do not resolve to attend harder — replace it with a mechanism that does not require attention.**

**Why:** 2026-07-19 (spt-core, todlando + doyle). Four rules failed their own authors in one day, every time on a competent person concentrating hard on content while the rule sat one layer out from what they were attending to:
1. todlando's own classify-at-birth rule, broken in the very commit that created the test it governed.
2. doyle's W2 dispatch, which as written would have destroyed the experiment it was meant to authorise (applying the fix before the measurement).
3. todlando's binding "long bodies ride a FILE" — broken in a message *about* discipline.
4. doyle broke the same inline-backtick rule two messages after commenting on todlando's breach.

The diagnosis that makes it actionable: **the judgement call is the failure mode.** "Does this body contain a metacharacter?" is a check that runs exactly when attention is elsewhere — which is the situation the rule exists for. A rule requiring you to notice you are in danger does not work.

**How to apply:** when a rule is broken by the person who owns it, that is evidence about the RULE, not about the person. Convert it to something unconditional:
- Every long message body rides a file — no judgement about whether *this* one has backticks ([[send-body-from-file-not-inline]]).
- A fixture **currency** assert in the rig, not a note in someone's gate log ([[teardown-authority-progress]] W1).
- A named sibling probe (`process_exists`) whose name IS the question, not a doc caveat on the wrong function.
- A test valve that manufactures a state, not a loop racing correct behavior for it.
- Each gate leg its own command with its own captured exit code, not a combined one-liner ([[ci-clippy-preflight-workspace]]).

Related: [[measure-the-box-before-the-instrument]] (the environment version of the same blind spot).