| Tell | A project team says “architecture” while looking at a diagram, model, generated relation graph, ADR, or module list. C.30 asks which subject relations obtain, which A.22 structure is selected, whether the architecture relation obtains or the content is candidate or expected only, how the inspected material is being used, and what architecture move remains admissible. |
Show: U.System | A payment system, plant, vehicle, product platform, AI-agent system, or neural-network model has actual subject relations from which functional, flow, control, module-interface, information, placement, scale, work, evidence, or declared logical structures can be selected. When the C.30 predicate is satisfied, the selected structure stands in an ArchitectureRelation to that holon; a claim or publication about it is not the relation. |
Show: U.Episteme | An ArchitectureClaim, architecture description, model, view, generated relation graph, ADR-like note, safety-case view, or dashboard is an episteme or publication-side object. It can state or describe actual, negative, unresolved, candidate, or expected content and can participate in source or grounding relations, but it does not create the selected structure, ArchitectureRelation, evidence sufficiency, gate result, assurance case, or project decision. |