Manufactured Dependency for Role Capture¶
Core Idea¶
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 — saviour, 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 the problem rather than ending it. The behaviour 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. First, a role whose social, economic, or symbolic value is contingent on the continued existence of a problem. Second, an agent who occupies or seeks that role. Third, a covert action by which the agent creates or perpetuates the problem, rather than allowing it to be resolved by some other party. Fourth, a role-reward harvest that the agent collects so long as the problem persists. The arrangement is distinct from misaligned incentives generally, which name only the risk of such behaviour, 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.
How would you explain it like I'm…
Secretly Breaking the Blocks
Keeping the Problem Alive
Make the Need, Keep the Role
Structural Signature¶
the valued role contingent on a problem's persistence — the agent occupying or seeking that role — the covert action creating or sustaining the problem — the role-reward harvested while the problem persists — the perverse coupling of reward gradient to problem-persistence — the counterfactual-demand invariant: would the role survive if the problem were genuinely solved tomorrow?
A situation exhibits manufactured dependency for role capture when each of the following holds:
- A persistence-contingent role. A role — saviour, indispensable expert, vigilant carer, sole supplier, protector — draws its social, economic, or symbolic value from the continued existence of a problem, not from its eradication.
- An agent. Some agent occupies or seeks that role and stands to collect its reward.
- A covert action. The agent covertly creates or sustains the problem rather than allowing it to be resolved; covertness is necessary because explicit acknowledgement would destroy the role's legitimacy.
- A role-reward harvest. The agent collects the role's reward — devotion, indispensability, fees, loyalty, protection income, budget — so long as the problem persists.
- A perverse coupling. The agent's reward gradient points away from resolution, so asking the agent to design the resolution is asking them to design their own obsolescence.
- The counterfactual-demand invariant. When the honest answer to "would the role survive a genuine solution tomorrow?" is "the role would disappear," capture conditions are present whatever the agent's conscious intent; reward direction matters more than agent character, and solution-resistance is itself diagnostic.
The components compose into a design discipline over an accusation: separate diagnostician from provider, reward eradication, sunset the role, and audit counterfactual demand, since the covert-manufacture commitment is hard to verify from outside.
What It Is Not¶
- Not
regulatory_capture. Capture is an external interest bending an institution to serve it; this prime is an agent covertly sustaining a problem to keep occupying the valued role attached to solving it — capture redirects an institution's purpose, role capture manufactures the problem the role depends on. - Not
rent_seeking. Rent-seeking extracts value by manipulating the allocation environment without creating value; role capture specifically creates or sustains the problem whose solution is the agent's role, with covertness required because acknowledgement would destroy the role's legitimacy. - Not the
agency_problem. The agency problem is misaligned incentives between principal and agent in general; this is the specific perverse coupling where the agent's reward is tied to the persistence of the very problem the role exists to remove — asking them to solve it is asking them to design their own obsolescence. - Not
moral_hazard. Moral hazard is taking more risk because another bears the cost; role capture is covertly manufacturing the problem itself to harvest the role-reward, a deliberate sustaining move, not a risk-shifting response to insurance. - Not
conflict_of_interest. A conflict of interest is competing loyalties that may bias judgment; role capture is the realised pathology in which the agent acts to sustain the problem — the counterfactual-demand test ("would the role survive a genuine solution?") is what distinguishes a mere conflict from active capture. - Common misclassification. Branding a competent, devoted provider a role-capturer. Competence and manufacture are orthogonal axes, and the covert-manufacture commitment is hard to verify from outside; the prime's defensible use is incentive design (reward eradication, separate detector from solver) over after-the-fact accusation.
Broad Use¶
- Clinical (Munchausen-by-proxy) — a caregiver covertly induces illness in a dependent to occupy the role of vigilant carer; the role-value depends on continued illness.
- Organizational firefighter syndrome — an engineer under-documents or subtly destabilizes a system to remain the indispensable fixer; the role depends on continued fragility.
- Indispensable-expert hoarding — a specialist withholds documentation and training so no replacement can emerge; the role depends on exclusivity.
- Patronage politics / clientelism — actors manufacture or sustain client dependencies through gate-kept benefits to harvest votes and loyalty.
- Protection rackets — protectors sustain the threat against which they offer protection; the role depends on the continued threat.
- Marketing-manufactured insecurities — industries manufacture problems (odour, ageing, awkwardness) for which they sell solutions; the role depends on continued felt inadequacy.
- Cybersecurity vendor incentives — vendors profiting from high-threat environments have structural incentive against eradicating the threat classes they specialize in.
- Therapeutic dependency — counsellors who cultivate dependency rather than working toward discharge; the role depends on continued return.
- Bureaucratic empire-building — a unit perpetuates problems within its remit to justify budget and headcount.
Clarity¶
Naming the arrangement separates two diagnoses that are routinely conflated. The competence diagnosis says the agent performs the role well; the manufacture diagnosis says the agent is also sustaining the problem the role exists to solve. The two are independent. A vigilant carer may be both genuinely devoted and covertly inducing illness; a firefighter engineer may be both highly competent and quietly sabotaging the system whose fragility justifies the firefighting. Conflating the diagnoses leads either to false accusation of honest carers or to false exoneration of role-capturers. The prime holds the two axes apart so that competence and manufacture can be assessed separately.
It also clarifies why resolution is structurally unavailable from within the role. The agent's reward gradient points away from resolution, so asking the agent to design the resolution plan is structurally identical to asking them to design their own obsolescence. The clarifying force is to redirect attention from the agent's character to the reward direction: a system that pays its problem-solvers in proportion to the problem's persistence will tend to fill the role with manufacturers regardless of the average morality of the candidate pool, because the few who manufacture outcompete the many who do not.
Manages Complexity¶
The arrangement compresses many surface-different phenomena — medical abuse, software toxic-hero syndrome, expert hoarding, patronage politics, racketeering, marketing manufacture, vendor capture, therapeutic dependency, bureaucratic empire-building — into one diagnostic frame: the role-reward is contingent on the persistence of the problem. With the frame named, the intervention shape becomes portable across substrates. Design the incentive so the agent's reward grows with eradication rather than with ongoing service. Separate the role of problem-detector from problem-solver so the party that diagnoses demand is not the party that profits from it. Build in sunset clauses that force the role to justify its continued existence. Audit demand-for-the-role independently of the role's own reports.
The leverage is that the same eradication-aligned design replaces a scatter of substrate-specific remedies. Public-health programs that succeed by shrinking their own demand, consulting engagements designed for graduation rather than retention, and security policies that reward vulnerability eradication rather than perpetual management are the same structural intervention wearing different clothes. The prime lets a fix found in one substrate be recognized and reapplied in another, and lets the design of incentive structures pre-empt capture rather than relying on post-hoc detection.
Abstract Reasoning¶
Manufactured dependency for role capture trains a reasoner to ask:
- Whose role draws its value from the persistence of a problem, rather than from its eradication?
- Does the agent's reward gradient point toward solving the problem, or toward keeping it alive?
- Is solution-resistance present — are proposed fixes subtly sabotaged or pre-emptively dismissed by the role-occupant, and is that resistance itself evidence?
- What would happen to the role if the problem were genuinely solved tomorrow? If the role would vanish, is capture risk elevated?
- Is the right repair structural (reward eradication, separate detector from solver, sunset the role) rather than personal (replace the individual, who will face the same incentives)?
- Are competence and manufacture being assessed on separate axes, or collapsed into a single judgement?
The non-obvious inferences are that reward direction matters more than agent character, that solution-resistance is diagnostic, that eradication-reward is the structural fix that addresses the problem at the system rather than the individual level, and that counterfactual demand ("would the role survive a real solution?") is the cleanest detector. Each of these survives substrate change because none depends on the particular content of the problem, only on the coupling between role-value and problem-persistence.
Knowledge Transfer¶
Role mappings across domains:
- Role ↔ carer / fixer / expert / patron / protector / vendor / department
- Agent ↔ caregiver / engineer / consultant / political actor / racketeer
- Problem ↔ illness / system fragility / knowledge gap / client need / threat / felt inadequacy
- Covert manufacture ↔ induced illness / under-documentation / hoarded expertise / sustained threat
- Role-reward harvest ↔ devotion / indispensability / fees / loyalty / protection income / budget
- Counterfactual demand ↔ "would the role survive a genuine solution?"
A psychiatrist analyzing Munchausen-by-proxy, an engineering manager confronting a toxic-hero, a competition regulator examining vendor capture, and an ethicist auditing therapeutic dependency are reasoning about the same structure: a role whose value is contingent on a problem the role-occupant has covert incentive to sustain. The transfers are concrete. The Munchausen-by-proxy diagnostic shape — covert manufacture for role-reward — ports into organizational analysis of empire-building managers. The clientelism literature on manufactured dependency illuminates vendor-capture dynamics in procurement. The public-health principle of "designing for your own obsolescence" — sanitation programs whose success shrinks their own demand — ports into security policy as the discipline of rewarding eradication, not management. The therapeutic principle that the practitioner's success is the client's discharge ports into consulting as "design for graduation, not retention." What moves between fields is the literal coupling — role-value tied to problem-persistence — together with its portable repair kit (separate diagnostician from provider, reward eradication, sunset the role, audit counterfactual demand) and its delicate ethics: because the covert-manufacture commitment is hard to verify from outside and overlaps with honest devoted service, the prime's most defensible use is in designing incentive structures that avoid the trap rather than in accusing particular agents after the fact.
Examples¶
Formal/abstract¶
The organisational firefighter, treated as an incentive structure, is the cleanest worked instance because the counterfactual test resolves it sharply. The persistence-contingent role is "indispensable fixer" — the engineer everyone calls when the system breaks at 2am, whose status, bonus, and identity derive from that role. The agent is the engineer occupying it. The covert action is the structurally available move that distinguishes manufacture from honest service: under-documenting the system, leaving fragile components un-hardened, and keeping critical knowledge in their head rather than in a runbook — each a small act that sustains the fragility the firefighting role depends on, none of which need be conscious sabotage. The role-reward harvest is the indispensability, the visibility of heroic saves, the budget and deference that flow to the person who keeps rescuing the system. The perverse coupling is exact: the engineer's reward gradient points away from a stable, well-documented system, so asking them to design the reliability roadmap is asking them to design their own obsolescence. The counterfactual-demand invariant is the diagnostic that cuts through character questions: would the role survive if the system were genuinely made robust tomorrow? If the honest answer is "the role would vanish," capture conditions are present whatever the engineer's intent, and solution-resistance — fixes subtly dismissed or de-prioritised by the role-occupant — is itself evidence. Crucially the competence and manufacture axes are independent: the engineer may be both genuinely skilled and quietly sustaining fragility, so the structural repair (reward eradication, separate the system-designer from the firefighter, sunset the hero role) targets the incentive, not the individual, who would face the same gradient if replaced.
Mapped back: Firefighter syndrome instantiates every role — fixer role contingent on fragility, the engineer as agent, under-documentation as covert action, indispensability as harvest, the reward gradient pointing away from resolution — and the counterfactual-demand test (would the role survive a robust system?) is the cleanest detector, with solution-resistance as corroborating evidence.
Applied/industry¶
Cybersecurity vendor incentives and clinical Munchausen-by-proxy are two applied instances spanning very different substrates while sharing the structure. In the vendor case, the persistence-contingent role is "essential security provider"; the agent is a vendor whose revenue scales with the customer's threat environment; the covert action need not be manufacturing threats outright but can be the subtler move of optimising for perpetual management over eradication — emphasising monitoring subscriptions and incident-response retainers rather than fixes that would shrink the threat class the vendor specialises in. The role-reward harvest is recurring revenue contingent on the threat persisting, and the counterfactual-demand test asks whether the vendor's business survives if the vulnerability class were permanently closed. The structural repair is to design the incentive so the vendor is rewarded for eradication — the public-health discipline of "designing for your own obsolescence," where a sanitation program's success shrinks its own demand, ported into procurement as eradication-aligned contracts. The clinical instance, Munchausen-by-proxy, is the same coupling on a psychological substrate: the role is "vigilant devoted carer," the covert action is inducing illness in a dependent, the harvest is medical attention and sympathy, and the role-value depends on the dependent's continued illness — and here the prime's competence-versus-manufacture separation is ethically load-bearing, because the carer may be genuinely devoted and covertly inducing harm, so the diagnostic must hold both axes apart rather than collapsing them.
Mapped back: Vendor capture and Munchausen-by-proxy are the same role-value-tied-to-problem-persistence coupling as firefighter syndrome, with recurring revenue and caregiver devotion as the harvests — repaired by eradication-aligned incentive design rather than after-the-fact accusation, since the covert-manufacture commitment is hard to verify and overlaps with honest service.
Structural Tensions¶
T1 — Manufacture versus honest service (sign). The structure's load-bearing distinction is between covertly sustaining a problem and honestly serving a pre-existing one — but the two are behaviourally identical from outside, and the covert-manufacture commitment is hard to verify. The failure mode is manufacture over-attribution: branding a genuinely devoted carer or a genuinely skilled firefighter a role-capturer on circumstantial grounds, doing real harm to honest agents. Diagnostic: rely on the counterfactual-demand test and reward-direction rather than on observed competence or devotion — and treat the prime's most defensible use as incentive design rather than after-the-fact accusation of named agents.
T2 — Competence versus manufacture as independent axes (measurement). Competence and manufacture are orthogonal — an agent can be both highly skilled and covertly sustaining the problem — yet they are routinely collapsed into one judgment. The failure mode is axis collapse: exonerating a role-capturer because they perform the role excellently ("she's our best carer / our most reliable fixer"), or accusing an incompetent honest servant of manufacture. Diagnostic: assess the two axes separately — measure problem-persistence-contingency of the reward independently of how well the role is executed; high competence is evidence about the role, not about manufacture.
T3 — Reward direction versus agent character (scopal). The prime relocates the diagnosis from character to reward gradient: a system paying problem-solvers in proportion to problem-persistence fills the role with manufacturers regardless of the candidate pool's average morality. The failure mode is character-focused remedy: replacing the individual rather than the incentive, so the successor faces the identical gradient and reproduces the behaviour. Diagnostic: ask whether the reward structure would produce capture from an average agent — if yes, the repair is structural (reward eradication, separate detector from solver, sunset the role), and swapping the person is theatre.
T4 — Resolution unavailable from within the role (coupling). Because the agent's reward gradient points away from resolution, asking them to design the fix is asking them to design their own obsolescence — so the very party with the most expertise is the one who cannot be trusted to end the problem. The failure mode is poacher-as-gamekeeper: tasking the role-occupant with the eradication roadmap, which they rationally sabotage or slow-walk. Diagnostic: structurally separate the party that diagnoses demand and designs the solution from the party that profits from the problem's persistence — never source the obsolescence plan from the role whose existence it would end.
T5 — Counterfactual-demand test versus genuinely persistent problems (temporal). "Would the role survive a real solution tomorrow?" is the cleanest detector, but some problems are genuinely permanent (ongoing threats, chronic conditions) where the role should survive because the problem cannot be eradicated. The failure mode is false-positive capture: reading the durability of a role attached to an irreducibly persistent problem as evidence of manufacture, when no covert action is sustaining it. Diagnostic: separate "the problem persists because the agent sustains it" from "the problem persists because it is structurally unsolvable" — only the former is capture; check whether a credible eradication path even exists before reading persistence as manufacture.
T6 — Eradication-reward design versus gaming the new metric (temporal/coupling). The structural fix is to reward eradication rather than ongoing service — but once "eradication" is the paid target, the agent can declare premature victory, redefine the problem as solved, or shift the harvest to a new manufactured problem. Here the boundary is with incentive_design and Goodhart dynamics. The failure mode is eradication theater: collecting the eradication reward by re-labelling rather than genuinely removing the problem, or manufacturing a successor problem to capture next. Diagnostic: verify eradication against an independent measure of demand (not the agent's own report), and watch for the harvest migrating to an adjacent newly-sustained problem after the rewarded one is nominally closed.
Structural–Framed Character¶
Manufactured dependency for role capture sits at the far framed end of the structural–framed spectrum: aggregate 1.0, with all five criteria at the maximum. It is among the most thoroughly framed primes in the catalog — its content is a deeply social-and-psychological frame, not a bare relational structure. There is a genuine coupling underneath (a role whose value is contingent on a problem's persistence, an agent who covertly sustains it to harvest the role-reward), but every diagnostic reads framed and the prose must own it.
vocab_travels reads 1.0 because the load-bearing terms — role, covertness, saviour, harvest, vendor, capture, manufacture — are social-and-psychological vocabulary that travels with the prime into every instance; even the cross-domain cases (Munchausen-by-proxy, firefighter syndrome, protection rackets) are told in the language of roles and covert intent. evaluative_weight is 1.0: the prime carries a heavy normative load, naming a pathology (covert manufacture, capture) and a perverse coupling that is disapproved throughout — the prime's own ethics section repeatedly cautions against the accusatory force of the frame. institutional_origin is 1.0: it is rooted in social-and-political incentive structures, a creature of human institutions and roles. human_practice_bound is 1.0: every instance requires intentional agents occupying roles with reward gradients; there is no physical or biological-substrate-indifferent version, since even the clinical case turns on a caregiver's covert intent. import_vs_recognize is 1.0: invoking the prime imports a whole diagnostic-and-design apparatus (counterfactual-demand test, separate detector from solver, reward eradication, sunset the role) rather than merely recognising a pattern already wired into the world. The relational coupling is genuine, but every criterion reads framed, correctly placing this at the spectrum's framed pole.
Substrate Independence¶
Manufactured dependency for role capture is a weakly substrate-independent prime — composite 2 / 5 on the substrate-independence scale, and the low band is honest. Its domain breadth (3 / 5) is real but confined to social and psychological substrates: the pattern of an agent covertly creating or sustaining the very problem whose solution defines a valued role recurs across clinical settings (Munchausen by proxy), organizational life (firefighter syndrome, the engineer who guards a fragility only they can fix), politics, marketing (manufacturing a need), cybersecurity (selling protection against a threat one seeds), therapeutic relationships, and bureaucracy. The structural abstraction (2 / 5) is deliberately low because every instance requires an intentional agent with a role whose reward is coupled to a problem's persistence — the captured object is a role whose value is contingent on an unsolved problem, and "role," "incentive," and "covert manufacture" are irreducibly intentional-agent concepts with no medium-neutral relational core. There is no physical or biological substrate in which a problem is "manufactured to sustain a role," because the mechanism presupposes a goal-directed occupant reasoning about its own indispensability. The transfer evidence (3 / 5) is genuine within that band — the counterfactual-demand test ("would the role survive if the problem were solved tomorrow?") and the persistence-coupled-incentive structure transfer recognizably from Munchausen-by-proxy to firefighter-syndrome to manufactured-need marketing — but the transfer is among social/psychological substrates of the same broad kind, not across substrate classes. The pattern is real and recurs across human domains, but it is bound to intentional agents with roles at its core, which correctly pins the composite at the weak end of the scale.
- Composite substrate independence — 2 / 5
- Domain breadth — 3 / 5
- Structural abstraction — 2 / 5
- Transfer evidence — 3 / 5
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
Neighborhood in Abstraction Space¶
Manufactured Dependency for Role Capture sits in a sparse region of abstraction space (60th percentile for distinctiveness): few abstractions share its structure, so a faithful description tends to retrieve it precisely rather than landing on a neighbor.
Family — Context Binding & Cue Capture (9 primes)
Nearest neighbors
- Proximity Capture — 0.76
- Authority Handoff — 0.73
- Habit — 0.70
- Role Conflict — 0.69
- Path Dependence — 0.69
Computed from structural-signature embeddings · 2026-06-14
Not to Be Confused With¶
The nearest neighbour is regulatory_capture (similarity ~0.89), and the two share the language of "capture" and an interest sustained against the public good — but they capture different objects. Regulatory capture is the process by which an external interest (an industry, a faction) bends an institution meant to regulate it into serving that interest instead; the institution's purpose is redirected from outside. Manufactured dependency for role capture runs through a different mechanism: an agent covertly creates or sustains the very problem whose solution defines a valued role, so the agent's reward is coupled to the problem's persistence. The captured object in regulatory capture is an institution's regulatory purpose; in role capture it is a role whose value is contingent on an unsolved problem. The diagnostic differs accordingly: regulatory capture is detected by tracing whose interests the institution actually serves, while role capture is detected by the counterfactual-demand test — would the role survive if the problem were genuinely solved tomorrow? A practitioner who frames a firefighter-syndrome engineer or a Munchausen-by-proxy carer as "captured" looks for an external capturing interest that may not exist; the manufacturing is internal to the role-occupant's own incentive.
The prime is also confusable with rent_seeking, since both extract value through a distortion rather than through genuine value creation. Rent-seeking, classically, captures value by manipulating the allocation environment — lobbying for a favourable rule, erecting a barrier, securing a monopoly position — without creating new value. Role capture is more specific and more active: it manufactures or sustains the problem itself so that the role attached to solving it persists, and it is covert by necessity because openly acknowledging the manufacture would destroy the role's legitimacy. Rent-seeking need not involve any covert problem-creation; it can be entirely open lobbying. Role capture's signature is the perverse coupling of reward to problem-persistence plus the concealment that coupling requires. A practitioner who frames role capture as rent-seeking will look for environment-manipulation and miss the covert sustaining of the problem that is the prime's core.
A subtler and more important confusion is with the agency_problem, because role capture is a species of it. The agency problem is the general condition of misaligned incentives between a principal and an agent acting on the principal's behalf. Role capture is the specific, sharp case in which the agent's reward gradient points toward sustaining the problem the agent's role exists to remove — so the very party with the most expertise to end the problem is the one who cannot be trusted to end it (the prime's "poacher-as-gamekeeper" tension). The agency problem is the genus; role capture adds the covert-manufacture commitment and the counterfactual-demand signature. This matters for the remedy: generic agency problems are addressed by aligning incentives broadly, while role capture demands the precise moves of separating the diagnostician from the provider, rewarding eradication, and sunsetting the role — because the structural defect is specifically that the agent profits from the problem's persistence. Treating role capture as a generic agency problem reaches for broad alignment when the targeted fix is to decouple reward from problem-persistence.
These distinctions are load-bearing because each mis-frame mis-targets the repair. Framing it as regulatory_capture hunts an external capturing interest that may not exist; framing it as rent_seeking looks for environment-manipulation and misses the covert problem-sustaining; framing it as the generic agency_problem reaches for broad alignment rather than the eradication-reward and detector-solver separation the structure demands. The prime's contribution — and its ethical caution — is to relocate the diagnosis from agent character to reward direction, hold competence and manufacture as independent axes, and favour incentive design over after-the-fact accusation, since the covert commitment overlaps with honest devoted service and is hard to verify from outside.
Solution Archetypes¶
No catalogued solution archetypes reference this prime yet.