E.4.FPF:2 - Problem
DPF and local-framework packages can have detailed rules for publication units, forms, carriers, relations, naming, quality, and refresh while authors leave FPF’s form unstated because they consider it “the main spec”.
That creates several failures:
- an all-in-one file or site, one of its Readme, Architectural Reference, ToC, pattern-body, card, or first-entry units, a skill-pack bundle, or an MCP route is mistaken for the FPF edition itself;
- FPF is described as one more DPF, losing the first-principles and transdisciplinary burden that makes DPFs possible;
- whole-FPF quality is checked by local pattern scores, landing status, or DPF package scales instead of
E.2.DA; - adoption units, forms, or access surfaces grow user-facing explanations that quietly become shadow authority beside subject patterns;
- skill or MCP access makes FPF look like a callable service, tool permission layer, or runtime dependency rather than a framework edition reached through an access route or borne by an exact access-facing presentation carrier.
Use an FPF-specific form rule. FPF must keep first-principles distinctions usable across domains while allowing domain and local frameworks to grow from it; E.4.DPF governs those dependent frameworks.