| “The architecture is documented in this view set.” | Treat the set as a package of separately identified architecture-description epistemes only if each has an exact claim graph, one EntityOfConcern, and effective U.ReferenceScheme. A member is a U.View only with its exact viewpoint episteme and independently obtaining E.17.0 conformance relation. The set is not the architecture, relation occurrence, or selected structure. |
| A transformation-flow graph expression is included in an architecture document. | Use E.18.2 for the mathematical graph description, E.18 for the selected flow structure, path, and crossing semantics, and C.30.TFS-REL when the graph is used by architecture. C.30.AD records the exact description and its path from the source expression into that use; add a source-return condition only if a stronger use must return to the named source or exact defining or constraining ClaimGraph. The graph expression or rendering creates no actual transformation. |
| A model card claims deployment safety. | Use C.30.AD only if the card publishes or represents a description episteme about an exact architecture-side object. Use the direct domain pattern for the safety or release claim, B.3 for a separate named safety-assurance claim, A.10 for evidence, and A.21 only for a named gate decision. |
| A generated code-agent relation graph shows modules and calls. | Treat the graph as a generated representation or source publication. Recover observed, inferred, and unknown relations; use C.30.ASV or C.30.TFS-REL only when an exact architecture structural view or flow relation is being used. Generation and display establish neither relation occurrence nor view membership. |
| A multi-view description set has functional, deployment, control, and evidence-reuse views. | Identify every description episteme separately, including its EntityOfConcern and scheme. Each cited view also names its exact viewpoint and obtaining conformance relation; an ArchitectureDescriptionViewUseClaim records set use without minting membership. Evidence-reuse claims do not stay inside C.30.AD. |
| A plant safety architecture description combines control, deployment, evidence, and operator-view material. | C.30.AD records exact description identities, view conformance, description-set use, and correspondence among views. Use C.30.LCA for the control view and A.10, G.6, or B.3 for evidence or assurance. If a system-role assignment, F.6 Work attribution, authority, allocation, or responsibility is claimed, cite its separate direct relation, or record the exact missing governor if a rule needed to state or test that claim is absent. |
| A product-line platform document reuses module-interface, variability, and deployment views across products. | C.30.AD records exact description epistemes, architecture claims carried as content, structural views, and source-to-use paths for reused views. A source-return condition is added only when a product-specific use exceeds the declared reuse boundary. A.6.M normalizes module-interface claims and routes any proposed direct relation; C.31.RSA accounts reusable structure or bespoke residue only after structure refs and accounting frame are declared. |
| A multi-view architecture description says local optimization at one declared holon level creates frustration in another. | C.30.AD records set use, correspondence, and each view use boundary. Use C.30.ILC for the residual; use C.29 only when the description contains a recoverable level or scale mapping with preserved and lost structure. |
| An operations model groups individual queues and interactions into three broad bands. | Name the operating subject, the fine and coarse description structures, the grouping map, the distinctions preserved and lost, and the use of the three-band view. This establishes a coarser description, not three subject levels. Use C.30.STRAT, C.29, A.22, or C.30 only if their separate subject or model claims are needed and supported. |
| An architecture document compares residual-reducing candidate decompositions or optimization moves. | Record with C.30.AD only the exact description or publication use of that comparison. Use C.32.MLAO for residual-reducing frames, C.32 for candidate palettes, A.19.CPM or A.19.SelectorMechanism for comparison and selector-policy use, C.18 or C.19 for archives, fronts, and current-pool treatment, G.5 for selected-set result declaration, and C.11 for final local choice. For a measurement claim, use the pattern that defines or tests the measured characteristic and result. |
| A review note, dashboard, or generated report describes gaps in an architecture description rather than the architecture itself. | Treat the second description as its own U.Episteme and name its source, representation, publication, review, or evaluation relation directly. Keep the path to the first description and its EntityOfConcern visible without treating either description as architecture, residual, decision, or proof. |