E.9:4.1a - Process-source method admission into FPF

When an author considers a stable method described in a process source, the author decides the FPF-admission disposition by value. The DRR records that decision and any source-use relation that matters; neither the source passage nor the record becomes a second canon.

The DRR names:

• the process-source passage or accepted process-source decision-ground item being considered, named by value;
• the reusable FPF method recovered from that passage;
• the current FPF pattern, section, or accepted DRR that already carries the method, if any;
• the remaining delta that current FPF does not yet carry;
• the selected FPF pattern chosen to carry that delta;
• process-control material excluded from FPF pattern prose, such as task dispatch, seam state, helper behavior, Git recovery, packet transport, review transport, chat cadence, and mutable release state;
• the source-use result for that passage or decision-ground item: quote named by value, narrowed scope, instantiated case, decision-bearing use, draft-guidance source, example-only use, or retired source use;
• any meaning loss or addition created by that source-use result: changed scope, relation, evidence path, admissible use, non-admissible use, reader use, or recoverability condition;
• the first improved FPF use that the admitted method gives to an author, reviewer, or downstream FPF user;
• the current disposition: selected now, inherited sufficient, rejected now, or outside the current decision with the named evaluation pattern, accepted DRR, or accepted decision-ground item named by value.

Reusable process-source method is not limited to semio wording or pattern-authoring language. It may enter FPF only when it is separable from local process mechanics, improves FPF use, and has one exact evaluation pattern. After the method lands in FPF, process documents should cite the selected FPF pattern instead of keeping a parallel long-form rule.