E.4:3 - Forces · fpf.tools

Force	Tension
Core stability	The FPF Core must stay stable enough to supply dependable constraints to downstream frameworks, while domain and local frameworks need faster evolution.
Reuse and source-local meaning	Domain and local frameworks should reuse FPF Core distinctions, but they must not silently redefine Core meaning or treat a local label as a universal premise.
Publication pressure	Readers need all-in-one carriers, tables of contents, cards, examples, and first-entry material, but those carriers do not by themselves settle architecture.
Relation richness	Pattern ecosystems need recommendation, specialization, dependency, publication, preservation, evaluation, and source-use relations, but a single “related patterns” list hides the relation function.
Source and generation pressure	Source summaries, relation graphs, and generated candidate sets speed work, but their losses and admissible use must be declared before architecture work relies on them.
Problem-solving primacy	Frameworks need vocabulary and ontology, but a DPF is valuable only when those distinctions help a practitioner recognize typical problem situations and choose stronger solution moves.
Evolution pressure	Framework editions, dependencies, and names change over time, so compatibility, deprecation, supersession, and refresh conditions must be explicit.