A.15.9:3 - Forces · fpf.tools

Force	Tension
Reuse versus fresh Work	A current qualified result can be cheaper and safer than a new request; a narrower answer can remain useful when a stronger one is unsupported. Acquisition must earn its cost without treating a stale or wrong-configuration answer as adequate.
Small request versus useful boundary	The receiver needs a short request without omitting the subject, situation, use, and stop that make the answer meaningful.
Supplier judgement versus receiver authority	The supplier governs its Method and professional conclusion; the receiver still owns the decision that consumes it unless a separate authority relation says otherwise.
Informal exchange versus recoverability	Two sentences may be enough for a reversible choice; consequential reliance may require exact sources, Work, evidence, authority, dissent, and currentness.
Named specialist versus supported performer	A title, department, credential, provider label, or tool name can help find a candidate but does not establish capability, assignment, authority, or performed Work.
Recognition versus assurance	A vague outside-practice dependency is enough to open the pattern; high-consequence use requires stronger direct evidence, assurance, and stop rules.
Shared move versus domain ownership	The inspect-reuse-or-request boundary transfers across practices, while every domain keeps its own questions, Methods, evidence standards, acceptance, and consequences.