C.32.CONWAY:4.1 - Keep acting, influence, and correspondence facts separate

1. Name the domain action and changed referent. Identify changedReferentRef independently. Add actualTransformationRef only when A.3.4 independently admits one bounded change of that same continuing referent; keep actor-side and Work-to-change relations under their subject patterns. Architecture influence identifies none of those facts.
2. Add acting and performance facts only when claimed. Every precise actual performer is one exact U.System recovered through A.13. Claimed performance requires one exact dated U.Work independently admitted through A.15.1 and the exact actor-side or Work-to-change relation needed by the claim. Add an obtaining occurrence of a directly admitted U.SystemRoleAssignment species under A.2.1 and F.6 performedUnderAssignment(W, RA) only when this frame or its receiving use expressly consumes precise assignment-bound attribution through the same obtaining A.13 assignment; then compare S with RA.HolderSystemSlot. F.6 identifies neither assignment nor performer, and missing or failed F.6 leaves the Work intact. Use A.15.1 CC-A15.1-17 when several systems jointly perform the top-level Work or when the use instead needs a parent Work with separately performed child occurrences.
3. Name every influence source by kind. Architecture, selected structure, Work, communication, constraint, and candidate-synthesis results retain their kinds and direct influence relations. Influence alone supplies no system identity, system-role kind or assignment, Work, performer status, changed-referent identity, or transformation participation.
4. Select one architecture pair. For an exact row, name one obtaining influence-source C.30 ArchitectureRelation and one obtaining transformed-side C.30 ArchitectureRelation, with each exact holon and selected-U.Structure participant. Their architecture-bearing holons may differ from every acting system. Record equality only when independent actor and architecture-bearer facts establish it. If either side is only candidate, required, desired, or expected, keep its exact ArchitectureClaim and the pair in the synthesis frame; do not assert an exact pair row.
5. Map only structures and characteristics that change the candidate. Name the source-side selected structure, transformed-side selected structure, expected gain, known loss, evolution window, pattern for the next question, and source-return condition. For each affected characteristic, reference only the few current C.32.ACS criteria rows and any declared C.25 Q-Bundle slots that make this trade-off real.
6. Prepare four candidate forms. Change the influence-source side, change the transformed architecture, change both, or keep a bounded mismatch with an explicit cost and reopen trigger.
7. Use C.29 only for structural-similarity claims. A correspondence row does not establish homomorphism, equivalence, or architecture adequacy.
8. Stop at the next governed claim. Send comparison, selection, publication, choice, decision, evidence, assurance, gate, Work, or organization-governance claims to their direct patterns.