| Structure-as-document | A diagram, table, dashboard, relation graph, or prose section is called the structure. | Recover publication, publication-form, description, or view relation; name the structure separately only when selected organization is being claimed. |
| Reliance-interpretation-as-structure | A trace used as source basis, benchmark, lens output, model, or simulation is treated as the structure. | Name the exact A.6.6, source-description, evidence, or lens relation and its definition or test; state its validation boundary and stop or return condition, using F.19:4 for any optional explanatory guard. |
| Loss-free extraction | Extracted or coarsened structure is used without lost structure or structure-use return. | Add preservedStructure, lostStructure, validationBoundary, and structureUseReturnCondition. |
| Architecture root-kind rebound | Structure work reintroduces U.Architecture or treats architecture as parallel to structure. | Use ArchitectureRelation and C.30; keep A.22 as the upstream selected-structure EntityOfConcern. |
| Lens ontology import | A mathematical lens output becomes the imported ontology. | Use C.29 for the lens, cite it through C.29 lens-use result, preserved structure, lost structure, and stop-condition discipline. |
| Sterile precision rewrite | The text removes overread but no longer tells the practitioner what to do. | Restore the surviving action: structure card, structure-claim reliance relation, Description or view, StructureUseReturnCondition, or FPF pattern application. |