C.2.P:9 - Consequences
| Benefit | Trade-off and mitigation |
|---|---|
| Prevents parallel episteme and publication ontology from entering FPF-governed wording. | Adds a small recovery step before apparently simple rewrites; mitigate by using the smallest sufficient mode. |
| Preserves accepted glossary and rules without turning source-related statements into accidental pattern authority. | Requires a clear separation between pattern guidance and source-related statements. |
| Makes unclear meaning fail closed. | Some attractive phrases will not be accepted until their kind or relation is actually recovered. |
| Improves DRR and pattern drafting discipline. | Authors must resist convenient lists and umbrellas when one kind named by value or relation is needed. |
C.2.P:9.1 - Operating consequence
For each repair:
- start from the sentence’s function and practical consequence, not from a word list;
- preserve any E.10 cue or routing result and recover only the one still-hidden episteme, publication, carrier, source-to-use, or use-disposition distinction;
- use the direct pattern as soon as it is known;
- choose direct repair before a compact row, and a compact row before a full check;
- keep the final sentence readable to a cold practitioner and state what action or non-use remains;
- reopen only when a material field or use changes.
Do not perform global lexical replacement. Do not treat every FPF pattern edit as a full epistemic-restoration case. Do not retain a compatibility field whose only function is to remember a previous internal schema.