C.32.CONWAY:5 - Worked Correspondence Cases
| Grounded working case | Acting and performance facts | Influence-source and architecture-pair facts | Candidate work | Stop or return |
|---|---|---|---|---|
| Product family and manufacturing system | The product referent and bounded A.3.4 transformation are identified independently when actual change is claimed. The admitted manufacturing and certification Systems jointly perform dated architecturing Work, each through its basis: A.13 first, independent A.15.1 Work admission second, and F.6 afterward only for precise assignment-bound attribution; the direct Work-to-change relation remains separate. | One obtaining C.30 ArchitectureRelation connects the manufacturing-and-certification holon to its shared batch-line evidence structure; another connects the product-family holon to its current field-module structure. A Plant-A domain declaration defines the influence predicate between those exact occurrences, and current case facts satisfy it. Neither architecture-bearing holon nor architecture relation is inferred to be a performer. | Prepare manufacturing-cell change, product-module split, joint change, and bounded batch exception. | Stop at candidate preparation. Handle product choice or architecture decision under C.11 or C.32.PAD; factory Work authorization through its direct authority or permission relation or an A.21 gate; and certification evidence or assurance through A.10 or B.3. |
| Organization designing and operating a service platform | Each acting team or organization is used through its admitted U.System identity; any actual design or operations Work points to its basis: A.13 first, independent A.15.1 Work admission second, and F.6 afterward only for precise assignment-bound attribution. | Communication, deployment, test, and approval structures influence one service-platform architecture pair through their direct relations. | Prepare a service-boundary, platform-mediation, or bounded-coordination-cost change. If responsibility retargeting is proposed, name the exact responsibility predicate and old and proposed participants; otherwise mark that branch missing-governor instead of calling it a team or test role change. | Stop before an organization-redesign decision or authority claim and apply the exact predicate and test for that claim. Use G.5 for selected-set result declaration and C.32.PAD for an architecture decision. When publication is current, use E.17 for a source-backed publication face and return to source and E.24.PUB for the publication occurrence, form, carrier, audience, bounded use, and availability. |
| Review method influencing authored work products | The method description does not act. When review is performed, recover every precise performer’s A.13 core and independently admit the review Work under A.15.1; add F.6 only when precise assignment-bound attribution is current, and state any Work-to-change relation separately. | The review-method or evidence structure influences the authored-section architecture through its exact method-use, evidence-scope, or project influence relation. | Add a prospective exception-assignment requirement and evidence scope, change the Method step, change the work-product structure, or reject the automation candidate. | Stop before method-governance or publication claims. For method use, apply the direct predicate and the pattern that defines and tests it. For publication, use E.17 for a source-backed face and source return and E.24.PUB for the publication occurrence and audience availability. Use G.5 only when selected-set result declaration is current. |
| Instructional system changing learner capability | Each instructor or instructional organization is used through its admitted U.System identity; any actual teaching Work points to its basis: A.13 first, independent A.15.1 Work admission second, and F.6 afterward only for precise assignment-bound attribution. | Curriculum, feedback, and evidence structures influence the architecture claim about the changed learner-capability referent. | Prepare curriculum, a prospective feedback-assignment requirement, evidence scope, or bounded-cohort candidates. | Stop before educational policy, evidence-sufficiency, or ethical-mediation claims; state them under the exact policy predicate, A.10, or D.4 respectively. |
| AI-agent toolchain changing project work products | An admitted execution System performs any actual tool-call or authoring Work through its basis: A.13 first, independent A.15.1 Work admission second, and F.6 afterward only for precise assignment-bound attribution. | Toolchain control and evidence-refresh structures influence the transformed work-product architecture through exact relations; the toolchain architecture itself does not act. | Add supervision and refresh, change task decomposition, or keep bounded autonomy with source return. | Stop before safety, gate, release, or assurance claims; use the exact safety predicate, A.21 for a gate decision, the applicable authority or permission relation for release, and B.3 for assurance. |
Exact positive, distributed-performer, and network-local slice. In one Plant-A domain framework, PlantArchitectureInfluenceRelations-v3 defines BatchEvidenceArchitectureConstrainsModuleArchitecture(sourceArchitectureRelation, transformedArchitectureRelation, evolutionWindow). Its first participant is the obtaining C.30 ArchitectureRelation(ManufacturingCertificationSystem@Plant-A, BatchLineSharedEvidenceStructure@Current); its second is the obtaining C.30 ArchitectureRelation(ProductFamily@Current, FieldModuleBoundaryStructure@Current). Both occurrences are explicitly individuated under A.6.REL because this domain predicate uses them as participants. Plant-A facts satisfy that predicate over ProductFamilyModuleChange@2026Q3, so BatchEvidenceConstrainsFieldModules-17 is the exact obtaining influence occurrence and the EntityOfConcern of BatchEvidence-to-FieldModules-Row-17. This case-local predicate and occurrence do not mint a universal Conway relation.
The changed referent is independently identified as ProductFamilyFieldModuleBoundary@2026Q3. If the case also claims actual change, A.3.4 independently identifies FieldModuleBoundaryTransformation-17 : U.Transformation.
Before the candidate occurrence is called Work, A.13 recovers both collective performers for one shared scope, working situation, and window. The scope is ProductFamilyModuleChange@2026Q3; the situation is PlantAModuleTransitionArchitecturingSituation-17; and the window is 2026-07-14T09:00:00+03:00 through 2026-07-16T18:00:00+03:00. ManufacturingArchitectureTeam-A : U.System has boundary ManufacturingArchitectureTeamBoundary-A, comprising the rostered team members, their manufacturing-constraint decision channel, and the coordination interactions governed by ManufacturingArchitectureCoordinationMethod-v2. Its exact case-local action is ManufacturingBoundaryConstraintAction-17: select, revise, pause, or escalate manufacturing-feasibility constraints on the field-module boundary. It acts toward BatchFeasibleModuleBoundaryObjective-17 under the current batch-line capability, shared-evidence, and batch-exception conditions. CertificationArchitectureTeam-A : U.System has the distinct boundary CertificationArchitectureTeamBoundary-A, comprising its rostered members, certification-evidence decision channel, and the coordination interactions governed by CertificationArchitectureCoordinationMethod-v2. Its exact action is CertificationEvidenceConstraintAction-17: select, revise, pause, or escalate the certification-evidence obligations attached to the same boundary. It acts under CertificationEvidenceContinuityNorm-17, which requires every recommended boundary continuation to retain traceable applicable evidence and requires a hold when a material evidence gap remains. Its relevant conditions are the applicable certification obligations, current evidence links, and open evidence gaps. Neither System boundary includes the product family, either C.30 architecture-relation occurrence, the role-kind descriptions, or the assignment occurrences; neither action is yet called Work.
PlantArchitecturingSystemRoleKindDomain contains two exact local agential system-role kinds with independent membership criteria. ManufacturingArchitectureSystemRole requires the stable work-facing contribution of manufacturing-feasibility constraint judgment and goal-directed, condition-sensitive regulation toward BatchFeasibleModuleBoundaryObjective-17: the holder must select among admissible boundary continuations and revise, pause, or escalate its judgment when batch-line capability or exception evidence changes. CertificationArchitectureSystemRole requires the stable work-facing contribution of certification-evidence constraint judgment and corresponding regulation under CertificationEvidenceContinuityNorm-17: the holder must select among admissible evidence continuations and revise, pause, or escalate when an obligation or evidence gap changes. ManufacturingConstraintDecisionTrace-17 shows the manufacturing team comparing two admissible continuations, revising one constraint after new batch-exception evidence, and pausing the unsupported continuation. CertificationEvidenceDecisionTrace-17 shows the certification team revising the evidence obligation after an applicability change and holding the unsupported continuation pending a missing trace. A.10 evidence-use claims connect those traces and the respective boundary and coordination records to the two criteria. On that basis Plant-A separately classifies ManufacturingArchitectureTeam-A under ManufacturingArchitectureSystemRole and CertificationArchitectureTeam-A under CertificationArchitectureSystemRole. The evidence and classifications are independent of the candidate Work and of either assignment. No Grade, autonomy result, characteristic profile, or stronger assurance claim is consumed here.
The two-participant assignment kind PlantArchitecturingWorkAssignment is declared under U.SystemRoleAssignment. Its HolderSystemSlot admits a U.System; its local AssignedSystemRoleKindSlot uses PlantArchitecturingSystemRoleKindDomain; and its predicate says that, for the declared scope, situation, and interval, the holder is selected to supply the contribution defined by the assigned kind to the Plant-A transition-architecturing action. ManufacturingArchitectureAssignment-17 assigns ManufacturingArchitectureSystemRole to ManufacturingArchitectureTeam-A; CertificationArchitectureAssignment-17 assigns CertificationArchitectureSystemRole to CertificationArchitectureTeam-A. Both occurrences obtain with their declared holder and assigned-kind values, all species-specific predicates satisfied, and maximal uninterrupted predicate-true intervals covering the full stated window. These are the same obtaining assignments later consumed by F.6.
Only after both A.13 cores are established does A.15.1 independently admit ModuleTransitionArchitecturingWork-17 : U.Work. The independently grounded joint performance history records the two actions above as one top-level occurrence; the Work runs from 2026-07-14T09:00:00+03:00 to 2026-07-16T18:00:00+03:00 and enacts ModuleTransitionArchitecturingMethod-v3. A locally declared relation places that Work within ProductFamilyEngineeringSystem-A for the stated engineering-system boundary and Work interval. The independently admitted ProductFamilyEngineeringSystem-A : U.System is the second participant of that relation. Neither assignment nor an F.6 conclusion is an A.15.1 admission premise.
F.6 then records that ModuleTransitionArchitecturingWork-17 was performed under each of the same obtaining assignments established in the A.13 cores. The direct case facts link the exact Work to both assignment occurrences; holder equality holds for ManufacturingArchitectureTeam-A and CertificationArchitectureTeam-A, and both assignment intervals cover the Work. The Plant-A relation ArchitecturingWorkChangesModuleBoundary separately states that this Work brings about FieldModuleBoundaryTransformation-17.
This is the A.15.1 CC-A15.1-17 joint-performer form. Neither a lead assignment nor the architecture pair substitutes for either performer. Taxonomy and scheme epistemes may help interpret an assertion, but they are not assignment participants.
ProductDevelopmentNetworkRecord-2026Q3 may cite BatchEvidence-to-FieldModules-Row-17 once in architectureCorrespondenceRowRefs[]. That citation contributes one reading of the exact two C.30 architecture-relation occurrences. The pair row remains an episteme, not the TransformationFlowStructureNetwork, not one of its members, and not a cross-flow relation. Its optional networkCrossFlowRelationRowRef stays absent unless this same influence occurrence is independently grounded at exact member-flow positions and the composite E.18.NET locator resolves exactly one matching row in that same current record edition.
Network-qualified reading.
A product-development TFS and a production-system-change TFS participate in one selected E.18.NET-conforming network. A current architecture pair row about manufacturing-architecture influence may be cited by the network record alongside a separately grounded obtaining production or project occurrence. If the pair row also carries networkCrossFlowRelationRowRef, that locator names this same exact current record edition and resolves exactly one matching row; it qualifies no citation from another record. The pair row remains one reading of one exact architecture pair. It is neither the network nor proof that the architecture-influence occurrence is the cross-flow occurrence.
Near miss. A diagram places a factory architecture beside a product architecture and labels the arrow “shapes”. No direct relation kind and predicate govern that pair and use. The frame may retain the pair as synthesis-local pressure, but the exact row and network cross-flow mapping remain absent with missing-governor; the diagram does not create an occurrence.