| Representation usefulness and action overread | Graphs, queries, predicates, and dashboards are useful precisely because they expose structure; their shape does not supply hidden work, permission, or release. |
| Legitimate path words and metaphor repair | A.10 evidence path, E.18 graph path, and carrier file paths may be legitimate; path becomes a defect only when it carries a stronger action or authority claim by metaphor. |
| Method generality and subject discipline | Algorithms, programs, solver models, proofs, SOPs, and process models can all be useful, but first identify the direct object or relation, the current claim, and any exact representation use. Select U.MethodDescription only after the claim-bearing episteme passes the A.3.2 membership test; representation form alone selects nothing. |
| Declarative and imperative labels are too crude | Current programming and process practice includes effects, handlers, constraint models, object-centric events, e-graphs, and process theories; the repair names the direct object or relation, current claim, any representation use, and subject pattern rather than choosing one programming-paradigm slogan. |
| Subject pattern and local repair | When E.18, A.10, A.3.1, A.3.2, A.6.1, A.15.2, A.15.1, E.17, or another pattern already governs the current claim, this pattern names only the overread and leaves the next claim to that pattern rather than duplicating it. |