E.18:4 - Forces · fpf.tools

Force	Tension
Universality vs specialization	One architecture covers supply chains, water networks, ML functionals, general P2W problem-to-work carry-through, and a first-principles P2W specialization, without baking in any one morphism set.
Publication neutrality vs auditability	Keep faces notation-neutral and non-mechanistic while requiring the exact `CrossingRef`, per-binding accounts, gate-decision refs, and publication pins used by the named downstream reliance.
Set-return discipline vs business pressure for totals	Preserve return sets and declared partial orders ↔ stakeholders demand single numbers.
Cross-locus, plane, edition, or selected-structure reuse vs safety	Enable bounded reuse while naming the changed `U.ContextSlice`, plane, edition, design/run tag, or retargeted subject and separating its from/to values, establishing basis, any applicable declaration or rule, and any current rule application; invoke F.9 only for a separately established cross-semantic Bridge and bounded-use claim.
Agility vs reproducibility	Permit evolving CG‑Spec, UNM, and Comparator editions ↔ require edition pins and re‑emission on change.
Cycles vs convergence	Allow Selection↔Planning iteration ↔ impose budget and slice‑scoped refresh to prevent thrash.