| The reliance relation is treated as the structure. | Recover the exact constituents, selected obtaining relation occurrences, applied constraints, and named use frame. When a neighboring source-description, source-use, base-dependence, grounding, evidence, lens, simulation, extraction, or representation reliance claim is current, name that exact relation and the content that defines or tests it separately. |
| The diagram, graph, table, dashboard, or publication form is the structure. | Recover the exact description or view and its publication occurrence, form, or carrier when relevant. If the account claims a source-description, base-dependence, grounding, evidence, lens, simulation, extraction, or representation relation, identify and test that relation separately. |
| A transformation-flow graph expression is the structure in every sense. | Use E.18 for one selected TFS and its internal paths, crossings, and valuations; use E.18.NET for a selected network of independently identified TFS members and exact cross-member relations; use E.18.2 and C.29 for the graph expression. A.22 supplies only the selected-structure identity, and C.30.TFS-REL defines and tests the architecture-to-transformation-flow relation claim. |
| A mathematical lens output is the structure. | Use C.29 for lens-use result and admissibility, and cite MathLensUseOutputRef only through C.29 lens-use result, preserved structure, lost structure, and stop-condition discipline. |
| A structure is cited as sufficient basis for evidence reliance, assurance, safety, causality, or gate passage. | Use A.10 for claim-bound evidence reliance, G.6 when a citable evidence-provenance path is needed, B.3 for an actual named assurance claim, the safety pattern for safety, C.28 for causal use, A.20 for internal-constraint validity, and A.21 for an actual gate decision. |
| A structure is a decision or work record. | Use C.11 or the project-side decision pattern for the decision, A.15 for the exact work-family object, and C.2.1 for an episteme describing it. A.20 or A.21 applies only when an internal-constraint result or gate decision is at issue. |
| Architecture is treated as identical to a selected structure. | Use C.30 to test the direct ArchitectureRelation between the exact holon and selected structure. Recover the architecture claim and any description or view separately. |
| Function, module, interface, platform, layer, stack, block, expert, cache, router, or gate becomes a root kind by appearing in structure prose. | Use C.30.STRAT for an ambiguous source label, then the definition or test required by the recovered claim: A.6.F for function, A.6.M for a module-interface relation, A.6.0 for a signature, A.6.5 for relation slots, A.6.B for boundary norms, A.6.C for contract unpacking, A.6.P:4.11a for service or access wording, E.18 for transformation-flow structure, or C.30.ASV for an architecture structural view. Apply any other direct pattern only for the claim it defines or tests. |