C.34:4 - Solution
State the decision that will use the correspondence. Identify the entities being matched and the relation on which the decision depends. A conclusion about the source carries over in the direction for which the mapping preserves the facts needed to reach it. To infer absence in the target from absence in the source, also show why any relevant target occurrence would have a source counterpart. Extra target connections can change the answer.
For a grouping, ask how membership is determined. If both models define membership by the same rule and the correspondence preserves everything that rule uses, derive the target grouping. If membership is assigned independently, inspect the assignments or an applicable allocation rule and the facts it uses. For an assignment whose preservation is in doubt, keep the matched entities and links fixed. Could two different assignments fit them? When this changes who may act, the correspondence alone leaves that decision open. Correspondence between two disciplinary models can matter even when both are at L2. A claim of model refinement has its own test in B.5.MR:4.3.
When reviewing a comparison someone produced, distinguish the correspondence supplied in the assignment from the choices the person or AI agent made. Applying a supplied match can establish that the comparison gave the right result. To credit someone with constructing a disciplinary model of correspondence, recover how they selected the entities, interpreted the links and justified the matching rule for further comparisons. An earlier decision record can show those choices. A new task can leave them open. Use C.39.QR:4.3 when the attribution changes what you entrust to the agent.
Work in this order:
- Name the selected source structures and selected target structures. Do not start from labels, diagrams, or tool objects alone.
- Name the intended architecture use: view correspondence, candidate comparison, structure recovery, generated-output admission, realization check, eval support, decision repair, or another receiving claim.
- Select a warranted mapping mode sufficient for the use. A weaker sufficient correspondence can finish the work; an already established stronger result can be reused within its scope. Use
exactEquivalenceonly when preservation of the entire selected structure is established within the declared scope. - State preserved relations or constraints in domain terms. Use FPF distinctions where the claim depends on them. Include relation-type semantics when edge or link meaning changes the use.
- State directionality and scope or scale window, with any material lost or hidden structure. Distinguish an observed loss from preservation left unestablished by incomplete observation. Neither supports a claim requiring the missing preservation, but each selects a different next inquiry or repair.
- Retain the mathematical definition, mapping and proof conditions needed by a formal preservation claim. Use
C.29when choosing, transferring, or relying on that mathematical representation remains unresolved. - Cite
C.30.ASV,C.30.AD, or their correspondence records when the relation is view or architecture-description correspondence. - Cite
A.6.3.NARwhen the target episteme or representation is a narrative rendering whose ordering rationale, preserved selected source structure, source-return condition, and any unresolved stronger assertion with the pattern that defines it must stay inspectable. - Use
F.9for cross-context or cross-tradition substitution or claim transport that requires a Bridge. UseF.15when the receiving use needs its static or regression conformance tests. - Stop when the supported use and its grounds are clear, with any material limitation and the condition for resolving it. Apply an additional mapping, Bridge or conformance rule when that use requires it.
CGUS-aware neighbor use: when a route-shaped publication card, narrative sequence, generated route card, framework publication, or demonstrative slice is claimed to preserve a constraint-governed unfolding structure, use C.34 only to check the sameness relation. The result names selected source and target structures, mapping mode, preserved constraints, preserved ordering or branching relations, lost alternatives, directionality, and admissible use.
A.22.CGUS, E.18.3, C.32.P2S, or another structure pattern continues to define or constrain the selected unfolding U.Structure; cite a ClaimGraph only if that structure claim must travel independently.
A demonstrative slice is a U.Episteme that presents one traversal of a qualified CGUS. Its correspondence to that structure may be checked here; DemonstrativeUnfoldingSlice@Context is a lineage cue, not a slice identity.
When that presentation is a narrative, A.6.3.NAR defines its source selection, ordering and connective account, preservation/loss, use, and return, not the selected structure.
The C.34 result says only whether the target is same enough for the declared architecture use.