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 02:22:15 UTC · snapshot created 2026-10-03 03:38:22 UTC · last check 2026-10-03 03:45:20 UTC

C.30.STRAT:4.2 - Recovered meanings and patterns to use

Recovered meaningCommon source labelsWhat must become clearPattern to use
Control structurelayer, level, tier, sometimes gateThe obtaining control relation, what its participants do, any rate band or locality boundary, and a B.2.5 supervisor-subholon relation only when it obtains.C.30.LCA; use B.2.5, dynamics, temporal, evidence, assurance, or gate patterns only for their separate claims.
Selected structure or structural viewlayer, level, stack, block, viewThe selected, hidden, lost, or preserved structure; view selection; correspondence; source return; an ArchitectureClaim when claim content is needed; and a separate ArchitectureRelation only when that direct relation obtains.A.22, C.30, C.30.ASV, or the applicable C.30 subpattern.
Module, interface, or substitutionblock, cache, router, expert, sometimes layer or stackModule boundary, interface specification, substitutability relation, variation point, conformance relation, or reliance boundary.A.6.M; stop using C.30.STRAT once that relation is clear.
Function or transformation flowblock, expert, cache, router, gate, sometimes layerTransformation or effect, path selection, graph node, path or crossing, architecture-to-flow relation, or E.18 flow valuation.A.6.F, E.18, or C.30.TFS-REL.
Characteristic, scale, or mathematical lenslevel, tier, ladder, rung, layer, stack, blockCharacteristic and bearer, coordinate or value, scoring method, comparison criterion, scale window, resolution, coarse-graining, preserved or lost structure, lens-use result, and stop condition only where the claim needs them. State separately how the subject is mapped to a scale value; a scale or band does not by itself establish levels in the subject.C.16.P, the applicable characterization pattern, or C.29.
Episteme, publication, view, or source usestack, layer, section, view, cache, gateDescription episteme, publication unit, face, form, carrier, source-currentness or source-use relation, source-return condition, or ordinary publication label.C.2.P for a remaining epistemic distinction; otherwise the direct pattern: C.2.1 for episteme content, E.17.0 for U.View membership, E.17 for reader-facing publication of an accepted account, E.24.PUB for publication availability, or the pattern defining the source-use claim.
State, currentness, time, or dynamicscache, stable, level, readiness, sometimes gateBearer, state frame and values, validity window, currentness relation, dynamics, temporal aspect or rate band, authored temporal-claim adequacy, and reopen condition.A.19.SPR only while the state-family meaning is unresolved; otherwise A.3.3, C.27.TA, C.27, or the applicable state or temporal pattern.
Evidence, assurance, gate, work, decision, or causal usegate, proof, safety, decision, work, effect, or any label used as authorityEvidence path, assurance argument, constraint-validity record, gate decision, Work occurrence, decision record, causal-use record, and any limits imposed by the applicable pattern on that claim.A.10, G.6, B.3, A.20, A.21, A.15.1, C.11, C.28, or the applicable neighboring pattern.
Ordinary source-label non-useany source labelNo FPF claim remains after the sentence is read in context.No precision-restoration pattern; keep ordinary wording, quote it, reduce its use, or block reliance.

When a level claim matters. When a later decision or design relies on a sentence such as “X is at level L” or “A is above B,” name the subject at stake (the EntityOfConcern), what is being ordered, compared, grouped, or mapped, the relation or scale mapping that gives the claim its meaning, when it applies, and whether the sentence asserts, proposes, assumes, or merely illustrates the claim. Apply the same test when layer, tier, band, scale, or stage carries the stronger claim. A named model or standard may provide this mapping within its declared use; its status does not extend the claim beyond that use. The source word may remain, but these facts—not the label—carry the claim. A list, diagram row, first-then order, carrier section, curriculum, scale label, stage sequence, or coarse-grained description does not establish a subject level by form. If the facts are missing, keep the wording local or illustrative and block reliance on the stronger level claim.

When orientation carries the claim. Recover the structure’s subject, the represented relation and the convention that gives vertical or horizontal its meaning through A.22:4.3a. Keep literal spatial directions under their actual reference frame. For a Method-architecture question, C.30.ASV:4.5a helps choose the structure; the axis does not choose it.