F.19:4.2 - Pattern-prose specialization

When the repaired prose is an FPF pattern, apply the same method with one purpose test:

Does this sentence help the pattern’s intended user recognize and perform the pattern, or does it record development, review, projection, landing, quality, or source-management evidence about this version?

If it records evidence about the pattern version, keep that evidence outside the pattern unless the pattern’s own primary EntityOfConcern is that evaluation or projection object. The evidence can cause edits to the pattern; it is not automatically pattern content.

Pattern prose keeps:

• the pattern’s own primary EntityOfConcern;
• the first useful move;
• the practical delta and cost of missing it;
• a local boundary that passes F.19:4’s full independent-ground, plausible-reader, contribution, and smallest-clear-correction test; and
• short references to related patterns after the pattern’s own content is visible.

Public architectural reasons stay with the explanation when they help the intended user understand, select, combine, or adapt the Methods and profiles. Apply E.8:4.2.3 to distinguish those reasons from the current version’s development history.

Pattern prose moves out:

• rationale for the current draft’s placement or promotion as a development decision;
• correspondence about producing or reviewing the draft rather than using the pattern;
• quality, projection, monolith-parity, landing, and source-management evidence; and
• repeated boundary doctrine already carried by another pattern.