#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 selected structure, architecture relation, architecture-description use, structural-view use, source-return relation, or named C.30 subcase is hidden before a reader applies A.22, C.30, C.30.ASV, or a named C.30.* pattern.

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

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.TFS-REL, C.30.LCA, C.30.ILC, named C.30.* structure and view patterns, A.10, B.3, A.20, A.21, C.11, C.28, A.15, E.11, and work, release, and publication patterns defining or constraining those claims.

E.10.ARCH applicability rule. When E.10 encounters architecture or structure wording whose selected structure, architecture relation, architecture-description use, structural-view use, source-return relation, source label, or neighboring claim is hidden, E.10.ARCH selects C.30.P only until the use under repair and subject pattern are recovered. C.30.P then stops applying; it does not become a registry of architecture topics or a substitute for A.22, C.30, C.30.AD, or named C.30.* patterns.

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

#Relations

#Content

#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.

#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 architecture-operation diagram, benchmark result, or source document. Ordinary shorthand is acceptable in FPF-governed prose when the intended use is recoverable. If the artifact is named by a source label such as block, layer, expert, cache, router, or gate whose technical meaning remains unclear, use C.30.STRAT before assigning the recovered use locally.

The repair question is:

Which selected structure, architecture relation, architecture-description use, structural-view use, source-return relation, or neighboring claim does the wording name, and which FPF pattern defines or constrains that claim?

The architecture or structure use under repair may be:

• selected structure under A.22;
• an ArchitectureOf@Context claim under C.30, a thin architecture-description bridge under C.30, or the full architecture-description mechanism under C.30.AD;
• an ArchitectureStructuralView@Context or named C.30.* subcase;
• a publication, view, face, PublicationUnit, carrier, dashboard, ADR, source document, or source-return relation under C.2.P or E.17;
• a relation construction under A.6.P;
• a function or functionality-kind use under A.6.F;
• a mathematical-lens use 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 subject pattern;
• ordinary prose with no FPF-governed use being made.

#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 named C.30.* subpattern?

#Forces

#Solution

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

Minimum fields:

ArchitectureOrStructureRepairNote:
  triggerSpan:
  boundedTextSpanOrPublicationUnit:
  encounteredFPFKindOrReference:
  candidateClaimUses:
  selectedClaimUse:
  sourcePublicationRelationSet?:
  relationClaimSlice?:
  functionOrFunctionalityClaim?:
  structureKindOrArchitectureQuestion?:
  characteristicOrQualityClaimSlice?:
  mathLensClaimSlice?:
  projectSideClaim?:
  relationFunctionClaimRef:
  repairedWordingOrDemotion:
  admissibleUse:
  nonAdmissibleUse:
  remainingReaderUse:
  disposition:

Use the note only when the repair must remain inspectable. A direct local rewrite is enough when one sentence clearly names the selected-structure claim being made, architecture relation, architecture-description use, structural-view use, source-return relation, or subject pattern.

#Recovery sequence

1. Capture the trigger. Copy the architecture or structure wording and the sentence that uses it.
2. Recover the encountered FPF kind or reference. Decide whether the text points to a selected structure, architecture claim, description, view, diagram, graph, model, dashboard, ADR, source document, carrier, publication, stratification-wording case or source-label case for C.30.STRAT, function, module-interface relation, signature, flow, control, score, quality term, evidence, gate, work, decision, release, or ordinary prose.
3. Recover source-publication relations before architecture assignment. If the wording relies on a source, publication, view, face, PublicationUnit, dashboard, ADR, file, carrier, or source-return relation and a source-use, source-currentness, or publication distinction remains hidden, apply C.2.P before assigning the architecture or structure claim. If that distinction and its subject pattern are already recoverable, use the subject pattern directly.
4. Choose the subject pattern for the architecture or structure use.
   • selected structure -> A.22;
   • ArchitectureOf@Context, selected architecture-relevant structure, or thin conditional ArchitectureDescription@Context bridge use -> C.30;
   • full ArchitectureDescription@Context mechanism -> C.30.AD;
   • architecture structural view -> C.30.ASV;
   • architecture transformation-flow relation -> C.30.TFS-REL;
   • control-structure view -> C.30.LCA;
   • cross-scope conflict or frustration triage -> C.30.ILC;
   • stratification wording or source-label wording such as layer, level, tier, stack, ladder, rung, block, expert, cache, router, or gate -> C.30.STRAT while the label's technical meaning remains unclear, before choosing the final subject pattern;
   • named C.30 subcase -> that subpattern.
5. Assign non-architecture claims to their subject patterns. If the sentence uses architecture wording to carry relation, function or functionality, mathematical-lens, characteristic and scale, quality, evidence, assurance, gate, work, decision, causal-use, release, or method claim, apply the subject pattern for that claim and keep this pattern only for the architecture or 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. Stop C.30.P after assignment. Stop after the subject pattern or ordinary-prose demotion is named.

#Subject pattern assignments

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.

#Refresh and reopen conditions

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

• a named C.30.*, structural-view, architecture transformation-flow, LCA or control, module-interface, mathematical-lens, characteristic, evidence, assurance, gate, work, decision, causal-use, release, or publication pattern now governs one row directly;
• source-current architecture-description, view, model, decision-record, or architecture-documentation practice changes one adopted distinction in C.30.P:7;
• README, ToC, E.11, retrieval, or local Problem-frame entry cues change the first practical entry for hidden architecture or structure wording;
• a subject pattern starts copying first-stage architecture or 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 selected structure, architecture relation, architecture-description use, structural-view use, source-return relation, or named C.30 subcase.

The refresh action is to remove, narrow, or reassign the first-stage row. It is not to preserve old assignment wording 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, subject-pattern assignments, source-return conditions, and conformance checks.

These distinctions block diagram-as-architecture, graph-as-proof, view-as-structure-kind, publication-as-claim, and ADR-as-decision overreads. This use does not import any external standard as FPF ontology.

#Conformance checklist

#Common anti-patterns

#Related patterns

• E.10 catches architecture or structure wording and selects this pattern only when the selected structure, architecture relation, architecture-description use, structural-view use, source-return relation, or named C.30 subcase 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 grounded ArchitectureOf@Context adequacy and thin conditional ArchitectureDescription@Context bridge use.
• C.30.AD governs the full architecture-description mechanism when ArchitectureDescription@Context is the EntityOfConcern under repair.
• C.30.ASV governs architecture structural views.
• C.30.STRAT recovers unclear stratification or source-label meaning before C.30.P assigns the recovered architecture or structure portion.
• Named C.30.* patterns define or constrain their own structure adequacy or view adequacy questions.
• C.2.P recovers source, publication, view, face, PublicationUnit, carrier, and source-use disposition.
• A.6.P repairs relation construction; A.6.F repairs function and functionality wording; A.6.M repairs module-relation and interface-specification wording.
• C.16.P repairs characteristic-and-scale wording, and C.16.Q repairs quality-term or evaluative characterization wording before score or quality use.
• C.29 governs mathematical-lens use and does not become architecture by analogy.

#C.30.P:End

Last Updated: 2026-09-10 — upstream FPF commit a87d0ef4 (github.com/ailev/FPF)