Manufactured Dependency for Role Capture¶
Core Idea¶
An agent covertly creates or sustains a problem in order to keep occupying the valued role — saviour, indispensable expert, vigilant carer, sole supplier — attached to solving it. The reward is coupled to the problem's persistence, so asking the agent to fix it is asking them to design their own obsolescence.
How would you explain it like I'm…
Secretly Breaking the Blocks
Imagine a kid who secretly knocks over the blocks so the grown-ups always need him to be the one who fixes them and calls him a great helper. If the blocks stayed standing, nobody would need his help anymore — so he keeps quietly knocking them down. He's not really fixing a problem; he's making sure the problem never goes away.
Keeping the Problem Alive
Manufactured dependency for role capture is when someone secretly creates or keeps a problem going so they can stay in the valued job of solving it — the hero, the expert, the protector, the only one who can help. Their reward comes from the problem existing, not from it being gone, so they actually work to keep it around instead of ending it. It has to be sneaky: if people realized what was happening, the role would lose its respect, because that respect depends on looking like they're meeting a real need. The simple test is a what-if question: would this person's special role still exist if the problem were truly solved tomorrow? If the honest answer is 'no, the role would vanish,' that's the warning sign.
Make the Need, Keep the Role
Manufactured dependency for role capture is an arrangement where an agent covertly creates or sustains a problem in order to occupy the valued role — savior, indispensable expert, vigilant carer, sole supplier, protector — that's attached to solving that problem. The key feature is a perverse coupling: the agent's reward is tied to the existence of the problem, not its eradication, so the agent rationally invests in perpetuating it rather than ending it. The behavior is covert by necessity, because openly admitting it would destroy the role's legitimacy — the role draws its value from appearing to serve a genuine need. It's distinct from 'misaligned incentives' in general, which only name the risk of such behavior, and from honestly serving a pre-existing problem, which has no covert manufacture. Its diagnostic core is a counterfactual: would the role survive if the problem were genuinely solved tomorrow? When the honest answer is 'the role would disappear,' the conditions for capture are present — whatever the agent's conscious intent.
Manufactured dependency for role capture is the structural arrangement in which an agent covertly creates or sustains a problem in a system in order to occupy the valued role — savior, indispensable expert, vigilant carer, sole supplier, protector — that is attached to solving that problem. The agent's reward is tied to the existence of the problem, not to its eradication, so the agent rationally invests in perpetuating it rather than ending it. The behavior is covert by necessity: explicit acknowledgement would destroy the role's legitimacy, since the role draws its value from appearing to serve a genuine need. The essential commitment is a perverse coupling between an agent's reward gradient and the persistence of the very condition the agent's role exists to remove. Four roles carry the structure: a role whose social, economic, or symbolic value is contingent on the continued existence of a problem; an agent who occupies or seeks that role; a covert action by which the agent creates or perpetuates the problem rather than letting it be resolved by some other party; and a role-reward harvest the agent collects so long as the problem persists. The arrangement is distinct from misaligned incentives generally, which name only the risk of such behavior, and from honest service of a pre-existing problem, which lacks the covert manufacture. Its diagnostic core is a counterfactual: would the role survive if the problem were genuinely solved tomorrow? When the honest answer is 'the role would disappear,' the conditions for capture are present, whatever the agent's conscious intent.
Broad Use¶
- Clinical: A caregiver covertly induces illness in a dependent (Munchausen-by-proxy) to occupy the role of vigilant carer.
- Software engineering: An engineer under-documents or destabilizes a system to remain the indispensable firefighter.
- Knowledge work: A specialist hoards documentation and training so no replacement can emerge.
- Politics: Patronage actors manufacture client dependencies through gate-kept benefits to harvest votes and loyalty.
- Organized crime: Protection rackets sustain the very threat against which they sell protection.
- Marketing: Industries manufacture insecurities (odour, ageing) for which they sell the cure.
- Cybersecurity: Vendors whose revenue scales with the threat environment have incentive against eradicating it.
- Bureaucracy: A unit perpetuates problems within its remit to justify budget and headcount.
Clarity¶
Separates two diagnoses routinely conflated — competence (the role is performed well) and manufacture (the problem is being sustained) — which are independent axes, so an agent can be both genuinely skilled and covertly capturing.
Manages Complexity¶
Compresses medical abuse, hero syndrome, expert hoarding, racketeering, and empire-building into one frame — role-reward contingent on problem-persistence — making the same eradication-aligned fix portable across substrates.
Abstract Reasoning¶
Relocates the diagnosis from agent character to reward direction: a system that pays its solvers in proportion to a problem's persistence fills the role with manufacturers regardless of the candidate pool's morality.
Knowledge Transfer¶
- Clinical → organizational: The Munchausen-by-proxy diagnostic — covert manufacture for role-reward — ports into analysis of empire-building managers.
- Public health → security: "Designing for your own obsolescence" (programs that shrink their own demand) ports as rewarding eradication over perpetual management.
- Therapy → consulting: The principle that success is the client's discharge ports as "design for graduation, not retention."
Example¶
The organizational firefighter: the engineer whose status derives from heroic 2am saves, who under-documents and leaves components fragile — sustaining the very fragility the role depends on. The counterfactual test cuts through character: would the role survive a genuinely robust system?
Relationships to Other Primes¶
Parents (1) — more general patterns this builds on
- Manufactured Dependency for Role Capture is a kind of Agency Problem — The file: role capture is 'a species of' the agency problem — the SPECIFIC, sharp case where the agent's reward gradient points toward SUSTAINING the problem the role exists to remove, plus the covert-manufacture commitment + counterfactual-demand signature. agency_problem is the genus.
Path to root: Manufactured Dependency for Role Capture → Agency Problem → Agency
Not to Be Confused With¶
- Manufactured dependency is not Regulatory Capture because role capture has an agent covertly manufacturing the problem the role depends on, whereas capture has an external interest redirecting an institution's purpose.
- Manufactured dependency is not Rent-Seeking because role capture covertly sustains the problem itself, whereas rent-seeking manipulates the allocation environment without creating value and need not be covert.
- Manufactured dependency is not the Agency Problem because role capture is the specific perverse coupling where reward tracks problem-persistence, whereas the agency problem names misaligned principal-agent incentives in general.