C.32.P2S:5 - Archetypal Grounding

Tell. The architect carries pressure into structure: first by finding which selected structures are missing or inadequate, then by constructing alternatives, deciding what will be pursued, enabling exact domain work, and watching which subject-side structures actually obtain under operation. An actual transformation is introduced only when its own A.3.4 basis is grounded.

First-minute use slice. A plant architect sees that expected throughput and actual throughput diverge after a layout change. The first P2S card pass names the production cell as described holon, the throughput-after-layout-change architecture question, operating-shift qualification window, pressure kind actualStructureDivergesFromExpectedStructure, first pattern to use C.30, unknown structure material-flow bottleneck bearer, selected structure candidate buffer placement, and pattern for the next claim C.32. The card does not yet add a PAD decision, work plan, or eval result; those refs appear only when their questions become current.

Lens-use slice. If the plant team builds a DSM or epiplexity-style lens over stations, buffers, and routing events, P2S records only the architecture use: which dependency or learnable structural content was preserved, which flow distinction was compressed away, which selected structures the lens can inform, and which lens-use return condition sends the claim back to C.29. The lens result is not architecture adequacy, an eval result, or a decision.

Show A - built asset and technical system. A clinic has rising instrument-turnaround delays and infection-control pressure. The first P2S move does not ask for a better diagram. It names the clinic service system as described holon, the turnaround-and-contamination architecture question, intended operating use, applicable scope and window, candidate structure kinds, architecture characteristics, and uncertainty: room layout, sterile and contaminated flows, equipment modules, tray interface, maintenance work, throughput, contamination isolation, maintainability, and surge adaptability. Candidate synthesis develops these alternatives: a centralized autoclave bay, distributed sterilization modules, and a reusable tray-interface change. Use C.32.PAD for the decision selecting one configuration, C.30.AD and C.32.ADR for its descriptions and publication, and A.15-family patterns for construction and operating work. During operation, measure actual turnaround, contamination events, maintenance burden, and actual-structure feedback triggers.

Show B - Method, organization and Work. Inspection work catches ontological errors late. Recover what the source’s “review practice” names before choosing the described holon. When the question concerns how source recovery, judgement and repair connect, the bearer can be the Method itself under A.3.1; candidate alternatives can change that sequence or its feedback. When staffing or coordination among performers is the problem, recover the review organization-as-system and its relevant structures. If a performed review is the subject, recover each actual performer through A.13 and identify the U.Work occurrence independently through A.15.1. Use C.32.HCS and C.32.ACS to bind characteristics to that bearer and the required result. Use E.10.ROLE to separate any local checker kind, classification, current assignment, direct review-relation position, function claim, organization position, and ordinary audience label. Candidate synthesis develops modal alternatives. Establish any claimed actual subject relations independently. For later actual inspection Work, add F.6 only when the flow or receiving use expressly represents precise assignment-bound attribution. Telemetry separately shows whether errors are caught earlier.

Show C - architecture-influence and transformed-side co-synthesis. A team wants a modular product architecture but its toolchain, team communication, release method, and evidence workflow only support one tightly coupled build. The team uses C.32.CONWAY within the P2S flow: those typed influence sources and their direct relations remain separate from both exact C.30 architecture sides, the changed referent, any actual transformation, acting Systems, assignments, and Work. Candidate families include changing the product modules only, changing the influence-source structures only, changing both, or accepting a bounded mismatch while retaining a named correspondence-frame return condition. The decision states which side changes now, what architecture characteristics are protected, what Work and exact work-to-change relations realize the change, and what operation or delivery feedback can return to the C.32.CONWAY correspondence frame or to decision repair.

Show D - PumpSkid 7 realization and return. Architecture pressure calls for a modular pump-skid with selected module and placement structures; use C.32.PAD for the project architecture decision. Assembly work W-PS7-ASSEMBLY and later commissioning work W-PS7-COMMISSION are separate Work occurrences admitted under U.Work by A.15.1. Mounting change T-PS7-MOUNT, wiring change T-PS7-WIRE, fluid-connection change T-PS7-CONNECT, and commissioning-related change T-PS7-COMMISSION are each independently identified under A.3.4. Where the assembly or commissioning work is asserted to cause a change, cite the work-to-change relation and its declared predicate. Shared work, temporal adjacency, and one selected pump-skid configuration do not establish one composite transformation. The local A.15.PROD entity-identity-inception claim uses the applicable PumpSkid 7 identity-specification edition, its applicability basis, work-to-change and change-to-identity facts, and inceptionBoundary; it need not assert a composite transformation. Later commissioning can remain production work until subject-state facts at completionBoundary satisfy the applicable production-completion-criterion edition; only then can a separate historically indexed completion claim be written. A later C.30.AD or C.30.ASV record describes the actual structure; use C.32.ACE to evaluate service-access coupling. When coupling is worse than the selected expectation, the eval result returns to decision repair or new synthesis. Neither the description, evaluation, identity-inception claim, completion claim, nor shared assembly work proves conformance to the selected architecture or transformation composition.