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

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 11:52:20 UTC · snapshot created 2026-10-03 11:53:41 UTC · last check 2026-10-03 13:45:10 UTC

C.32.MLAO:9 - Consequences

Positive consequenceCost or trade-off
Residual-reducing architecture candidates are made explicit.The practitioner must name the affected levels or scopes, selected structures, residuals, preserved structure, lost structure, new burdens, and the pattern for the next question for any comparison or choice claim. Use C.30.STRAT or B.2.P first when level wording or whole-reidentification wording is not yet typed.
Optimization language is usable without carrying architecture adequacy.No scalar selector or architecture decision is available by wording alone.
Holonic breadth is preserved.Non-software cases must still recover their selected structures and patterns for the next questions.
Residual triage and candidate framing stay distinct.The team may need both C.30.ILC and C.32.MLAO.
Compressed representations can guide action.Source-return triggers must be visible.