First Foundation — Anti-Patterns
Related Foundation: Deferred Fragility Export
Purpose
This Pattern Application Note provides a field-ready method for identifying, analyzing, and communicating live instances of the Extractive Dependency Trap while events are still unfolding.
Its goal is not attribution or blame, but structural diagnosis: determining whether a situation reflects a temporary disruption or a deeper design failure with long-term civic consequences.
When to Use This Note
Apply this note when observing cases involving:
- Sudden institutional withdrawal (or credible threat of withdrawal)
- Community shock disproportionate to the immediate event
- Claims of “resilience” following loss of a dominant provider
- Public confusion over who is responsible for remediation
- Visible physical or institutional remnants of prior centralization
This note is especially relevant during Crisis phases, when Deferred Fragility Export becomes legible.
Step 1: Identify the Dominant Node
Ask:
- Was there a single actor or small cluster providing an essential service, function, or economic anchor?
- Did that actor replace a diverse local ecosystem, rather than complement it?
If no dominant node existed, this is likely not an Extractive Dependency Trap.
Step 2: Classify the Entry Mode
Determine how the actor originally entered the system:
- Transactional framing
(“lower prices,” “efficiency,” “cost savings,” “innovation”) - Institutional effects
(dependency, loss of alternatives, reshaping of local capacity)
If the actor entered as a transaction but behaved as an institution, flag Unlabeled Institutional Capture.
Step 3: Examine Exit Conditions
Ask:
- Is exit legally permitted and economically rational for the actor?
- Are there formal obligations to remediate harm, restore capacity, or fund transition?
- Would exit impose costs far exceeding those of the pre-entry system?
If exit is optional for the actor but catastrophic for the community, the trap is active.
Step 4: Trace the Blame Path
Observe post-failure narratives:
- Is blame shifting toward:
- local government?
- community resilience?
- individual adaptation?
- Is the exiting actor treated as neutral, inevitable, or absent from the causal story?
Downward or sideways blame displacement is a strong Extractive Dependency Trap signal.
Step 5: Identify Physical or Institutional Artifacts
Look for institutional scar tissue, such as:
- Empty single-purpose infrastructure
- Facilities too large or specialized for local reuse
- Loss of skills, suppliers, or governance capacity
- Long recovery timelines with no restoring actor
These artifacts confirm Deferred Fragility Export has already occurred.
Step 6: Distinguish From Adjacent Failure Modes
Use this contrast to avoid misclassification:
- Not a cyclical downturn
(those preserve optionality) - Not creative destruction
(replacement capacity is absent) - Not Pathological Lock-In
(this is abandonment, not forced continuation)
If the system is worse off because exit was allowed, this anti-pattern applies.
Common Live Case Categories
Without naming specific entities, this anti-pattern commonly appears in:
- Retail consolidation and withdrawal
- Hospital system mergers and closures
- Broadband or utility monopolies
- Logistics hub centralization
- Corporate housing ownership
- Outsourced civic IT platforms
- Supply-chain offshoring reversals
Surface form varies. Structure does not.
Communication Guidance
When discussing live cases publicly or politically:
- Focus on design choices, not actor intent
- Avoid moral language; emphasize predictable outcomes
- Reframe “resilience” as costly recovery from preventable design failure
- Highlight exit modeling gaps rather than entry decisions
This keeps the analysis defensible and non-partisan.
Diagnostic Summary (Quick Test)
A live case likely reflects the Extractive Dependency Trap if:
- Dependency was created under efficiency rhetoric
- Exit was legal, rational, and unilateral
- Recovery burden fell locally
- Physical remnants remain
- Responsibility is diffuse or inverted
If all five are present, classification is warranted.
Relationship to Future Work
This Application Note is intended to pair with:
- Counter-patterns addressing exit obligations
- Policy guardrails for dependency creation
- CivMMI diagnostics on institutional maturity
- Structural audits of proposed large-scale projects
One-Line Field Test
If a system becomes fragile precisely because an actor is allowed to leave, the Extractive Dependency Trap is active.