Jump to text
On this page
Copy and source
Published source confirmed at last check

Source changed 2026-11-18 21:11:39 UTC · snapshot created 2026-11-18 21:12:35 UTC · last check 2026-11-18 22:00:10 UTC

C.34 - Assess Structural Correspondence for Architecture Use (Equivalence and Morphisms)

Type: Architectural pattern Status: Stable Normativity: Normative unless marked informative

C.34:1 - Problem frame

Use this pattern when two descriptions, views, models, generated outputs, or realized observations that carry or describe selected structure are being treated as same enough for architecture work and the practitioner must say what selected structure is preserved, what is lost, and which use the correspondence licenses.

Primary working reader: an architect, reviewer, or model-assisted practitioner comparing views, descriptions, source models, generated graphs, candidate architectures, realized structures, abstraction levels, coarsened models, or transformed models.

Typical entry phrases:

"These two diagrams look equivalent; what relation is preserved?"
"The model query and the architecture view should correspond; what was lost in projection?"
"The generated graph matches the module graph; is the semantic relation the same?"
"This candidate preserves dataflow but changes control authority."
"The neural architecture replacement keeps shape but changes routing and memory placement."
"The narrative order preserves the architecture trade-off; what selected source structure is still same enough for this use?"

The first useful result explains which correspondence supports the intended architecture use. An ordinary account can suffice; reuse an adequate existing account. StructuralPreservationAdequacyNote@Context is an optional working form:

StructuralPreservationAdequacyNote@Context:
  selectedSourceStructureRefs:
  selectedTargetStructureRefs:
  architectureClaimRef?:
  mappingMode:
    exactEquivalence | isomorphism | homomorphism | correspondence |
    projection | abstraction | coarsening | simulationRelation |
    nearSameness | declaredOther
  preservedRelationsOrConstraints:
  preservedInvariantsOrCompositions?:
  lostStructure?:
  relationTypeSemantics?:
  relationObservationClass?:
  directionality:
  scopeOrScaleWindow?:
  lensUseOutputRef?:
  correspondenceRecordRef?:
  constraintGovernedUnfoldingStructureRefs?:
  admissibleUse:
  nonAdmissibleUse?:
  preservationLossReturnCondition?:
  nextClaimOrRuleRef?:
  receivingClaimKind?:

After using C.34, another practitioner can recover the claimed correspondence, preserved structure, direction and scope, any loss or uncertainty that limits reliance, and the use it supports.

What C.34 buys in practice: the practitioner can say “same enough for this use” without implying stronger equivalence. The pattern makes sameness conditional on preserved relation, declared loss, and receiving use.

Name the conclusion you want to carry from one model to the other. Identify what makes it true in the first. Look for that relation, or a rule from which it follows, in the second.

For a current claim limited to mathematical-lens use, generic bridge translation, measurement, structural view adequacy, architecture-description correspondence, candidate synthesis, decision, evidence, assurance, gate, release, or work authorization, use the pattern that defines or tests it. Use C.34 only for the architecture-specific preservation claim.

C.34:2 - Problem

Architecture work often needs “same enough” claims. A view should correspond to a description. A generated graph should preserve selected dependencies. A candidate should preserve required interfaces while changing placement. A realized structure should match an expected selected structure enough for an evaluation or decision repair. A neural-network substitution should preserve dataflow or routing while changing memory and compute trade-offs.

Visual similarity, label sameness, graph isomorphism, or formal vocabulary does not by itself establish architecture adequacy. An edge-isomorphic graph can lose relation semantics. A projection can preserve module names while dropping control authority. A category-theoretic morphism can be useful as a C.29 lens without proving architecture equivalence. A DSM cluster can preserve co-change pressure while losing functional bearer semantics.

C.34 makes the preservation claim explicit before the result is used.

C.34:3 - Forces

ForceTension
Equivalence vs useExact equivalence is rare and often unnecessary; the declared use decides how much preservation is enough.
Formal rigor vs practitioner actionFormal mapping modes help only when preserved and lost structure are named in architecture terms.
Shape vs semanticsTwo graphs, views, or diagrams can have the same shape while their relation types differ.
Compression vs lossProjection, abstraction, coarsening, and simulation relations make work possible by dropping structure. In a chain from selected source structures to architecture, architecture description or view, and narrative or framework carrier, preservation must be checked relation by relation rather than claimed as one global sameness.
Cross-context reachA mapping across teams, source traditions, tool models, or holon levels needs the Bridge predicate and conformance test when substitution or transfer is claimed.

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:

  1. Name the selected source structures and selected target structures. Do not start from labels, diagrams, or tool objects alone.
  2. Name the intended architecture use: view correspondence, candidate comparison, structure recovery, generated-output admission, realization check, eval support, decision repair, or another receiving claim.
  3. 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 exactEquivalence only when preservation of the entire selected structure is established within the declared scope.
  4. 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.
  5. 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.
  6. Retain the mathematical definition, mapping and proof conditions needed by a formal preservation claim. Use C.29 when choosing, transferring, or relying on that mathematical representation remains unresolved.
  7. Cite C.30.ASV, C.30.AD, or their correspondence records when the relation is view or architecture-description correspondence.
  8. Cite A.6.3.NAR when 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.
  9. Use F.9 for cross-context or cross-tradition substitution or claim transport that requires a Bridge. Use F.15 when the receiving use needs its static or regression conformance tests.
  10. 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.

C.34:5 - Archetypal Grounding

C.34 is the pattern for a declared architecture preservation claim. It is used when a practitioner says that one description, view, model, generated output, or realized observation is same enough as another for a specific architecture use. The account identifies a sufficient warranted mapping, preserved structure, direction, scope and supported use, together with any material loss or uncertainty and the rule needed by further reliance.

What a pair of diagrams preserves. Two diagrams show all three stations A, B and C, with links A–B and B–C. In one, a link records data dependency. In the other, it records control authority. For the question “which stations are joined by some path when link direction and meaning are ignored?”, both give the same answer. Matching all the stations and links preserves connected components under that definition.

A planner now needs the crew responsible for each station. One crew could have A and B and another C, or one crew could have all three, with exactly the links shown. Connectivity leaves both crew assignments possible. The current allocation record can identify the responsible crew, as can a rule assigning stations by connected component together with the current assignment of each component to a crew. To dispatch a crew, use the duty rule for this shift. If it sends the responsible crew, the assignment settles whom to send. If it provides cover for an unavailable crew, also check who is on duty. If the decision concerns who may authorize a control action, inspect the control relation with its direction and meaning intact. Use C.30.ASV or C.30.LCA when that relation needs recovery.

Source model and generated graph case. A code-agent dependency graph matches module names in the model used as the source, but marks several edges inferred and several regions unexplored. C.34 records the observation class and directionality, the supported dependency correspondence, and the dynamic wiring whose preservation is still unestablished.

The graph may help inspect candidate dependencies; safe-change or release reliance needs the missing structure and the assurance grounds for that use.

Candidate and realized structure case. A candidate architecture promises that a service split preserves interface substitutability, but the realized structure adds shared storage and a hidden orchestration dependency. C.34 records preserved interface signatures, lost runtime independence, changed coupling, and a preservation-loss condition that reopens the dependent decision premise before its reuse.

Use A.6.M for substitutability, A.6.F for a function or bearer question, C.31 for changed coupling, C.30 for the changed structure and C.32.PAD for the affected decision as each question requires.

Neural substitution case. A candidate replaces an attention block with an SSM block. C.34 asks which selected structures are preserved: sequence dataflow, routing interface, memory access, latency envelope, training resource boundary, or inference resource boundary. Shape sameness or benchmark improvement does not by itself preserve the architecture relation needed by the next claim.

Selected source structure and narrative structure case. An architecture narrative orders a candidate set as “pressure, alternative, trade-off, decision, residual.” C.34 records:

AspectValue
Mapping modecorrespondence
Preserved structurecandidate alternative and selected trade-off relation
Lost structurefull Pareto-front detail and rejected-candidate evals
Directionalityselected source structure to narrative only
Admissible useteam orientation and decision memory

The narrative order is not exact equivalence and does not license implementation, evidence, or assurance use without the rule that defines or tests that downstream claim.

C.34:6 - Bias-Annotation

BiasHow C.34 counters it
Shape-equivalence biasRequire relation-type semantics, preserved structure, and lost structure. Same nodes or edges are not enough.
Formal vocabulary mistaken for adequacyKeep graph isomorphism, morphism, functor, entropy, or simulation wording as lens or mapping support until the architecture use, preserved structure, and loss are declared.
Symmetric-equivalence overclaimRequire directionality and scope. A projection, abstraction, simulation relation, or coarsening often licenses one direction only.
Semantic-loss hidingMake lost control authority, allocation, bearer semantics, placement, timing, confidence, or source-tradition meaning explicit before the mapping is reused.
Bridge-bypass biasHandle cross-context substitution, source-tradition transfer, and later conformance strengthening under F.9 or F.15 instead of letting C.34 authorize the transfer alone.

C.34:7 - Conformance checklist

CheckPass condition
CC-C34-1Source and target structures are named before the mapping claim.
CC-C34-2The selected mapping is warranted and sufficient for the declared use; no stronger result is required merely to complete the assessment.
CC-C34-3The account identifies the facts that support the intended inference in the target and the direction in which they carry over. Where independently assigned relations could change the decision, the account establishes them or identifies the decision that remains open.
CC-C34-4Relation-type semantics, observation class, directionality, and scope are present when they affect use.
CC-C34-5Each current mathematical-lens, view, description, Bridge, conformance, candidate-synthesis, measurement, eval, decision, evidence, assurance, gate, release, or work-authorization claim uses the pattern that defines or tests it.
CC-C34-6The supported use and its grounds are clear, with any material limitation, recovery condition and rule required by the next reliance.

C.34:8 - Common Anti-Patterns and How to Avoid Them

Anti-patternWhy it failsRepair move
Edge-isomorphism overreadThe same pattern of links can coexist with different responsibilities or directions of control.Derive properties defined by the preserved links. For a claim about an assigned relation, match the assignments or establish the rule and facts that determine them.
Semantic-loss hidingA projection or coarsening can look clean because it drops the structure that the next decision needs.Name lost structure and preservation-loss return condition before comparison, decision repair, or candidate admission.
Exact-equivalence overclaimExact equivalence is stronger than most architecture uses need and is often false.Use a warranted correspondence, projection, abstraction, coarsening, simulation relation or near-sameness when sufficient. Exact equivalence may be retained when independently justified.
Generated graph proof overclaimA generated graph can match labels or topology while hiding dynamic wiring, confidence, or unexplored regions.Use C.34 only for the preservation claim; handle generated-carrier admission under C.35, and apply the rules that define evidence, assurance, gate, or release claims when those claims are current.
Narrative-order equivalence overclaimA narrative can preserve a useful path through selected source structure while dropping alternatives, relation semantics, measurements, or directionality.Record a warranted correspondence sufficient for the use, preserved structure, lost structure, directionality, and non-admissible use; use A.6.3.NAR for the narrative rendering relation.
Formal result mistaken for architecture adequacyA morphism, functor, entropy value, or graph match establishes a result under its mathematical conditions; its architecture use also depends on what the mapping preserves.Establish the preserved structure, any material loss or uncertainty, mapping mode and intended architecture use. Use C.29 for a remaining mathematical-representation choice, transfer, or reliance question.
Bridge-governance bypassA cross-context or cross-tradition mapping can preserve local structure while losing local sense.Use F.9 for the Bridge. Apply F.15 when the current or changed use needs its conformance tests; reuse an adequate existing result.

C.34:9 - Consequences

Positive consequences:

  • Architects can use partial sameness without asserting identity. This keeps comparison, projection, generated-output admission, realization checks, and decision repair usable.
  • Formal methods can support the mapping without becoming architecture ontology. Examples include graph matching, category-theoretic morphisms, entropy, and simulation relations.
  • Cross-context and source-tradition risks are visible early because directionality, scope, bridge loss, and the conformance rules for the receiving use are named.
  • Later decisions can be repaired locally: the preservation note says which relation failed, which structure was lost, and which claim or check must be reopened.

Costs and trade-offs:

  • Assessing correspondence takes attention. Reuse an adequate account; investigate further when a plausible preservation difference could change the intended use.
  • The pattern does not prove formal equivalence by itself. When proof, measurement, evidence, assurance, gate, release, or work authorization is current, apply the corresponding rule or test.
  • Some comparisons will lower from equivalence to correspondence or near-sameness. That lowering is a success when it prevents a false downstream claim.

C.34:10 - Rationale

Architecture preservation is use-relative. The same two structures can be equivalent for one use, merely corresponding for another, and unusable for a third. For this architecture-specific claim, start from source and target selected structures, then establish a warranted correspondence sufficient for the next architecture use.

This keeps C.34 separate from its neighbors. C.29 defines mathematical-lens-use accounts. C.30.AD and C.30.ASV govern architecture-description and structural-view adequacy, with records for uses that need them. F.9 defines cross-context Bridges. F.15 supplies static and regression conformance tests over a finite slice of governed objects and versions for one receiving use. C.32 describes candidate synthesis. C.34 contributes the preservation claim those uses may need, but it does not replace them.

The source families explain the safeguards. Structural-equivalence research shows that symmetry can compact search only under explicit conditions. Applied category theory explains the capabilities of preservation maps; they remain formal lenses until tied to the architecture use. MBSE view practice makes projection and omitted structure ordinary. Sapunov and ToCS, plus GonzoML, show why observed relation maps and neural substitution labels need typed relation, confidence, and source-label recovery before architecture use.

C.34:11 - SoTA-Echoing

Source or practice lineUse of the contributionContribution to the assessmentBoundary of use
Yang et al., Structural Equivalence in Subgraph Matching, arXiv:2301.03161Adapt structural-equivalence and symmetry discipline.Supports a warranted mapping mode and the distinction between shape and the relations needed for use.Subgraph structural equivalence does not define holon architecture equivalence outside declared structures and use. Reopen when the source graph, target graph, or use changes.
Fong and Spivak, Seven Sketches in Compositionality, arXiv:1803.05316Adapt applied category-theory preservation language; use C.29 for an unresolved mathematical-representation choice, transfer, or reliance question.Keeps morphism, functor, sketch, and composition vocabulary tied to preserved structure, lost structure, mapping mode, and architecture use.Older source is lineage and still useful as applied compositional practice, but it does not become the default FPF architecture ontology.
Multi-view architecture, MBSE and W3C PROV-DM, responsibilityDistinguish views of structure and the meanings of particular relations, including delegation.Helps a reviewer identify the relation whose preservation would justify the target inference.A correspondence over untyped links leaves responsibility open unless a rule or an assignment determines it. Reopen when the relevant mapping, relation or declared use changes.
Sapunov, ToCS, and code-agent architecture-map practiceAdapt partial-observation preservation discipline.Makes relation observation class, inferred edges, unexplored regions, confidence and active-passive gap conditions on the warranted preservation claim. Incomplete observation can leave preservation unknown without demonstrating structural loss.A code-agent map, JSON probe, dependency F1, invariant F1, or active-passive gap does not prove architecture equivalence, safe change, assurance, gate passage, or release readiness.
GonzoML neural-network architecture intakeAdapt neural architecture operation language.Distinguishes dataflow, routing, memory and cache placement, resource boundaries, block substitution and affected characteristics in neural structure substitution.Use clear source-local meanings directly. Recover an unresolved selected structure or preservation relation when it changes the architecture claim; benchmark gains alone do not establish that preservation.

C.34:12 - Relations

  • Builds on: A.22, C.30, C.30.ASV, C.30.AD, C.29, and F.9.
  • Uses: C.16, C.25, and C.32.ACE when a preservation, similarity, distance, entropy, loss, or compression claim is recorded as a reading or eval result.
  • Coordinates with: C.32, C.32.PAD, C.32.ADR, C.30.TFS-REL, C.30.STRAT, A.6.M, A.6.3.NAR, C.31, C.31.ASAP, E.18, and F.15.
  • Boundary: C.34 tests declared preservation adequacy for an architecture use. It does not make a formalism ontology, select a candidate, decide a project, establish evidence or assurance, or authorize substitution across contexts; that substitution requires the Bridge predicate and conformance rule.

C.34:End

Referenced in the corpus

68 literal mentions in other sections. Read their context to establish the relation.