| CC-C30-1 Architecture name. | A conforming use distinguishes actual subject relations and selected A.22 structure from candidate or expected content, identifies an obtaining ArchitectureRelation only when its predicate is satisfied, and gives every ArchitectureClaim one EntityOfConcern and effective reference scheme. It also names concern, admissible-use frame, and the source, description, view, representation, publication form, or other use of inspected material. | Recover the direct relation for an actual claim, retain modal content at its supported scope, or keep a recognition cue. Ordinary prose can suffice; use the question card when its organization helps. |
CC-C30-2 No U.Architecture. | The pattern use does not mint or rely on a root U.Architecture. | Recover the A.22 structure and ArchitectureRelation, or keep candidate or expected content in a claim and use the pattern that defines or tests any other claim. |
| CC-C30-3 EntityOfConcern and Description-episteme boundary plus specification-use separation. | Actual subject relation, selected structure, ArchitectureRelation, claim, description, view, representation, publication occurrence, publication form, carrier, decision, evidence, and Work stay distinct. | Recover the object doing each job; a description, specification use, diagram, list, file, or publication creates no subject-side architecture fact. |
| CC-C30-4 Description subject. | Every architecture description has one C.2.1 EntityOfConcern—holon, obtaining ArchitectureRelation, or selected structure—and effective reference scheme; architecture-claim refs remain optional content or trace. | Recover the subject and scheme, or split the description from the bounded architecture claim. |
| CC-C30-5 View and publication boundary. | The same description episteme is U.View only through an independently obtaining E.17.0 conformance relation to one viewpoint; representation, publication occurrence, form, carrier, and publication currentness remain separate. | Apply C.30.AD, E.17.0 or E.24.PUB to the respective description, view or publication question; use C.29 only for a remaining mathematical representation issue. Remove view membership inferred solely from authoring or presentation. |
| CC-C30-6 Small output before heavy record. | Ordinary use may stop once the needed next architecture move and the basis for any separate claim are clear. Retain or share that account; use the question card when the receiver needs its additional organization. | Remove needless form expansion, or identify the missing content that the fuller account must supply. |
| CC-C30-7 Structure-kind boundary. | Structural-view claims apply C.30.ASV; module, function, flow, control, work, evidence, scale, and decision claims do not collapse into C.30. | Name the structure kind, state the structural view if needed, or use the pattern that defines or tests the separate claim. |
| CC-C30-8 Characteristic assignment. | Quality, measure, score, metric, modularity, and ility wording recovers its bearer and the applicable characteristic pattern before use. | Identify the bearer and characteristic under :4.5 in the working account; retain only a recognition cue if the needed meaning remains unresolved. |
| CC-C30-9 Non-architecture claim kind. | For each evidence, assurance, causal, gate, work, decision, publication-use authority, mathematical-lens, measurement, or release claim, name its kind and the FPF pattern that defines or tests it. | Keep the C.30 record limited to architecture and selected-structure adequacy. |
| CC-C30-10 Useful action. | The repaired wording leaves an admissible action: name the architecture claim, recover the use of inspected material, state an architecture structural view, add a source or reliance relation, add a SourceReturnCondition, or apply the FPF pattern that defines or constrains the claim kind being made. | Restore that action, or classify the phrase as reduced-use cue, quote-only wording, blocked transfer, or incomplete rewrite. |