C.32.CONWAY:4.2 - Exact reusable architecture-pair row
ArchitectureInfluenceTransformedArchitectureCorrespondenceRow@Context <: U.Episteme:
entityOfConcernRef: exactArchitectureInfluenceOrCorrespondenceRelationOccurrenceRef
entityOfConcernKindRef: exactArchitectureInfluenceOrCorrespondenceRelationKindRef
relationFunctionClaimRef: subject pattern of that exact relation kind and occurrence
influenceSourceArchitectureRelationRef: one exact obtaining C.30 ArchitectureRelation
influenceSourceHolonRef: the exact architectureBearingHolonRef participant of influenceSourceArchitectureRelationRef
influenceSourceSelectedStructureRef: the exact selectedArchitectureStructureRef participant of influenceSourceArchitectureRelationRef
influenceSourceArchitectureClaimRef?: exact C.30 ArchitectureClaimRef when the current use also needs claim content about that same holon, relation, or structure
transformedArchitectureRelationRef: one exact obtaining C.30 ArchitectureRelation
transformedHolonRef: the exact architectureBearingHolonRef participant of transformedArchitectureRelationRef
transformedSelectedStructureRef: the exact selectedArchitectureStructureRef participant of transformedArchitectureRelationRef
transformedArchitectureClaimRef?: exact C.30 ArchitectureClaimRef when the current use also needs claim content about that same holon, relation, or structure
changedReferentRef: exact independently identified referent of the current change
actualTransformationRef?: U.EntityRef constrained to U.Transformation, only when A.3.4 independently admits the bounded change of changedReferentRef
performerRows[]?:
actingSystemRef: U.EntityRef constrained to U.System; for performance, this is the exact actual performer recovered through performerA13CoreBasisRef
performerA13CoreBasisRef?: required with workOccurrenceRef; cites the exact local kind and criterion, classification, same obtaining assignment, scope, working situation, window, and adequate core evidence
workOccurrenceRef?: U.EntityRef constrained to U.Work, independently admitted by A.15.1 when performance is claimed
actingSystemRoleAssignmentRef?: U.RelationRef constrained to U.SystemRoleAssignment, include when an obtaining assignment is separately represented and require the same A.13 assignment when attribution is represented
performedUnderAssignmentRelationRef?: U.RelationRef governed by F.6, include only when this row expressly represents precise assignment-bound attribution; omit otherwise; missing or failed F.6 leaves workOccurrenceRef intact
actorSideOrWorkToChangeRelationRefs[]: U.RelationRef
additionalInfluenceSourceRows[]?:
influenceSourceRef:
influenceSourceKindRef:
exactInfluenceRelationRef: U.RelationRef
influencePatternLocator:
affectedArchitectureCharacteristicRefs[]: current C.32.ACS criteria-row refs; exact C.25 Q-Bundle slot refs when composite
evolutionWindowRef:
correspondenceUse:
expectedArchitectureGain:
knownArchitectureLoss:
receivingUsePatternLocator:
sourceReturnCondition:
networkCrossFlowRelationRowRef?: E.18.NET NetworkCrossFlowRelationRowRef
The row is a U.Episteme about one already obtaining direct influence or correspondence relation whose exact participants include the two obtaining C.30 architecture-relation occurrences required by this use. Because those occurrences fill participant positions of another relation, each is explicitly individuated under A.6.REL for this receiving use. The row neither creates the influence occurrence nor mints a universal Conway relation. Each C.30 occurrence keeps its exact holon and selected-U.Structure participants; the influence occurrence keeps its identity under its direct relation pattern and A.6.REL. This row only describes them for the current correspondence use. entityOfConcernRef, its kind, its governor, both C.30 occurrences and their participant pairs, and the changed referent are required. If the practitioner has only a useful local compound correspondence claim, or either architecture side is modal rather than obtaining, keep it in the frame for candidate synthesis. Assert the row only after the admitted influence relation kind’s direct predicate is applicable and current facts satisfy it affirmatively. If the predicate is false, assert no row; if facts are unresolved, keep the frame and name that boundary; if the kind or predicate is absent, return missing-governor. None of these branches permits inferring a relation from two architecture claims, structures, diagrams, or names.