| Every edit becomes a programme | A typo triggers candidates, scoring, evidence packaging, and refresh work. | Use the direct bounded repair and stop after its focused check. |
| Delta by label | “Lexical” or “minor” hides an action-changing edit. | Describe the actual reader and consumer effect first. |
| The author’s map proves preservation | A rewrite is checked only against what its author remembers preserving. | Derive predecessor-use probes independently and inspect every material function. |
| Search output equals impact | Every textual mention is edited, while an undeclared real consumer is missed. | Test whether each candidate locus actually depends on the changed premise. |
| One score chooses the winner | Readability, breadth, formal checks, and assurance are added without lawful scales or protected trade-offs. | Keep constraints separate and choose among non-dominated candidates for the intended use. |
| Version number supplies semantics | major, minor, or patch is treated as proof of compatibility. | Decide continuity first; use a version label only to communicate that decision. |
| A new trace for every change | DRR, review, source, check, and landing facts are copied into another authoring-trace record. | Keep the minimum change account in the receiving workflow and cite existing results. |
| Precise fragment, unreadable pattern | A formal repair passes a token check while the whole pattern loses recognition and practical entry. | Read the whole changed pattern as a cold practitioner and simplify non-load-bearing formal language. |
| Self-log as practitioner guidance | The pattern publishes its own authoring history and calls it Work or quality evidence. | Keep one worked practitioner case in the pattern; keep actual work and evaluation evidence in their direct records. |