E.9:0.2 - What this buys

• one external decision record that states the bounded FPF change by value before Core text is rewritten
• one minimum kernel that keeps Problem frame, Decision, Rationale, and Consequences recoverable for later review and replay
• one temporary convergence record that fixes the selected answer before later drafting fans out, while keeping enduring Core text in the selected patterns and selected non-pattern FPF kind-reference pairs rather than in the DRR

First useful move. State the working FPF problem, selected answer, practical change, selected loci, first substantive drafting action, and nearest boundary in ordinary precise language before drafting or landing Core text.

Cheap stop. If the change is ordinary local wording repair, application of an already accepted pattern, or editorial cleanup that does not change FPF semantics, obligations, boundaries, names, admissible uses, or normative force, do not open a full DRR. Use the lighter governing pattern for the local repair: F.19 for kind-preserving plain rewriting, E.10 for an unresolved FPF wording-use question, E.17.AUD.LHR for one overloaded local lexical head inside one publication unit, C.2.P for an episteme, publication, or source-use distinction left unresolved after the E.10 check, F.18 only when a durable reusable name is being minted, and E.8 for authoring-form correction. Leave E.9 for bounded content decisions that need rationale by value.

Kind-or-boilerplate diagnostic. When a DRR proposes wording for selected patterns, apply F.19 to separate boilerplate from remaining content before any wording is treated as pasteable pattern prose. If the remaining content still hides wording-use, naming, relation, claim, admissible-use, selected-locus, user-action, or flow-position precision, the DRR names the applied E.10, E.10.ARCH, F.18, or the pattern that defines the affected object or relation. Process, architecture, review, or reference boilerplate belongs in its own carrier, not in pasteable pattern prose.

Wording proposed in a DRR is not pasteable pattern prose until the selected-answer basis shows what object, relation, claim, slot, use, admissibility, or scope would change—or explicitly says that no such semantic change occurs. Apply F.19 and the concrete pattern that defines or constrains the live distinction. Do not expand ordinary wording into method, work, application, or ClaimGraph apparatus unless that exact distinction changes the decision or later reliance.

Primary EntityOfConcern in plain terms. One external decision-rationale account for one bounded FPF content decision or coordinated change set. It keeps the problem, selected answer, rationale, consequences, practical change, selected loci, and boundary recoverable enough for authoring without invention. Exact C.2.1 identity is added only when the decision or a named later reliance needs it.

Primary working reader. The first working reader is an FPF author, reviewer, or steward who must evaluate, challenge, or land one bounded content decision. Downstream pattern readers benefit from the landed Core text; they are not the primary reader of the DRR itself.