| Generic container recovery | A record, row, field, or slot-shaped placeholder is presented as the recovered ontology although the current object could be a direct relation, assertion episteme, declaration, participant designation, publication form, or representation. | Name the exact governed object and its defining or testing rule; add declaration, assertion, reference, publication, or representation apparatus only for a named receiving use. |
| Representation becomes obtaining | A graph edge, tuple component, diagram element, or table cell is treated as the world-side relation or its occurrence identity. | Keep the element under the exact C.29 or publication predicate, state the represented object and explicit correspondence, and test the direct relation predicate separately. |
| Method description becomes a project constellation | One U.MethodDescription is made to contain a method family, mechanism, plan, Work occurrence, transformation, result, architecture, and representation as if they were one object. | Let one U.MethodDescription describe one exact U.Method; state every other current object and direct relation separately under its defining or testing rule. |
| Authoring row becomes a practitioner form | Engineers are required to complete an applicability row before using a clear rule. | Keep the row inside E.10.ARCH authoring and publication architecture; give practitioners the shortest exact object-and-relation sentence and bypass restoration when the concrete predicate and its rule are clear. |
| Classification or type-correct-designation fallback without repair | The text names a restoration pattern, generic result label, MethodDescription field, planned use, compatible type, or designation but leaves no exact governed object, direct relation, claim-bearing episteme, defining or testing rule, truthful WMR result family, or blocker. | Apply the recovered defining or testing rule to one truthful result or fail closed; type correctness and designation do not establish actuality. |
| Trigger registry copying | E.19, C.30.P, C.16.P, C.16.Q, or a subject pattern copies the full E.10 trigger list. | Keep only the thin cues needed for independent unresolved questions and cite E.10 and E.10.ARCH through ordinary references or Relations. |
| DPF entry promoted to FPF vocabulary | A domain trigger or its local repair is copied into the shared applicability table merely because one DPF uses it. | Keep the entry beside the DPF claim whose wording it restores; propose an FPF amendment only when the same participants, relation, failure, move, and use remain meaningful across domains. |
| DPF wording profile by default | A DPF creates a trigger registry, profile, table, or package-wide no-profile result before recurring wording or a maintained multi-entry use has been shown. | Repair one case locally; create entries only for demonstrated recurrence, identify a separate profile only for a named maintained multi-entry use, and keep any table that publishes it as a publication form. |
| Wording repair settles domain doctrine | An author changes a domain claim while presenting the work as lexical repair. | Stop and reopen the DPF source, semantic-synthesis, or content decision; resume wording restoration only after the relied domain claim is current. |
| Umbrella-to-umbrella replacement | support becomes basis, display becomes view, reading becomes evaluation, or function becomes role without a recovered governed object and exact use. | Recover the governed object, any direct relation use, admissible use, and remaining reader use; otherwise demote or block. |
| Source-ontology smuggling | interface, schema, record, profile, path, or another familiar source-domain word is used because it sounds precise, but the recovered governed object or direct relation is different. | Recover the source ontology, governed object, exact direct relation, any declaration-local SlotSpec or assertion-side designation, and the rule that defines or tests the claim; keep the source word only when that rule makes the meaning current. |
| Over-annotated restoration | A clear subject sentence is expanded into type labels or source-ontology commentary even though no object, kind, relation, slot, admissible use, or subject pattern changes. | Keep the ordinary wording; annotate only the claim-governing term under repair and use F.19 if phrase apparatus remains. |
| Sterile precision | The wording is ontologically well-formed but no working reader can tell why the distinction matters or what reader use remains. | Apply F.19 to restore the didactic or recognition function in admissible ordinary wording. Use a non-use disposition only when it is the current grounded result; otherwise return an incomplete rewrite. |
| Shadow precision-restoration pattern | A subject pattern contains its own first-stage repair algorithm beside this distribution. | Extract repair-only material to the applicable realization pattern and leave a first-use cue. |
| Reference boilerplate in subject pattern | A subject pattern explains where the repair belongs, why the package was split, or what this text does not contain instead of stating the subject pattern’s own repaired wording or first move. | Move architecture-placement rationale to DRR or architecture notes; replace routing prose with a normal pattern id, citation, or Relations row. |
| Apparatus-preserving paraphrase | A repair changes wording but keeps phrase-level apparatus around a recoverable kind. | Apply F.19 first; use E.10.ARCH only for remaining word, head, or use precision. |
| History placement as pattern prose | Past placement or old naming text explains history instead of current use. | Keep only current entry or repair rows where needed; write current pattern prose in the selected placement. |