E.4.DPF:3 - Forces · fpf.tools

Force	Tension
Domain urgency	The local team needs usable guidance soon, but premature durable names and pattern heads freeze poor ontology.
Source richness	Domain traditions provide valuable methods and examples, but source summaries can hide rival traditions and lost evidence.
Problem-solving primacy	A DPF may need terms and ontology, but those are supports for recognizing recurring domain problems and choosing SoTA solution moves, not the framework’s payoff by themselves.
FPF reuse	FPF Core gives strong authoring, relation, and quality patterns, but direct copying can mask domain-specific concerns.
Publication need	A framework publication carrier helps readers, but it can hide relation, dependency, and currentness records.
Evolution	Domain and local frameworks change and improve as sources, uses, relied-on framework editions, and the required Core claims change.