E.11.PFP:3 - Forces · fpf.tools

Force	Tension
Cold-reader entry	Stable labels and order reduce search cost, but edition administration must not displace practical entry or the pattern bodies.
Exact edition return	Readers need a stable public designation and locator, while dates, filenames, statuses, and build digests must not become edition identity.
One logical index	FPF-family editions need one authoritative pattern index, while visible Part or placement groups remain useful.
Product variation	FPF, DPF, and LPF editions share a front form, but their body, reference tail, and choice-relevant public cues differ.
Whole and direct use	Readers need the language’s shared problem, organization, reasons, and limits, while a direct question may be answered by one pattern.
Product boundary	Support units may belong to one framework product; independently useful adjacent products need a truthful boundary and public return.
Deterministic checking	Syntax checks should be reproducible, but they must not infer table purpose, product truth, or reader value from prose.
Form and carrier separation	One form may be borne by several carriers, and one outer carrier may expose several products, without merging their identities.
Accessibility and translation	Predictable headings and navigation aid many readers and tools, while one English label set cannot silently stand in for every language or access need.