0. Economic Scope Note

This entry is conceptual and systems-oriented.

It does not treat allocation, prioritization, triage, routing, delegation, proxy delivery, phased support, indirect investment, or mediated resource flow as inherently failed. Complex systems often cannot deliver directly to every need at once. Some delivery must route through infrastructure, institutions, interfaces, representatives, or intermediate nodes.

The failure begins when the delivery target does not match the real need.

The issue is not routing.

The issue is delivery to the wrong place being counted as delivery to the right place.

Mis-Targeting occurs when flow exists but does not reach the actual coherence requirement.

1. Definition

Mis-targeting occurs when resource, support, signal, value, care, attention, authority, repair, enforcement, or capacity is delivered, but to the wrong node, layer, phase, need, boundary, scale, interface, or form, leaving the actual coherence requirement unmet while the system records delivery as successful.

The mis-targeted delivery may go to:

• a visible proxy instead of the affected node
• a central institution instead of local need
• a symptom instead of the cause
• a public interface instead of the hidden burden
• a higher layer instead of runtime execution
• a later phase instead of present need
• an individual node instead of a structural constraint
• a policy layer instead of delivery capacity
• a dashboard metric instead of field reality
• a trusted intermediary instead of the actual source of harm
• a convenient category instead of the real case
• a symbolic repair site instead of the load-bearing wound

The core failure is:

delivery occurs
target fit↓
affected need remains
system records provision
H↑

Mis-Targeting is not absence of delivery.

It is delivery whose path fails to match the actual state that needs support or repair.

2. Core Pattern

The core pattern is:

1. A need, harm, burden, gap, risk, or restoration requirement exists.
2. The system identifies a target for delivery.
3. The identified target is easier to see, easier to fund, easier to govern, more politically legible, more administratively convenient, or more aligned with existing categories than the actual need.
4. Delivery occurs.
5. The delivery is counted as action, care, support, justice, investment, repair, or success.
6. The actual affected node receives little or no load reduction.
7. The system interprets continuing burden as new demand, poor uptake, resistance, inefficiency, or lack of gratitude.
8. More delivery may be sent to the wrong target.
9. Hidden debt accumulates in the unserved state.
10. Local coherence declines despite recorded delivery.

This failure mode often appears as:

we delivered resources, so the need was addressed

or:

the program exists, so support is available

or:

the funding reached the sector, so the affected nodes were helped

The restorative question is:

did the delivered flow reduce the actual burden at the actual target?

Targeting is validated by load reduction, not by allocation record.

3. Failure Signature

Typical signature:

delivery present
target accuracy↓
affected-node burden unchanged
allocation credit↑
local coherence↓
repair latency↑
H↑

Extended signature:

support reaches the visible node but not the burdened node
funding reaches the institution but not the field
repair reaches the symptom but not the cause
attention reaches the spectacle but not the wound
policy reaches the document but not the runtime

Common forms include:

funding centralized away from local repair
support programs designed around administrative categories rather than lived need
security spending on visible tools while analysts lack triage capacity
AI governance resources spent on policy statements while review teams remain under-resourced
justice processes funding procedure while affected nodes receive no repair
economic stimulus reaching intermediaries but not depleted households or communities
aid delivered to areas with visibility rather than areas with highest burden
health support focused on symptom metrics while underlying capacity remains depleted
interface redesign targeting appearance while user action pathways remain blocked
restoration resources spent on ceremonies rather than load reduction

The defining condition is not imperfect targeting.

The defining condition is that the system receives delivery credit while the actual need remains materially under-served.

4. Primary U-Layer Origin

Common origin layers:

• U1 — Power / Budgets: resources are allocated toward powerful, visible, fundable, or legitimacy-preserving targets.
• U2 — Configuration / Boundaries: need boundaries are misdrawn; target categories do not match affected-state geometry.
• U3 — Execution / Runtime: delivery routes through channels that fail to reach the real node.
• U4 — Information / Truth: allocation record substitutes for need fulfillment.
• U5 — Coordination / Time: delivery targets a phase that is not currently load-bearing.
• U6 — Coherence Field: visible delivery creates the feeling of support.
• U7 — Memory / Recurrence: historical targeting logic persists after need geometry changes.
• U8 — Environment / Field: broader field incentives favor legible targets over actual need.

Common manifestation layers:

• U1 — Budgets: flow is selected toward the wrong target.
• U2 — Boundaries: target map is wrong.
• U3 — Execution: support is routed incorrectly.
• U4 — Truth: delivery record replaces effect audit.
• U5 — Time: phase mismatch persists.
• U6 — Coherence Field: visible delivery masks missed need.

Mis-Targeting is primarily a U2 / U4 allocation-truth failure.

The system’s map of need does not match the actual field.

5. Typical Development Sequence

A common development sequence is:

1. A real need appears.
2. The need is translated into an administrative, economic, policy, interface, or institutional category.
3. The translation loses relevant state.
4. Delivery is routed according to the category.
5. The target receives resource or attention.
6. The affected node does not receive sufficient usable support.
7. Metrics show delivery occurred.
8. The system claims progress.
9. The burdened node compensates or deteriorates.
10. The system interprets continuing problems as separate or excessive.
11. More delivery is sent through the same mis-targeted channel.
12. Hidden debt grows beneath allocation success.

The loop often looks like:

need → category → allocation → wrong target → burden persists → more allocation

Another common loop is:

mis-targeting exposed → target renamed → delivery route unchanged → need remains unmet

Mis-Targeting becomes self-reinforcing when the wrong target becomes institutionally invested in remaining the recognized recipient.

6. Diagnostic Markers

Diagnostic markers include:

• Delivery records improve while affected-node burden remains.
• The actual burdened node cannot access support.
• Intermediaries receive resources but local need persists.
• Support is designed around categories that affected nodes do not fit.
• The system funds visibility instead of load reduction.
• Delivery goes to the symptom rather than the cause.
• Need is defined by the delivering system rather than the receiving state.
• Multiple programs exist but none reduce the primary burden.
• Support eligibility excludes the highest-need nodes.
• Resource flow is captured by administratively convenient layers.
• Delivery is evaluated by output rather than effect.
• Affected nodes must translate their need repeatedly to fit the target map.
• The same burden persists across several rounds of delivery.
• The wrong target becomes a gatekeeper.
• Restoration improves when delivery is rerouted, not when delivery volume increases.

Useful diagnostics:

• Need / Supply Fit: Tests whether delivered support matches actual need.
• Target Accuracy: Measures whether the intended target is the affected node.
• Resource Flow Integrity: Tests whether flow reaches the correct place.
• Affected-Node Burden: Measures remaining load after delivery.
• Layer Fit: Determines whether support reaches the correct layer.
• Delivery Adequacy: Measures adequacy after targeting is corrected.
• Restoration Capacity: Tests whether delivery enables repair.
• Hidden Debt: Tracks cost left in the unserved node.
• Auditability: Determines whether misrouting can be traced.
• Local Coherence: Tests whether the receiving field actually stabilizes.

7. Related Gates

Relevant gates include:

• Targeting Gate: Fails when delivery is routed to the wrong node, layer, phase, or need.
• Need Gate: Fails when the need is misread or misclassified.
• Delivery Gate: Fails when delivery does not reach the load-bearing target.
• Compatibility Gate: Fails when delivered form does not fit actual state.
• Layer Gate: Fails when support reaches the wrong system layer.
• Boundary Gate: Fails when affected-state boundaries are misdrawn.
• Restoration Gate: Fails when repair does not reach the burden source.
• Auditability Gate: Fails when delivery-path effects cannot be inspected.

The first common gate failure is usually the Targeting Gate.

The system sends support to what it can see, not what carries the load.

8. Related Operators

Relevant operators include:

• Γ — Selection: Selects which node, need, layer, or category receives delivery.
• Φ — Flow / Resource Movement: Routes resources, attention, authority, and repair.
• Λ — Compatibility: Tests whether delivery fits the actual target.
• Ψ — Observation / Interface: Determines what need is visible.
• Au — Auditability: Determines whether targeting can be inspected.
• K — Constraint / Load: Remains high on the unserved node.
• R — Restoration Capacity: Fails to activate when delivery misses the repair target.
• H — Hidden Debt: Accumulates where burden persists.
• O — Coherence: May appear improved through visible allocation.
• BΣ — Boundary Integrity: Determines whether target boundaries match affected-state boundaries.
• Τ — Trajectory / Time: Reveals persistent burden across delivery cycles.
• D — Damping: May temporarily buffer local harm or hide mis-targeting.
• G — Gain: Can amplify delivery into the wrong target.

Common operator pattern:

need appears
Ψ sees visible proxy
Γ selects proxy target
Φ routes resources to proxy
Λ fit with actual need remains low
K persists in affected node
R does not reach burden source
O appears improved through delivery record
H accumulates
Τ reveals persistent failure

The core operator inversion is:

delivery to recognized target → need addressed

instead of:

delivery to affected state → burden reduction → need addressed

Mis-Targeting turns allocation into false repair.

9. Related Laws and Invariants

Related Laws

• Hidden Debt Accumulation: missed need remains as deferred cost.
• Under-Delivery: the actual affected node remains under-supplied.
• Over-Delivery: the wrong node may receive excess.
• Phase Failure: delivery may target the wrong moment.
• Auditability Collapse: delivery path cannot be traced to effect.
• Observability Collapse: actual need is not visible.
• Success Proxy Substitution: allocation record substitutes for outcome.
• U4 Truth Substitution: delivery report substitutes for need truth.
• Resource Gatekeeping Capture: intermediaries capture flow intended for affected nodes.
• Restoration Starvation: repair fails where resources do not reach burden.

Related Invariants

• Delivery Must Reach the Correct Node: support must arrive where load exists.
• Support Must Match the Actual Need: form and target must fit.
• Allocation Requires Affected-State Visibility: targeting needs real state contact.
• Repair Must Target the Burden Source: repair delivered elsewhere is not repair.
• Resources Must Not Be Counted as Successful Until Fit Is Verified: allocation is not effect.
• Wrong-Layer Delivery Must Remain Auditable: layer mismatch must be traceable.
• Need Fit Must Override Delivery Theater: visible allocation cannot replace load reduction.

10. Common False Positives

Not every indirect delivery is Mis-Targeting.

Common false positives include:

• Delivery through an intermediary that demonstrably reaches the affected node.
• Support to infrastructure that directly reduces local burden.
• Preventive targeting before the burden becomes visible.
• Phase-aware delivery to a precursor need.
• Symbolic support paired with material delivery to the right node.
• Centralized delivery where central infrastructure is the true bottleneck.
• Broad delivery when the need is genuinely broad.
• Support that looks indirect but reduces the actual burden.
• Delivery to a representative with verified fidelity.
• Trial targeting with explicit feedback and correction loops.

Clarifying rule:

This is not Mis-Targeting unless delivery, support, attention, authority, enforcement, repair, or capacity is counted as successful while missing the actual affected node, need, layer, phase, boundary, scale, or usable form.

11. Common False Repairs

Common false repairs include:

• increasing delivery volume to the same wrong target
• renaming the target without changing flow
• creating more programs that use the same wrong category
• adding reporting requirements to prove delivery occurred
• funding intermediaries without effect audits
• blaming affected nodes for poor uptake
• treating visibility as need
• designing support around administrative convenience
• measuring allocation rather than burden reduction
• offering advice where capacity is needed
• delivering to leadership instead of operators
• delivering to policy instead of runtime
• delivering to metrics instead of affected state
• using symbolic repair to cover target failure

False repair often produces the loop:

need persists → more delivery to wrong target → delivery record improves → need persists

Another common loop is:

mis-targeting exposed → eligibility adjusted slightly → core target map unchanged → burden remains

The repair fails because it improves delivery appearance without correcting target geometry.

12. Restoration Direction

Restoration requires recontacting affected-node reality, auditing the delivery path, correcting the target map, and rerouting resources toward actual load reduction.

Primary restoration direction:

recontact the affected node,
audit the target map,
reroute flow,
and verify burden reduction

A fuller restoration path includes:

1. Name the delivered flow. Identify what resource, support, signal, attention, authority, care, enforcement, repair, or capacity was delivered.
2. Name the intended target. Identify where the system believed the delivery should go.
3. Name the actual affected node. Identify who or what carries the burden.
4. Compare target to need. Test whether the delivery target matches the load-bearing state.
5. Map the delivery path. Trace how resources moved through intermediaries, categories, tools, interfaces, or institutions.
6. Identify misrouting. Locate where delivery drifted away from need.
7. Audit target incentives. Determine whether the wrong target benefits from remaining recognized.
8. Reroute usable flow. Move resources, authority, support, or repair toward the actual burden.
9. Correct layer and phase. Ensure delivery reaches the right system level and timing.
10. Reduce proxy authority. Stop counting intermediary receipt as affected-node repair.
11. Verify burden reduction. Confirm load actually falls where need exists.
12. Repair accumulated hidden debt. Address cost from prior mis-targeting.
13. Install targeting feedback. Let affected nodes update the target map.
14. Validate local coherence. Confirm the receiving node stabilizes.

A valid restoration path should reduce:

target error
proxy capture
affected-node burden
allocation theater
resource misrouting
wrong-layer support
hidden debt
repair latency
local incoherence

Mis-Targeting is not repaired by sending more.

It is repaired by sending correctly.

13. Cross-Module Links

• Economy: Core allocation failure; delivery exists but does not reach the actual need.
• Diagnostics: Requires target-accuracy, need/supply-fit, layer-fit, resource-flow, and affected-node-burden diagnostics.
• Restoration: Repair fails when resources do not reach the burden source.
• Justice: Justice resources can target procedure, institutions, or optics while affected nodes remain unrepaired.
• Cybernetics: Mis-targeting indicates failed observation, selection, compatibility, and control routing.
• Scaling: At scale, allocation often follows legible categories rather than actual local need.
• Security: Security spend can target tools, dashboards, or compliance while real risk remains elsewhere.
• AI Governance: Governance resources can target policy language, public messaging, or benchmarks rather than review capacity and affected-user repair.
• Interfaces: Interfaces shape what need is visible and therefore what receives delivery.
• Coherence: Local coherence does not improve unless delivery reaches the load-bearing node.

14. Relationship to Parent / Child Modes

Production treatment: Canon / Economy Parent

This mode maps upward to:

• FM-ECO-001 — Under-Delivery
• FM-CORE-003 — Success Proxy Substitution
• FM-C-001 — Observability Collapse
• FM-CORE-004 — Auditability Collapse
• FM-CORE-002 — Hidden Debt Accumulation

Sibling or related Economy modes include:

• FM-ECO-001 — Under-Delivery
• FM-ECO-002 — Over-Delivery
• FM-ECO-004 — Stasis / Blockage
• FM-ECO-005 — Economic Leakiness
• FM-ECO-006 — Shunting / Bypass
• FM-ECO-007 — Phase Failure
• FM-ECOX-003 — Mis-Targeting
• FM-ECOX-004 — Late Delivery
• FM-ECOX-014 — Suppression-by-Abstraction
• FM-ECOX-016 — Risk Model Theater

Related cross-family modes include:

• FM-JC-004 — Under-Resourced Justice
• FM-R-004 — Repair Burden Externalization
• FM-R-007 — Repair Suppression via Efficiency
• FM-C-010 — Requisite Variety Failure
• FM-C-015 — Proxy-Relay Drift
• FM-SEC-006 — Metric Capture / Reward-Hacked Security
• FM-OMD-009 — Restoration Bottleneck Collapse
• FM-AIX-001 — Responsibility Diffusion
• FM-AIX-006 — Template Capture
• FM-RX-004 — Capacity-Inverting Restoration

Aliases preserved from source material:

• Mis-Targeting
• Wrong-Target Delivery
• Misdirected Delivery
• Wrong-Node Delivery
• Wrong-Layer Support
• Wrong-Need Allocation
• Targeting Failure
• Allocation Misfit
• Support Misrouting
• Repair Mis-Targeting

15. Minimal Entry Version

Definition: Mis-targeting occurs when resource, support, signal, value, care, attention, authority, repair, enforcement, or capacity is delivered, but to the wrong node, layer, phase, need, boundary, scale, interface, or form, leaving the actual coherence requirement unmet while the system records delivery as successful.

Signature:

delivery present
target accuracy↓
affected-node burden unchanged
allocation credit↑
local coherence↓
repair latency↑
H↑

Restoration direction:

• name the delivered flow
• name the intended target
• name the actual affected node
• compare target to need
• map the delivery path
• identify misrouting
• audit target incentives
• reroute usable flow
• correct layer and phase
• reduce proxy authority
• verify burden reduction
• repair accumulated hidden debt
• install targeting feedback
• validate local coherence

16. Machine-Readable Summary

failure_mode:
  id: "FM-ECO-003"
  name: "Mis-Targeting"
  family: "Economy"
  production_treatment: "Canon / Economy Parent"
  parent_modes:
    - "FM-ECO-001 — Under-Delivery"
    - "FM-CORE-003 — Success Proxy Substitution"
    - "FM-C-001 — Observability Collapse"
  primary_failure: "Delivery, support, attention, authority, enforcement, repair, or capacity is counted as successful while missing the actual affected node, need, layer, phase, boundary, scale, or usable form."
  source: "UTS — Failure Modes Registry"
  source_id: "FM-ECO-003"
  scope_note: "Conceptual and systems-oriented; does not treat allocation, prioritization, triage, routing, delegation, proxy delivery, phased support, indirect investment, or mediated resource flow as inherently failed."
  aliases:
    - "Mis-Targeting"
    - "Wrong-Target Delivery"
    - "Misdirected Delivery"
    - "Wrong-Node Delivery"
    - "Wrong-Layer Support"
    - "Wrong-Need Allocation"
    - "Targeting Failure"
    - "Allocation Misfit"
    - "Support Misrouting"
    - "Repair Mis-Targeting"
  signature:
    - "delivery present"
    - "target accuracy↓"
    - "affected-node burden unchanged"
    - "allocation credit↑"
    - "local coherence↓"
    - "repair latency↑"
    - "H↑"
  primary_layers:
    origin:
      - "U1 — Power / Budgets"
      - "U2 — Configuration / Boundaries"
      - "U3 — Execution / Runtime"
      - "U4 — Information / Truth"
      - "U5 — Coordination / Time"
      - "U6 — Coherence Field"
      - "U7 — Memory / Recurrence"
      - "U8 — Environment / Field"
    manifestation:
      - "U1 — Budgets"
      - "U2 — Boundaries"
      - "U3 — Execution"
      - "U4 — Truth"
      - "U5 — Time"
      - "U6 — Coherence Field"
  state_variables:
    - "Γ"
    - "Φ"
    - "Λ"
    - "Ψ"
    - "Au"
    - "K"
    - "R"
    - "H"
    - "O"
    - "BΣ"
    - "Τ"
    - "D"
    - "G"
  first_gate_failure: "Targeting Gate"
  restoration:
    - "Targeting Audit"
    - "Affected-Node Need Recontact"
    - "Resource Re-Routing"
    - "Layer Fit Repair"
    - "Allocation Recalibration"
    - "Hidden Debt Accounting"
    - "Local Coherence Restoration"
    - "Repair Target Rebinding"
    - "Delivery Verification"