Approximation Target Divergence Mapping

Refine an approximation by mapping where it diverges from the target, then focus improvement effort on the most consequential gaps.

The Diagnostic Story

Symptom: Refinement effort accumulates without the approximation getting meaningfully closer to fitting its purpose. One reviewer flags edge-case failures, another demands polish on already-acceptable parts, a third questions the whole architecture — and there is no shared map of which gaps actually matter. Average metrics look acceptable while the cases that count most keep slipping through.

Pivot: Stop treating improvement as undirected iteration and instead build a target-relative gap map: snapshot the current approximation against an explicit target, decompose divergence by dimension and context, and score each gap by how materially it threatens validity, safety, or usefulness. Effort flows to the highest-priority mismatches, while acceptable simplifications are documented and defended.

Resolution: Refinement loops converge faster because every action traces to a scored gap rather than salience or stakeholder pressure. Approximation limits become visible to reviewers and decision-makers, so acceptable deviations are tolerated rather than re-litigated. Persistent divergence triggers architecture or target review early, rather than surfacing as a late rejection.

Reach for this when you hear…

[ML engineering] “Our benchmark score keeps going up but the model still mishandles the exact cases the product team cares about — we're polishing the wrong gaps.”

[urban planning] “Every revision cycle someone adds a new concern and we lose track of which deviations from the original brief we actually signed off on.”

[clinical trials] “The protocol hit all the primary endpoints but the FDA asked why we never documented what the model was allowed to miss — and we didn't have an answer.”

Mechanisms / Implementations

• checkpointed_convergence_review
• refinement_backlog_prioritization
• regression_guarded_refinement_cycle
• residual_error_heatmap
• side_by_side_target_delta_review
• tolerance_band_gap_scoring

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.

▸ Show 16 more

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.

Qualitative Target-Gap Mapping · domain variant · recognized

Map divergence from a qualitative, interpretive, aesthetic, or experiential target using criteria rather than pure metrics.

Benchmark-Anchored Divergence Mapping · validation variant · candidate

Use benchmark cases or reference examples to decide which approximation-target divergences require refinement.

Regression-Guarded Refinement · risk or failure variant · candidate

Close one target gap while explicitly checking that already acceptable dimensions do not regress.