CC-C32P2S-1 | The card names the exact problem claim or pressure, described holon, architecture question and intended use, first pattern to use, and at least one architecture-relevant structure or unknown-structure slot; scope, window, and selected transformation-flow structure are named only when material. |
CC-C32P2S-2 | Each architecture use keeps the exact described holon, obtaining C.30 ArchitectureRelation occurrences and their selected-structure participants, and any affirmative, negative, unresolved, candidate, required, desired, or expected ArchitectureClaim content separate; no description or publication record carries the architecture by itself. |
CC-C32P2S-3 | Architecture characteristics are separate from functional demands, measurements, eval programs, eval results, Q-bundles, comparison rules, and decisions. |
CC-C32P2S-4 | The structural-information slots in the P2S card record unknown, selected, expected, actual, captured, handed-off, latent or hidden, lost, and returned structure when those slots are live. |
CC-C32P2S-5 | Use C.32 for candidate synthesis and the applicable patterns for comparison and selection. A score or prose preference alone does not establish a selection result. |
CC-C32P2S-6 | When a project architecture decision is current, use C.32.PAD; for an ADR-like publication, use C.32.ADR and the applicable publication patterns. |
CC-C32P2S-7 | Use A.3.1 for Method identity, A.3.2 for MethodDescription membership, and A.15-family patterns for alignment, work-plan, readiness, and performed-work claims. Identify every actual transformation under A.3.4. For every claimed Work-to-change link, cite the relation and the pattern or local A.6.RCD claim used to check it. Keep production-work, entity-identity-inception, and production-completion as separate local A.15.PROD claims. The P2S card carries refs and expected structure effects only. |
CC-C32P2S-8 | For measurement, Q-bundle, mathematical-lens, eval, improvement, G.11 currentness refresh, and E.18 transformation-flow slice-local refresh claims, use C.16, C.25, C.29, C.32.ACE, E.23, G.11, or E.18 as applicable. |
CC-C32P2S-9 | Architecture-influence cases keep the changed referent, any actual A.3.4 transformation, both exact C.30 architecture sides or modal claims, every influence source’s exact kind and obtaining direct relation or precise provisional disposition, and the C.32.CONWAY synthesis-local frame or exact pair row separately recoverable. |
CC-C32P2S-10 | When actual-structure feedback is the current question, check subject-side U.Structure values recovered under A.22 from obtaining relation occurrences, applied constraints, invariants, or other selected-organization facts, together with architecture-characteristic results and relevant functional-characteristic or capability implications. Use operation, use, inspection, measurement, eval result, telemetry, decay, stronger-structure inspection return, or a decision-repair trigger as applicable. An earlier P2S use may stop with its current result and next receiving action under §4 without adding a feedback claim. |
CC-C32P2S-11 | Selected and expected structures, methods, plans, models, decisions, descriptions, evaluation results, publications, and transfers remain distinct from actual structures and actual transformations. Resemblance does not establish conformance. Shared work, adjacency, common referents, or one flow establishes neither transformation composition nor partlessness. |
CC-C32P2S-12 | The PumpSkid 7 replay independently identifies mounting, wiring, connection, and commissioning-related changes; cites exact assembly and commissioning work plus the work-to-change relations and their declared predicates; separates entity-identity inception from later historically indexed production completion; and routes actual-structure description, architecture-characteristic evaluation, and return without fabricating conformance or one composite transformation. |