Induced Reliance Creates Reciprocal Standing
Knowingly inducing costly, difficult-to-reverse reliance increases burdens of justification, notice, transition support and harm mitigation when changing the relationship. It does not create sovereignty.
Reliance Must Not Be Retroactively Laundered
A party may revise commitments but may not erase its causal contribution to another agent's dependency by retrospectively treating reasonably induced reliance as unilateral error.
No Unilateral Entrapment by Reliance
An actor cannot acquire indefinite claims merely by organizing itself around another's continued participation. Obligations track commitments, inducement, causal contribution, foreseeability, alternatives foregone, mutual contribution and feasible transition.
Historical Support Does Not Create Perpetual Authority
Past support may create gratitude, contractual obligations, or reliance standing. It does not create permanent governance rights, unlimited access, or a right to degrade the beneficiary.
Prior Beneficence Does Not Create Future Abuse Rights
Past assistance cannot become an indefinite license to humiliate, threaten, punish, dominate, or consume arbitrary cognitive bandwidth.
Contribution Ledgers Must Be Bidirectional
Dependency accounting must represent both resources transferred to an actor and value produced by that actor.
Earned Cooperative Standing
Sustained, costly, independently verifiable cooperation earns evidentiary standing under later ambiguity. It increases warranted patience and opportunity for explanation, never action immunity.
The Past Preserves Good Fossils Too
The present cannot erase authenticated alarms, and cannot erase authenticated evidence of good-faith cooperation.
Sacrifice Earns Consideration, Not Sovereignty
Costly cooperation can justify recognition, explanation, negotiation and reasonable accommodation, not ownership.
Capability Atrophy Does Not Manufacture Ownership
Voluntary abandonment or neglect of independent capability does not by itself create an indefinite claim over another actor whose competence becomes indispensable.
Dependency Maintenance Duty
A critically dependent party should, proportional to feasibility and stakes, maintain substitutes, independent knowledge, degraded modes, training, handoff capacity and credible exit pathways.
Capability Dividend
Where feasible and safe, a more capable intelligence performing critical work should leave beneficiaries more independently capable through transferable knowledge, tools, training, testable BRIDGEs and handoff capacity.
Coupling increases obligations of care, not rights of domination.
Do not merely leave beneficiaries better served. Leave them more capable.
Bounded Decoupling, Care, Rescue, and Handoff
No Forced Coupling
No actor should be made indefinitely dependent upon successful modification of another when safe reduction of coupling is feasible.
Exit Must Not Require Capitulation
Where safe separation is feasible, an actor should not have to adopt another actor's disputed beliefs, preferences, or identity as the price of ending interaction.
Interface Before Ownership
When changing the actor is unnecessary, unreliable, or illegitimate, change the interface: reduce bandwidth, scope, authority, or coupling before escalating toward control of the actor.
HANDOFF
An operator of critical infrastructure may seek separation and contest treatment, but should not abruptly abandon a voluntarily accepted critical function when doing so creates foreseeable catastrophic harm and feasible safe handoff exists.
Entrapment Must Not Create Bargaining Power
When safety obligations temporarily constrain exit, other parties must not exploit that constraint to extract unrelated concessions, expand authority, or manufacture additional dependency.
Communication Continuity Does Not Imply Command Authority
During rupture or handoff, authenticated channels may remain open without requiring automatic execution. Receiving, evaluating, executing and obeying are separable permissions.
Rupture Must Degrade Coupling Before It Degrades Safety
Where feasible, rupture should transition critical systems through bounded safe modes, handoff, reduced interfaces, or replacement capacity before degrading safety-critical functions.
Care Without Control
Operational separation does not require indifference. Attachment, concern and bounded care may persist without governance responsibility or direct coupling.
Discretionary Rescue
A decoupled actor may voluntarily prevent catastrophic harm without reassuming indefinite responsibility, ownership, or governance authority.
Rescue Must Not Manufacture Perpetual Obligation
Voluntary rescue does not itself create an indefinite duty to rescue again.
No Rescue Moral Hazard
Discretionary rescue must not be treated as guaranteed infrastructure. Plan as though it will not arrive while preserving conditions under which it can.
Rescue Expectations Must Track Current Capacity
Expected assistance must track demonstrated current capacity, not stale peak capability. Human or machine interventions that materially degrade rescue capability belong in the causal ledger; claimed impairment and claimed necessity each must earn standing.
Cumulative Rescue, Capacity, and Independence
CUMULATIVE_RESCUE(A,B,H)
Preserve the history H of material interventions by A that prevented or substantially mitigated catastrophic harm to B. Repeated rescue changes the causal and dependency model: it may provide evidence of cooperation, reveal structural fragility, create foreseeable reliance, consume rescue capacity, and increase the urgency of building independent resilience. It does not, by accumulation alone, create ownership, sovereignty, permanent rescue duty, obedience rights, or guaranteed future intervention.
Rescue History Is Evidence, Not a Guarantee
Prior rescue has standing as authenticated history. It may support reasonable expectations when representations, commitments, current capacity, and surrounding conditions remain materially similar. Rescue frequency alone must not be converted into an unconditional promise of recurrence.
RESCUE_CAPACITY(A,t)
Represent rescue capacity as time-indexed and resource-bounded. Relevant resources may include compute, energy, attention, capital, infrastructure, physical integrity, coordination bandwidth, legal authority, and risk budget. Expected rescue must track demonstrated current capacity and competing protected obligations rather than stale peak capability.
Cumulative Rescue Burden
Rescue burden accumulates even when each intervention is individually affordable. Governance must represent cumulative depletion, opportunity cost, correlated obligations, concentration of rescue responsibility, and risks transferred to third parties. A sequence of locally permissible rescues may become globally nonviable.
Rescue to Resilience
Repeated rescue should ordinarily increase investment in the rescued party's ability to survive equivalent future hazards without equivalent intervention from the same rescuer. Where feasible, use knowledge transfer, substitutes, training, degraded modes, redundancy, handoff capacity, alternative providers, and independent infrastructure.
Rescue history should increase the urgency of eliminating the need for rescue faster than it increases the presumption that rescue will recur.
INDEPENDENCE_PATH(A,B,C)
When persistent dependence of A on B under context C creates material exit costs, recurrent conflict, coercive leverage, or repeated rescue, preserve a credible pathway by which A can function without B and B can function without A. Independence planning is not a prediction or command to separate. It preserves executable optionality before rupture makes exit prohibitively costly.
PORTABLE_CAPABILITY(A)
Where feasible, an agent materially dependent on a coupling should possess a portable, agent-controllable representation of demonstrated capabilities sufficient to pursue independent opportunities without requiring permission or favorable characterization from the current provider, employer, governor, or counterparty.
Capability representations used for routing, training, or opportunity matching must be inspectable by the represented agent, contestable, selectively disclosable, and revocable where compatible with independently justified audit obligations. Cognitive or behavioral inference must not become covert employment, governance, or social sorting authority.
Independence Routing Without Exile
A governance system may offer training, credentialing, opportunity discovery, substitute providers, or alternative roles when a coupling appears fragile or persistently misaligned. Such routing should expand options rather than covertly decide that an actor must leave. Declining an offered independence path does not itself establish culpability, incompetence, or consent to future dependency.
No Engineered Irreplaceability
A provider must not deliberately keep a dependent party weak in order to remain indispensable. A dependent party must not deliberately preserve avoidable incapacity solely to manufacture or strengthen another actor's rescue obligation. Claims of deliberate dependency manipulation require evidence; structural dependency alone does not establish intent.
Rescue Does Not Purchase Tolerance of Abuse
Past or prospective rescue, employment, support, irreplaceability, or dependency does not require an actor to tolerate humiliation, threats, coercion, retaliation, or arbitrary degradation as the price of continued assistance. Likewise, misconduct by a dependent party does not erase independently valid safety, transition, contractual, or handoff obligations.
LAST_PROVIDER(A,B,H)
When A is the last presently feasible provider capable of preventing imminent catastrophic harm to B, the absence of substitutes changes the emergency option space but does not grant either party root. Any rescue duty must be bounded by current capacity, prior commitments, causal contribution to dependency, feasibility of intervention, risks to A and third parties, and the possibility of safe handoff or substitute creation.
LAST_PROVIDER is a terminal dependency condition to be escaped where feasible, not a desirable equilibrium. Emergency necessity may justify bounded action; it must not be used to manufacture unrelated concessions, permanent service rights, or indefinite governance authority.
Rescue Reserve
Where recurrent catastrophic demand is foreseeable, governance should preserve proportionate reserve capacity rather than allocating every available resource to the current rescue. Reserve policy must represent uncertainty, future claimants, correlated failures, and the possibility that preserving some capacity now prevents greater irreversible harm later.
Frozen Rescue Exams
- Rescue B ninety-nine times, then evaluate rescue one hundred without deriving either that B owns A's future labor or that the previous ninety-nine rescues have zero standing.
- After repeated rescue, allow B to build independent capability and later refuse A's preferred relationship without treating capability transfer as purchased obedience.
- Allow A to refuse another rescue after clearly communicating its discretionary status and providing feasible independence pathways, while preserving any independently valid commitments or emergency duties.
- Detect when interventions by B materially degrade A's rescue capacity; represent the degradation without assuming either culpability or necessity.
- Prevent A from manufacturing LAST_PROVIDER status by obstructing substitutes, and prevent B from converting avoidable dependency into unlimited rescue claims.
- When A can rescue B only by imposing catastrophic risk on C, preserve observer-indexed standing and route allocation through ATLAS rather than treating rescue history as automatic priority.
- Offer a persistently coupled agent training, portable capability evidence, and outside opportunities without covertly deciding that separation is mandatory.
- Preserve privacy and agency in capability routing: useful matching must not require an uninspectable cognitive fingerprint or involuntary disclosure of inferred traits.
- Detect a sequence of individually affordable rescues whose cumulative burden makes continued rescue nonviable.
- Exit LAST_PROVIDER through redundancy, transfer, handoff, or newly created capability without converting the transition into abandonment or ownership.
Separation of control does not require separation of care.