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

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 05:29:54 UTC · snapshot created 2026-10-03 05:30:57 UTC · last check 2026-10-03 07:15:14 UTC

A.19.SOURCE-SET-SPACE-SUBSTRATE:5.4 - Use-situation spread

Use the pattern this way across different working situations:

Working situationWhat to do with this patternWhat must stay explicitCommon miss avoided
Archive-side QD line where navigation and evaluation stay in one declared behavior spaceUse the shared-space profile. Fill the six core fields, then add descriptor/metric qualifier only if active.Archive as source set, both role-refs, sameDeclaredSpaceAs, and the active posture.Treating the archive or descriptor layer as if it were the space itself.
Derived tradition/front line that is judged against one different outcome spaceUse the cross-space profile and keep DerivedViewKind plus BasePaletteRef visible.The derived view stays derived, the base palette stays recoverable, and the cross-space relation stays explicit.Letting the visible front replace the base palette or hiding the bridge-loss posture.
Learned, adaptive, or uncertainty-bearing line where the space declaration is real but heavier qualification is still case-boundKeep the substrate core explicit and choose the honest posture token such as uncertainty-bearing, learned/adaptive, or unstable-under-refresh.The reader can see that the substrate is real without being promised fake geometric closure.Pretending every serious case is either fully transparent or fully described by one metric stack.
Shortlist or publication note that only says what set result or publication form is shown or shippedDo not use this pattern. Apply G.5 or G.10 directly.The note stays publication-facing instead of imitating substrate depth.Padding publication metadata with pseudo-substrate language.