| 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 A.6.6, source-description, evidence, or lens relation and its definition or test; state the validation and stop conditions required by that relation or intended use, and add a structure-use return condition when §4.5 requires it. Use F.19:4 for any optional explanatory guard. |
| Loss-free extraction | An extracted or coarsened account hides a loss that changes the receiving use. | State what is preserved and lost, the supported use and any required validation boundary. Add a structure-use return condition under §4.5 or narrow the use so the hidden distinction is not relied on. |
| 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 information and any action still needed for the practitioner’s receiving question. |