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

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 08:25:59 UTC · snapshot created 2026-10-03 10:17:34 UTC · last check 2026-10-03 10:30:16 UTC

C.30.P:5 - Subject pattern assignments

Recovered use, claim kind, or admissible-use boundarySubject pattern
selected structure, structural description, structure source-returnA.22
ArchitectureOf@Context, selected architecture-relevant structure, thin conditional ArchitectureDescription@Context bridge use, architecture question cardC.30
full ArchitectureDescription@Context mechanism, architecture-description multi-view set, architecture-description specification-use boundaryC.30.AD
architecture structural view, structure-kind view, hidden or lost structureC.30.ASV
transformation-flow graph expression, flow relation, architecture-to-transformation-flow relationE.18.2 for a mathematical flow-graph expression; E.18 for selected transformation-flow structure; C.30.TFS-REL for its bounded architecture-use record; otherwise the subject pattern for the claim being made
architecture-synthesis wordingRecover the concrete claim kind, then use the architecture-synthesis routing note below.
control structure view, LCA sketch or control sketchC.30.LCA when an architecture control-structure view claim is being made
cross-scope conflict or frustration triageC.30.ILC when that question is being asked
source, publication, carrier, view, face, PublicationUnit, dashboard, ADR, documentation, source-returnC.2.P while the relevant distinction remains hidden; otherwise E.17, E.17.0, or the publication or source-use pattern governing the claim
relation construction, basedness, source, base-dependence, evidence and relation-claim discrimination, endpoint compression, comparisonA.6.P or the A.6 specialization selected by the recovered claim
function, functional, functionality, effect, module, interface, or signature claimA.6.F, A.6.M, A.6 signature and slot pattern, or the retained module, interface, or signature specialization selected by the claim
stratification or source labels such as layer, level, tier, stack, ladder, rung, block, expert, cache, router, or gateC.30.STRAT while the label’s technical meaning remains unclear; after recovery, use A.22, C.30, C.30.ASV, C.30.LCA, C.30.TFS-REL, A.6.M, A.6.F, E.18, C.16.P, C.29, or the pattern governing the recovered claim
mathematical lens, mapping, model, similarity, preserved-structure and lost-structure as mathematical-lens useC.29
characteristic, scale, metric, score, indicator, threshold, architecture score, quality coordinateC.16.P, then C.16, A.19, C.25, E.21, or the pattern governing the claim
quality-term or evaluative characterizationC.16.Q, C.25, E.21, or the characterization pattern governing the claim
evidence, proof, validation, witnessA.10 for source recovery and bounded reliance; the defining or testing pattern for the evidence, proof, validation, or witness claim itself
assurance, engineering justification, safety caseB.3 or the applicable assurance pattern for a named assurance claim; the defining domain pattern for a separate safety claim
internal constraint, gate, admissibility, release, approvalA.20 for an internal-constraint result; A.21 for a named gate decision; the direct domain pattern for the particular admissibility, release, or approval claim
work, method, implementation, operation, change executionA.15 for the Work family; A.15.4 while appearance hides a work-reliance prerequisite; A.3.1 for U.Method; A.3.2 for U.MethodDescription; or the work or method pattern governing the claim
decision, choice, trade-off resultC.11 or the decision pattern governing the claim
causal-use or intervention claimC.28

Architecture-synthesis routing note:

  • Use C.32, C.32.MLAO, C.32.CONWAY, or C.32.FAIL when the recovered claim is a candidate palette, residual-reducing multilevel frame, transformer and transformed correspondence frame, or architecture-synthesis repair cue.
  • Use A.19.CPM, A.19.SelectorMechanism, C.11, or G.5 when the recovered claim is comparison-policy use, selector-policy use, local choice, or selected-set result declaration. When publication is current, use E.17 for a source-backed face and source return and E.24.PUB for the publication occurrence and audience availability.
  • Use C.18 or C.19 when the recovered claim is archive, front, or pool policy.
  • For transformation-flow, function, module, transformer, mathematical-lens, relation-signature, affordance, architecture-use, or move-like wording, recover that claim kind first and use its subject pattern by value.