#Architecture and Structure Precision Restoration

C.30.P · Cluster C.IV - Composite & Macro-Scale · Stable · Architectural pattern · Normative unless explicitly marked informative · Part C - Kernel Extension Specifications

#About this pattern

This is a generated FPF pattern page projected from the published FPF source. It is canonical FPF content for this ID; it is not a FPF Reference product feature page.

#How to use this pattern

Read the ID, status, type, and normativity first. Use the content for exact wording, the relations for adjacent concepts, and citations to keep active work grounded without pasting the whole specification.

Type: Architectural pattern Status: Stable Normativity: Normative unless explicitly marked informative

Plain-name. Architecture-structure wording repair.

Intent. Recover architecture or structure wording whose live object is hidden before a reader applies A.22, C.30, C.30.ASV, or an exact C.30.* pattern.

This pattern does not mint U.Architecture, does not fuse architecture and structure into one kind, and does not replace architecture-description adequacy or structural-view adequacy. It repairs overloaded wording so the exact architecture, structure, description, view, publication, source, relation, characteristic, mathematical-lens, evidence, assurance, gate, work, decision, causal-use, release, or ordinary-prose use becomes recoverable.

Builds on. E.10, E.10.ARCH, A.22, C.30, C.30.ASV, C.2.P, A.6.P, A.6.F, C.29, C.16.P, C.16, C.25, E.17, and E.8.

Coordinates with. C.30.TGA-FLOW-REL, C.30.LCA, C.30.ILC, exact C.30.* structure/view patterns, A.10, B.3, A.20, A.21, C.11, C.28, A.15, exact work/release/publication patterns, and J.4.

Use this pattern when architecture or structure wording hides which object is live.

#Relations

#Content

#Use this when

Use this pattern when architecture or structure wording hides which object is live.

Typical triggers:

• architecture, architecture description, architecture model, architecture diagram, architecture map, architecture dashboard, architecture score;
• structure, structural view, structural model, layer, module layout, block, component structure, interface structure;
• graph, flow, TGA graph, 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/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/interface claim becomes architecture by default.

What this buys. The reader can recover the live object, block the overread, and move to the exact pattern: selected structure under A.22, architecture description under C.30, architecture structural view under C.30.ASV, TGA-flow relation under C.30.TGA-FLOW-REL, control-structure view under C.30.LCA, mathematical lens under C.29, characteristic/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 what object the architecture or structure wording is actually naming, then either apply the exact architecture/structure pattern directly or use one architecture-structure repair note to assign the claim elsewhere.

Not this pattern when.

• If the live object is already a selected structure, use A.22 directly.
• If the live object is already ArchitectureOf@Context or ArchitectureDescription@Context, use C.30 directly.
• If the live object is already an architecture structural view, use C.30.ASV or an exact C.30.* view pattern directly.
• If the live claim is evidence, assurance, gate, work, decision, causal-use, release, mathematical-lens adequacy, characteristic/scale construction, quality characterization, source-transfer, or relation construction, use the exact pattern for that claim after any architecture/structure wording is demoted or assigned.

#Problem frame

Working engineers often say "architecture" or "structure" while pointing at a useful artifact: a diagram, model, graph, table, dashboard, ADR, code-agent relation graph, neural-network block diagram, benchmark result, or source document. Ordinary speech is acceptable; FPF-force-bearing prose is not.

The repair question is:

What live object does the architecture or structure wording name, and which exact FPF pattern now carries the claim?

The live object may be:

• selected structure under A.22;
• an ArchitectureOf@Context claim or ArchitectureDescription@Context under C.30;
• an ArchitectureStructuralView@Context or exact C.30.* subcase;
• a publication, view, face, PublicationUnit, carrier, dashboard, ADR, source document, or source-return relation under C.2.P / E.17;
• a relation construction under A.6.P;
• a function-like carrier under A.6.F;
• a mathematical-lens adequacy claim under C.29;
• a characteristic, scale, score, coordinate, threshold, or quality-coordinate claim under C.16.P or C.16;
• a Q-bundle or quality-characterization claim under C.16.Q, C.25, or E.21;
• an evidence, assurance, gate, work, decision, causal-use, release, or method claim under its exact pattern;
• ordinary prose with no current FPF force.

#Problem

How can FPF repair architecture or structure wording without:

• creating U.Architecture;

• treating architecture and structure as one fused kind;

• treating a description, view, diagram, graph, dashboard, source, ADR, model, or publication as the architecture itself;

• assigning all function, flow, module/interface, signature, control, evidence, assurance, gate, decision, work, quality, mathematical-lens, or source claims to architecture;

• duplicating first-stage repair lists inside A.22, C.30, C.30.ASV, and every exact C.30.* subpattern?

#Forces

#Solution

Repair architecture/structure wording by producing an architecture-structure repair note or an equivalent local rewrite.

Minimum fields:

ArchitectureOrStructureRepairNote:
  triggerSpan:
  boundedTextSpanOrPublicationUnit:
  encounteredObjectKind:
  candidateLiveObjects:
  selectedLiveObject:
  sourceOrPublicationStack?:
  relationClaimSlice?:
  functionCarrier?:
  structureKindOrArchitectureQuestion?:
  characteristicOrQualityClaimSlice?:
  mathematicalLensClaimSlice?:
  projectSideClaim?:
  exactReceivingPattern:
  repairedWordingOrDemotion:
  admissibleUse:
  nonAdmissibleUse:
  remainingReaderMove:
  disposition:

Use the note only when the repair must remain inspectable. A direct local rewrite is enough when one sentence clearly names the live object and exact receiving pattern.

#Recovery sequence

1. Capture the trigger. Copy the architecture or structure wording and the sentence that uses it.
2. Recover the encountered object. Decide whether the text points to a selected structure, architecture claim, description, view, diagram, graph, model, dashboard, ADR, source document, carrier, publication, function, module/interface, signature, flow, control, score, quality term, evidence, gate, work, decision, release, or ordinary prose.
3. Recover source/publication first when live. If the wording relies on a source, publication, view, face, PublicationUnit, dashboard, ADR, file, carrier, or source-return relation, apply C.2.P for the source/current and publication stack before assigning the architecture or structure claim.
4. Choose the architecture/structure object.
   • selected structure -> A.22;
   • architecture claim or architecture description -> C.30;
   • architecture structural view -> C.30.ASV;
   • TGA-flow relation -> C.30.TGA-FLOW-REL;
   • control-structure view -> C.30.LCA;
   • cross-scope conflict/frustration triage -> C.30.ILC;
   • exact C.30 subcase -> that subpattern.
5. Exit non-architecture claims. If the sentence uses architecture wording to carry relation, function-like carrier, mathematical lens, characteristic/scale, quality, evidence, assurance, gate, work, decision, causal-use, release, or method force, send that force to the exact pattern and keep this pattern only for the architecture/structure wording repair.
6. State admissible and non-admissible use. Say what the reader may do with the repaired wording and what non-admissible adjacent interpretation is blocked.
7. Return to the subject pattern. Stop after the exact receiving pattern or ordinary-prose demotion is named.

#Direct receiving-pattern exits

#Refresh and reopen conditions

Reopen or narrow C.30.P when current pattern-language ecology changes the first architecture/structure entry:

• a new exact C.30.*, structural-view, TGA-flow, LCA/control, module/interface, mathematical-lens, characteristic, evidence, assurance, gate, work, decision, causal-use, release, or publication pattern can receive one row directly;
• current architecture-description, view, model, decision-record, or architecture-documentation practice changes one adopted distinction in C.30.P:7;
• J.4 entry projection changes the first practical entry for hidden architecture/structure wording;
• a receiving pattern starts copying first-stage architecture/structure trigger lists that belong here;
• C.30.P begins to act as a registry of architecture topics rather than a wording-use repair pattern for hidden live objects.

The refresh action is to remove, narrow, or redirect the first-stage row. It is not to preserve old exits as history.

#Worked cases

#Reduced SoTA row

Current architecture-description, model, view, and decision-record practice treats architecture as distinct from architecture descriptions, models, views, viewpoints, diagrams, and decision records. FPF adopts that line only where it changes action guidance: examples, non-use boundaries, exact exits, source-return conditions, and conformance checks.

This row is live in this pattern because it blocks diagram-as-architecture, graph-as-proof, view-as-structure-kind, publication-as-claim, and ADR-as-decision overreads. It does not import any external standard as FPF ontology.

#Conformance checklist

#Common anti-patterns

#Related patterns

• E.10 catches architecture/structure wording and selects this pattern only when the live object is hidden.
• E.10.ARCH defines the shared wording-use recovery order and applicability row.
• A.22 governs selected structure and structural views as structure.
• C.30 governs architecture descriptions and ArchitectureOf@Context.
• C.30.ASV governs architecture structural views.
• Exact C.30.* patterns govern their own structure/view adequacy questions.
• C.2.P recovers source, publication, view, face, PublicationUnit, carrier, and source-transfer use.
• A.6.P repairs relation construction; A.6.F repairs function-like carrier wording; A.6.M repairs module/interface relation wording.
• C.16.P and C.16.Q repair characteristic/scale and quality/evaluative characterization wording before score or quality use.
• C.29 governs mathematical-lens adequacy and does not become architecture by analogy.

#C.30.P:End

Last Updated: 2026-05-31 — this section last modified in upstream FPF commit 16cd3138 (github.com/ailev/FPF)