Approximation Target Divergence Mapping¶
Refine an approximation by mapping where it diverges from the target, then focus improvement effort on the most consequential gaps.
Gap-fill role¶
This draft directly addresses the zero-any accepted-prime target refinement from queue position 24 of scaled_gap_fill_batch_003_queue.yaml. It operationalizes refinement as a target-relative divergence discipline: specify the target, snapshot the approximation, map consequential mismatch, and use that map to prioritize corrective improvement.
Pre-draft disposition conclusion¶
Disposition: drafted_full_archetype. The candidate has close neighbors in bounded_approximation, iterative_refinement_loop, progressive_refinement_from_core_model, divergence_detection_and_correction, tolerance_band_management, tolerance_stack_management, variance_reduction, quality_control, and the pilot benchmark_anchored_refinement variant. None clearly absorbs the full pattern, and no binding alias or duplicate-merge directive was found.
When This Archetype Applies¶
Partial catalog groundingSome structural conditions are represented by existing abstractions, but no sufficient condition set is fully represented.
Diagnostic problem
An acknowledged approximation has a gap structure that is implicit, unevenly perceived, or poorly prioritized, causing actual refinement to follow local cues rather than the gaps that govern fitness to the target.
What this problem means
A model, prototype, plan, performance, forecast, classification, or artifact is recognized as approximate, but the divergence between the approximation and the target is implicit, unevenly perceived, or poorly prioritized. Teams then refine by habit, salience, stakeholder pressure, available tools, or aesthetic polish rather than by the gap structure that determines whether the approximation is becoming more fit for purpose.
Applicability expression5 distinct conditions
groundedpartly groundedopen
Equivalent to the 4 condition sets it replaces, with 3 duplicate condition cards removed.
1Required in every casenumbered 1–1
These hold no matter which pattern applies.
Ungoverned refinement priorities · open
The condition-specific gap information remains insufficiently visible or prioritized to govern refinement, causing actual refinement to follow local cues instead of the gap structure that determines target fitness.
This condition preserves a load-bearing part of the diagnostic problem that was not captured by a source-condition atom. It remains explicit because omitting it would weaken the sufficient condition set.
4At least one of theselettered A–D
Any single one of these completes the pattern.
Multidimensional target gaps · open
The current approximation is known to depart from its target in several distinct ways.
The source archetype describes the situation as follows: A current approximation is serviceable but known to miss the target in several ways. The normalized requirement above isolates the load-bearing portion used in this condition set.
Unequal deviation severity · grounded
Some approximation deviations are benign simplifications while others threaten validity, safety, value, or acceptance.
The source archetype describes the situation as follows: Some deviations are harmless simplifications while others threaten validity, safety, value, or acceptance. The normalized requirement above isolates the load-bearing portion used in this condition set.
primeEngineering Tolerances— Acceptable variation.
Conflicting fit criteria · open
Different stakeholders use conflicting criteria for judging whether the approximation is closer to its target.
The source archetype describes the situation as follows: Different stakeholders disagree about what “closer to target” means. The normalized requirement above isolates the load-bearing portion used in this condition set.
Local-global fit divergence · grounded
An approximation keeps improving locally without a corresponding improvement in whole-target fit.
The source archetype describes the situation as follows: A prototype, model, or performance keeps improving locally without improving overall fit. The normalized requirement above isolates the load-bearing portion used in this condition set.
primeProxy-Target Divergence— An apparatus calibrated against a proxy keeps operating on it after the proxy-target relationship has silently decoupled.
Other requirements and context (2)
Why these sit outside the expression
Application gate — it governs whether applying the archetype is appropriate or material, rather than defining the structural problem itself.
Solution feasibility — it describes whether the intervention can work, not whether the diagnostic problem exists.
Application gateRefinement effort is scarce and not all gaps can be closed at once.
Solution feasibilityThe target itself is measurable only through proxies, benchmarks, or qualitative criteria.
Coverage
2 of 5 conditions grounded · 3 open.
Review emphasis¶
Review this draft with the broader refinement family. Its most important boundary risks are component-only collapse into a generic gap map, overlap with iterative_refinement_loop, overfitting to benchmark targets, and false precision when target divergence is scored more exactly than the measurement supports.
Common Mechanisms¶
6 documented mechanisms across 4 implementation forms.
The grouping reflects forms represented among the mechanisms currently documented for this archetype; an absent form is not necessarily an impossible implementation.
Assessment, Review & Assurance · 3 mechanisms
- Checkpointed Convergence Review — Re-snapshots the approximation at fixed checkpoints to confirm it is still converging on the target — and to trigger a stop-or-escalate when it is not.
- Side-by-Side Target Delta Review — Places the intended target and the current approximation next to each other, dimension by dimension, so every consequential delta becomes visible and nameable.
- Tolerance-Band Gap Scoring — Scores each divergence against its acceptable-error band, separating harmless simplifications from out-of-tolerance gaps that actually need repair.
Decision, Gate & Allocation · 1 mechanism
- Refinement Backlog Prioritization — Turns scored gaps into an ordered refinement backlog by weighting each by consequence, tractability, confidence, and whose stake it serves.
Interface, Display & Cue · 1 mechanism
- Residual Error Heatmap — Renders the divergence map as a colored field so the eye lands first on where residual error is largest — with a confidence overlay showing how far each cell can be trusted.
Protocol, Workflow & Routine · 1 mechanism
- Regression-Guarded Refinement Cycle — Executes prioritized refinements one at a time behind a regression guard, so closing one gap can never silently reopen a gap that was already within tolerance.
Compression statement¶
Approximation-Target Divergence Mapping is the pattern of treating the difference between a current approximation and an intended target as a structured object. Instead of refining everywhere or reacting to the most visible defects, it specifies the target, snapshots the approximation, decomposes their divergence by dimension, distinguishes acceptable approximation error from material mismatch, and directs refinement effort toward the gaps whose correction most improves fit.
Canonical formula: refinement_priority_i := consequence(target_i - approximation_i) × tractability_i × confidence_i; refine gaps above the action threshold while preserving acceptable approximation bounds
Related Abstractions¶
Abstractions this archetype builds on — directly (a source ingredient) or as a related pattern. Links follow the typed catalog namespace.
Built directly on (1)
- Refinement: Iteratively improving a candidate solution toward adequacy through repeated cycles of evaluation and adjustment that narrow the gap to a target, rather than deriving the answer in one shot.
Also references 26 related abstractions
- Approximation: Good-enough representation.
- Boundedness: Values remain within limits.
- Calibration: Aligning a system's output to a trusted reference by measuring deviation, adjusting to reduce it, and monitoring for drift.
- Convergence: Movement toward stable state.
- Cost–Benefit Analysis: Evaluate decisions.
- Data Integrity: Accuracy and consistency preserved.
- Diminishing Incremental Gains: Reduced benefit per unit.
- Divergence-Convergence in the Design Process: Expand then refine ideas.
- Engineering Tolerances: Acceptable variation.
- Error Proofing (Poka-Yoke): Error prevention.
Variants¶
Narrower or domain-specific specializations that share this archetype's core structure. Recognized variants are established; candidate variants are provisional.
Metric Residual Divergence Mapping · subtype · recognized
Map quantitative residuals between a model or process output and target values to guide selective refinement.
- Distinct from parent: Narrower because the target gap is primarily quantitative.
- Use when: Target dimensions can be measured or benchmarked; Residuals vary by region, case type, subgroup, or operating regime.
- Typical domains: simulation refinement, machine-learning error analysis, quality control
- Common mechanisms: residual error heatmap, tolerance band gap scoring, checkpointed convergence review
Qualitative Target-Gap Mapping · domain variant · recognized
Map divergence from a qualitative, interpretive, aesthetic, or experiential target using criteria rather than pure metrics.
- Distinct from parent: Narrower because comparison depends on qualitative criteria.
- Use when: The target includes style, meaning, user experience, judgment, or interpretive fit; Numeric scores are insufficient or misleading.
- Typical domains: musical performance, design review, policy implementation
- Common mechanisms: side by side target delta review, refinement backlog prioritization
Benchmark-Anchored Divergence Mapping · validation variant · candidate
Use benchmark cases or reference examples to decide which approximation-target divergences require refinement.
- Distinct from parent: Narrower because the target is represented through test cases or exemplars.
- Use when: Direct target measurement is difficult but benchmark cases exist; The approximation must perform across known regimes before being trusted.
- Typical domains: scientific model validation, software acceptance testing, engineering calibration
- Common mechanisms: benchmark case delta table, checkpointed convergence review
Regression-Guarded Refinement · risk or failure variant · candidate
Close one target gap while explicitly checking that already acceptable dimensions do not regress.
- Distinct from parent: Narrower because regression control is the dominant constraint.
- Use when: Refinement actions interact across dimensions; Local improvement can degrade prior target fit.
- Typical domains: software releases, model tuning, service redesign
- Common mechanisms: regression guarded refinement cycle, checkpointed convergence review
Near names: Target Divergence Mapping, Approximation Gap Analysis, Residual Gap Mapping, Gap-Directed Refinement.
Editorial Notes¶
Problem Classification¶
Classification: Representation, Classification & Model Misfit → Abstraction, Reduction & Approximation Fidelity
Problem kernel: approximation error is unstructured and misprioritized
Rationale: A known approximation lacks an explicit map of where and how it diverges from the target, so refinement follows salience rather than task-relevant fidelity.
Independent corroboration: The earliest necessary condition in the frozen evidence is: A model, prototype, plan, performance, forecast, classification, or artifact is recognized as approximate, but the divergence between the approximation and the target is implicit, unevenly perceived, or poorly prioritized. That is a abstraction reduction and approximation fidelity problem because A compressed, approximate, sparse, or proxy representation drops or weights structure without a traceable account of task-relevant loss.
Review outcome: Independent reviewer agreement; high confidence.