CC-C30P-1 | The repair names the trigger span, encountered FPF kind or reference, selected use under repair, subject pattern, admissible use, non-admissible use, and remaining reader use. |
CC-C30P-2 | A diagram, model, graph, dashboard, ADR, source, publication, view, face, PublicationUnit, file, carrier, or rendering is not treated as architecture or structure by appearance. |
CC-C30P-3 | Direct A.22, C.30, C.30.ASV, or named C.30.* use applies the subject pattern directly when the selected-structure claim being made, architecture relation, architecture-description use, structural-view use, or named C.30 subcase is already recoverable. |
CC-C30P-4 | Source-use, currentness, and publication-to-carrier relation recovery uses C.2.P before architecture or structure claim use only while the relevant distinction remains hidden; an already recovered claim goes directly to its subject pattern. |
CC-C30P-5 | Function-like, relation-like, mathematical-lens, characteristic and scale, quality, evidence, assurance, gate, work, decision, causal-use, release, and method claims are assigned to their subject patterns. |
CC-C30P-6 | The repair does not mint U.Architecture, ArchitectureStructure, a generic architecture head, or mandatory architecture-repair record. |
CC-C30P-7 | The subject architecture or structure pattern keeps its own invariant central and carries at most a thin pointer back to this pattern. |
CC-C30P-8 | The repaired wording preserves one useful admissible reader use; type-correct but inert architecture wording is not recovered by value. |