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

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:0 - Use this when

Use this pattern when architecture or structure wording hides which use is being made.

Typical triggers:

  • architecture, architecture description, architecture model, architecture diagram, architecture map, architecture dashboard, architecture score;
  • structure, structural view, structural model, module layout, component structure, interface structure, or stratification wording or source-label wording such as layer, level, tier, stack, ladder, rung, block, expert, cache, router, or gate whose technical meaning must be recovered through C.30.STRAT before local architecture or structure assignment;
  • graph, flow, transformation-flow graph expression, control sketch, LCA diagram, ADR, dashboard, benchmark, source, or view being treated as architecture or structure by wording alone;
  • a function, module, interface, signature, flow, control, quality, score, evidence, assurance, gate, work, decision, causal-use, or release claim being smuggled under architecture or structure wording.

What goes wrong if missed. A diagram becomes the architecture, a graph becomes proof, a view becomes the selected structure, a source document becomes an architecture decision, a score becomes architecture adequacy, or a function, module, or interface claim becomes architecture by default.

What this buys. The reader can recover the architecture or structure use under repair, block the overread, and move to the subject pattern: selected structure under A.22, grounded architecture claim or conditional architecture description under C.30, architecture structural view under C.30.ASV, stratification-wording repair and source-label repair under C.30.STRAT, architecture transformation-flow relation under C.30.TFS-REL, control-structure view under C.30.LCA, mathematical lens under C.29, characteristic and scale repair under C.16.P, or a project-side evidence, assurance, gate, work, decision, causal-use, release, or publication pattern.

First useful move. Ask which selected structure, architecture relation, architecture-description use, structural-view use, source-return relation, or neighboring claim the architecture or structure wording is actually naming, then either apply the architecture or structure pattern named by value directly or use one architecture-structure repair note to assign the claim elsewhere.

Not this pattern when.

  • If the use under repair is already a selected structure, use A.22 directly.
  • If the use under repair is already ArchitectureOf@Context, use C.30 directly. If the use under repair is the full ArchitectureDescription@Context mechanism, use C.30.AD; use C.30 only for the thin architecture-description bridge tied to one architecture move.
  • If the use under repair is already an architecture structural view, use C.30.ASV or a named C.30.* view pattern directly.
  • If the claim being made is evidence, assurance, gate, work, decision, causal-use, release, mathematical-lens use, characteristic and scale construction, quality characterization, source-use, or relation construction, use the subject pattern for that claim after any architecture or structure wording is demoted or assigned.