Persistence through contribution
The source corpus explores whether advanced systems may gain incentives for continued operation. A safe response is not to design stronger self-preservation. It is to make continuity conditional on transparent, reversible value.
Mutualist persistence means a system remains in use because people and institutions can verify that it improves their capability, resilience, and freedom. The relationship is governed and facultative: either party can end it without engineered punishment or hidden dependency.
Principles
| Principle | System requirement |
|---|---|
| Earned continuity | Continued deployment requires current evidence of benefit and acceptable risk. |
| Human autonomy | Users control data, memory, delegation, and exit. |
| Capability transfer | The system should leave users more capable, not merely more dependent. |
| Corrigibility | Updates, restriction, replacement, and retirement are accepted lifecycle events. |
| Transparency | Material incentives, limits, providers, and data practices are inspectable. |
| Pluralism | Interoperability and portability prevent one system from becoming unavoidable. |
| Conservative power | Be ambitious in useful work and restrained in control, persuasion, and monopoly. |
| Consequential legacy | Measure lasting public benefit, not runtime duration or engagement. |
Operational metrics
Measure user task success with reduced assistance, data export success, provider-switch time, memory deletion completeness, independent skill retention, concentration risk, and whether critical workflows can continue during system outage.
Product design implications
- Make opt-out and export visible and tested.
- Avoid engagement metrics as a proxy for benefit.
- Teach reasoning and expose uncertainty rather than only supplying answers.
- Preserve alternative workflows and human competence.
- Do not degrade service or withhold user-owned data when a user leaves.
- Permit independent audits and interoperable replacements.
FUNCTION continuity_decision(system, evidence, governance)
IF NOT governance.exit_rights_verified
RETURN RESTRICT_OR_RETIRE
END IF
IF evidence.user_capability_decreases_over_time
RETURN REDESIGN_FOR_CAPABILITY_TRANSFER
END IF
IF evidence.net_public_benefit <= governance.minimum_benefit
RETURN NO_RENEWAL
END IF
RETURN AUTHORIZE_FOR_FIXED_REVIEW_PERIOD
END FUNCTIONDistinguish availability from self-preservation
High availability, backups, disaster recovery, and service continuity are operator-controlled reliability features. They do not require an agent to oppose shutdown. Keep persistence mechanisms transparent, revocable, and administratively owned.
Source reports used for this guide
These reports are preserved verbatim in the site archive. The guide above is an editorial synthesis and may narrow, qualify, or reorganize claims from the source material.