Jump to text
On this page
Copy and source
Published source confirmed at last check

Source changed 2026-11-21 18:11:08 UTC · snapshot created 2026-11-21 18:12:06 UTC · last check 2026-11-21 21:20:10 UTC

E.4.FPF:3 - Forces

ForceTension
First principles vs domain knowledgeFPF must carry transdisciplinary ontology, epistemology, evidence, architecture, decision, work, publication, and improvement distinctions without becoming a doctrine of one domain.
Public adoption vs subject-pattern authorityReadme, Architectural Reference, examples, cards, skills, and MCP access must help new users without becoming a second spec.
Core stability vs evolutionDownstream DPFs need a stable basis in FPF, while FPF remains open to new patterns, better terminology, and source-front movement.
Pattern-set quality vs whole-framework qualityIndividual E.21 results matter, but they do not establish whether the whole FPF meets the Pillars.
Carrier plurality vs identityThe same FPF edition can use several publication units and forms, several exact presentation carriers, and several access routes; those different objects must not create competing FPFs or collapse into one another.
Access convenience vs architecture clarityA callable access route can make FPF easier to use while hiding edition, currentness, source, and authority boundaries.