fpf.tools
Library / First Principles Framework (FPF) - Core Conceptual Specification
Jump to passage
In this reading
Source · lines 74810–74820

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 02:22:15 UTC · snapshot created 2026-10-03 03:38:22 UTC · last check 2026-10-03 05:05:10 UTC

C.32.PAD:3 - Forces

ForceTension
Candidate pluralitySeveral candidate configurations can be valid under different trade-offs, while project work needs one current direction or a bounded exception.
Trade-off visibilityArchitecture characteristics compete; a decision that hides accepted losses cannot be responsibly executed or reopened.
Structure and method couplingThe decision must govern actual or modal structure content for the described or transformed-side holon and may also prescribe developer methods intended to produce or preserve those structures.
Work splitStructures fixed by the decision and refinement left open must be separated without severing source return.
EvolutionA decision must close enough work for now while staying reopenable when context, eval readings, or candidates change.
Publication pressureTeams often want an ADR file before the decision relation is recoverable.