Library / First Principles Framework (FPF) - Core Conceptual Specification
Jump to passage
In this reading

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 07:42:37 UTC · snapshot created 2026-10-03 07:43:27 UTC · last check 2026-10-03 07:55:10 UTC

C.32.MWA:3 - Forces

ForceTension to hold
One answer vs several structuresThe decision needs a coherent account, while the useful structures may remain non-isomorphic.
Actual use vs prospective designObtaining Work offers dated evidence; proposed Method use needs a truthful realization and later-test account instead.
Precision vs readable entryExact kinds and relations prevent false claims; notation-first prose can make the Method unusable to the practitioner who needs it.
Candidate breadth vs proportional effortThe first source layout is rarely enough; an unlimited candidate search can delay the decision without changing it.
Local gain vs moved burdenOne structure can improve while another inherits cost, delay, evidence burden, loss of control, or unresolved residual.
Project choice vs cultural changeA project can deliberately choose or change an arrangement; distributed generation, transmission, selection, retention, and loss are different claims.
Reusable Method vs domain fillingThe action sequence transfers across domains; actual domain Methods, institutions, evidence, constraints, and cases remain with the receiving domain.