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:
| Aspect | Value |
|---|---|
| Mapping mode | correspondence |
| Preserved structure | candidate alternative and selected trade-off relation |
| Lost structure | full Pareto-front detail and rejected-candidate evals |
| Directionality | selected source structure to narrative only |
| Admissible use | team 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.