A.2.3:3 - Forces · fpf.tools

Force	Tension
Consumer promise vs provider ability	Promise content states the consumer-side outcome; capability states what the provider System can do under declared conditions.
Specification vs execution	Promise content remains an episteme; exact delivery-work facts, affected entities, post-work states, and separately governed delivery or acceptance relations are evaluated against the promised predicates. The evaluation operation’s result binding and any verdict episteme remain distinct from those subject facts.
Universality vs domain richness	One kernel meaning must cover IT, utilities, healthcare, public services—without absorbing domain taxonomies.
Reviewable acceptance vs method autonomy	Consumers need named outcome predicates, characteristics, scales, target values, and acceptance criteria. Systems classified under provider system-role kinds and holding exact assignments retain freedom to select delivery methods through method-selection work; an individual deontic duty enters only through an independently obtaining `U.Commitment`.
Stability vs evolution	A changed promise creates a new promise-content episteme edition, while earlier work occurrences and evidence relations retain their own identities.