Acceptable Substitution Mapping

Map which combinations of resources, attributes, or alternatives can substitute for one another while preserving acceptable outcome value.

Solution archetype #

5

Problem family

Representation, Classification & Model Misfit

Problem subfamily

Equivalence, Substitution & Order Normalization

The Diagnostic Story

Symptom: The system has multiple pathways or bundles that might satisfy the same goal, but nobody can say with confidence which ones are truly interchangeable. Substitutions get approved by whoever has local authority that day, and cheaper or more available options quietly replace something important. When the same dispute surfaces for the third time in a month, it becomes clear there is no reusable rule — only accumulated judgment calls that nobody trusts.

Pivot: Define what outcome must actually be preserved, then map the regions where alternatives are genuinely equivalent for that outcome and mark the dimensions that cannot be traded away. The substitution question stops being a one-time power negotiation and becomes a governed lookup against explicit evidence.

Resolution: Recurring substitution decisions become faster and more legitimate because the map gives a reusable answer instead of starting fresh each time. False equivalences are exposed because the non-tradable constraints are named. Stakeholders can see why one bundle is treated as acceptable rather than simply being told it is.

Reach for this when you hear…

[pharmaceutical supply] “We keep approving alternate suppliers without documenting which quality attributes we're actually protecting, and then we wonder why a batch fails a test the original always passed.”

[accessible design] “Someone said the PDF was equivalent to the accessible version, but users who rely on screen readers are still stuck — equivalent for whom?”

[construction procurement] “We have a list of approved substitutes but it doesn't say why they were approved, so every change order becomes a negotiation from scratch.”

When This Archetype Applies

No catalog groundingNone of the structural conditions is currently represented by an accepted prime or domain-specific abstraction.

Diagnostic problem

Diagnose contested or harmful substitution while separating the decision need from evidence of false equivalence.

What this problem means

The structural problem is unclear substitutability. A system wants flexibility, but the boundaries of acceptable replacement are undefined. One actor may see two alternatives as equivalent because both meet a visible criterion; another actor may see them as very different because one preserves trust, accessibility, compatibility, or safety and the other does not.

This problem often appears as repeated substitution disputes, informal exceptions, confusing procurement approvals, service downgrades disguised as equivalence, one-dimensional scoring, or stakeholder dissatisfaction after a supposedly equivalent change.

The root tension is that flexibility is valuable only if the preserved outcome remains intact. A substitution map prevents the system from confusing "different but acceptable" with "different in a way that breaks the purpose."

Show the applicability expression

Applicability expression2 distinct conditions

any oneDisputed bundle equivalenceorHarmful prior substitutions

Algebraic(A∨B)

groundedpartly groundedopen

2 conditions, all required.

2At least one of theselettered A–B

Any single one of these completes the pattern.

A

Disputed bundle equivalence · open

Stakeholders disagree whether one bundle is equivalent to another. more

or — any one satisfies this slot

B

Harmful prior substitutions · open

Prior substitutions caused quality, access, satisfaction, safety, compatibility, or fairness harm. more

Other requirements and context (3)

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.

• Application gateSeveral options differ across multiple attributes, but decision-makers need to choose or authorize substitutes.

• Application gateA preferred resource, supplier, pathway, role, or design is unavailable, too costly, too slow, or not suitable for all users. more

• Application gateA shortage, budget constraint, customization need, or redesign pressure forces substitution rather than simple selection of the ideal option. more

Coverage

0 of 2 conditions grounded · 2 open.

None of the 2 open conditions sit in the shared core — each falls inside one alternative branch, so grounding any one of them closes only that branch.

Read the methodology · Download the trigger-logic data

Mechanisms / Implementations

• Substitution Matrix: A table that scores candidate stand-ins against the attributes a role requires and records which swaps are acceptable under which conditions — and which resources must never be substituted at all.
• Equivalency Table: A lookup that, for each specified item, lists the alternates certified to satisfy the same requirement, with the validation basis recorded so a swap is settled by reference.
• Approved Alternative Catalog: Maintains a reusable list of substitutes that have already passed validation, so an urgent decision reaches for a pre-vetted stand-in instead of re-deciding.
• Indifference Map: Draws the contours of bundles a specific decision-maker treats as equally good, mapping the subjective equivalence region under current, explicitly provisional assumptions.
• Preference Elicitation Workshop: Convenes the actual stakeholders to surface, in their own words, which attributes they will let compensate for others and which value must never be traded away.
• Conjoint or Tradeoff Survey: Estimates how stakeholders value different attribute combinations by asking them to choose between bundles, then infers the exchange rates hidden in their picks.
• Procurement Equivalence Review: Adjudicates a specific proposed substitute against the requirement — demanding evidence, applying an approve/reject/escalate boundary, and offering an appeal — before it may be used.
• Design Tradeoff Curve: Plots the line of designs that all deliver the same required function, showing how much of one physical attribute must be given up to gain another while staying acceptable.
• Service Tier Mapping: Defines a graded set of service bundles, each preserving the core outcome for a different segment's needs and budget, so a customer can be matched to an acceptable tier.
• Exception Review Workflow: Routes borderline and out-of-band cases to an accountable reviewer for a governed accept/repair/reject decision, and flags when repeat exceptions mean the band itself is wrong.

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 (4)

• Equivalence Relation: Groups elements into equivalence classes.
• Indifference Curves: Equal satisfaction sets.
• Paradigmatic vs. Syntagmatic Relations: Any structured system can be decomposed along two orthogonal axes, the vertical set of substitutable alternatives that could fill a slot and the horizontal chain in which selected items are combined.
• Trade-offs: Balancing competing priorities.

Also references 6 related abstractions

• Boundary: Defines system limits.
• Boundedness: Values remain within limits.
• Constraint: Limits possibilities to guide outcomes.
• Opportunity Cost: Value of best alternative.
• Resource Management: Allocation of finite assets.
• Threshold: Safe vs harmful levels.

Variants

Narrower or domain-specific specializations that share this archetype's core structure. Recognized variants are established; candidate variants are provisional.

Procurement Equivalency Mapping · domain variant · recognized

Defines which products, vendors, materials, or specifications may substitute for one another while preserving required performance, compatibility, and risk constraints.

Service Bundle Substitution · implementation variant · recognized

Maps alternative bundles of service features, speed, coverage, channel, support, and price that preserve acceptable user value.

Compensation Bundle Equivalence · domain variant · candidate

Maps combinations of pay, benefits, flexibility, autonomy, status, stability, and development that may be acceptable to different participants.

Capability Mix Substitution · implementation variant · recognized

Maps how different mixes of roles, skills, tools, staffing, or automation can preserve a required capability.

Care Pathway Substitution · risk or failure variant · candidate

Maps alternative care, support, or intervention pathways that can preserve acceptable outcomes without violating safety or dignity constraints.

Multidimensional Dominance-Gated Resource Substitution · subtype · recognized

Substitute an ambient resource for active processing only when it improves every protected state dimension; otherwise combine it with correction or keep the boundary closed.

Editorial Notes

Problem Classification

Classification: Representation, Classification & Model Misfit → Equivalence, Substitution & Order Normalization

Problem kernel: substitutability is confused with false equivalence

Rationale: The system lacks a purpose-relative account of which alternative bundles preserve outcome value and which differences make substitution invalid

Independent corroboration: The earliest necessary condition in the frozen evidence is: A system has multiple possible bundles, resources, service forms, designs, or pathways that might satisfy a goal, but the boundary between acceptable substitution and harmful false equivalence is unclear. That is a equivalence substitution and order normalization problem because Cases that are equivalent or substitutable for a purpose remain fragmented, while consequential differences or canonical order are inconsistently represented.

Review outcome: Independent reviewer agreement; high confidence.