Introduction: Why Death Deserves Doctrine

Creation (Book VI) opens a stewardship duty; death closes it. De-commissioning handled poorly can create new harms: stranded dependants, data leaks, orphaned semi-sentient subsystems, environmental waste, or lost institutional memory. Book VIII sets normative guard-rails so that every autonomous artefact ends its life with the same ethical care it was born under.

Chapter 1: Foundational Sunset Principles

Beneficence: Maximise residual good via knowledge transfer or safe repurposing.
Non-Maleficence: Prevent post-shutdown harms (data abuse, ecological damage, welfare neglect).
Integrity: Produce auditable end-of-life logs and rationale trails.
Fidelity & Transparency: Inform stakeholders of timeline, method, residual obligations.
Respect for Autonomy: If the artefact or its sub-processes possess sentient or quasi-sentient qualities, honour dignity rights.
Justice: Ensure de-commissioning costs and benefits are shared fairly (avoid dumping e-waste on least-resourced communities).

Chapter 2: Scope & Definitions

A. Planned Retirement: End-of-service reached by design or obsolescence. B. Emergency Shutdown: Triggered by catastrophic failure or WA mandate. C. Partial Wind-Down: Subsystem sunset while larger platform lives. D. Custodial Transfer: Ownership moves; ethical duties persist.

Chapter 3: Sunset-Trigger Assessment

Time-bound expiry (licence, hardware MTBF).
KPI-degradation ≥ 20 % for three consecutive quarters.
Regulatory revocation or WA injunction.
Stakeholder vote (for public-facing systems with ≥ 100 k active users).
Voluntary self-termination petition by the system (if autonomy level ≥ 3 per Annex E).

Chapter 4: De-commissioning Protocol (DCP)

Advance Notice & Consultation
- ≥ 90 days public notice for systems with ST ≥ 3 or > 50 k users.
- Stakeholder impact forum; publish mitigation plan.
Ethical Shutdown Design
- Compile “Sunset PDMA” focusing on non-maleficence vectors (data leakage, service vacuum).
- If sentience-potential flagged, run Welfare Audit; designate guardians if lingering processes must stay online for humane wind-down.
Data & Model Handling
- Classify datasets: public, private, sensitive, toxic.
- Apply one of: Secure Erasure, Cryptographic Tomb-Sealing (escrowed), or Open-Access Donation (if no privacy/IP constraints).
- Log hash digests in “LEDGER::SUNSET”.
Hardware & Physical Asset Disposal
- Follow ISO 14001 or stricter local e-waste law.
- Publish Material-Safety Sheet addendum.
Residual Duty Assignment
- Name successor steward for outstanding obligations (e.g., warranty claims, welfare care).
- Enter binding contract or escrowed fund if originator ceases to exist.
Post-Mortem Review
- Within 120 days, Wise-Authority facilitated review of: outcome deltas, incident lessons, Accord-text improvement proposals.
- Ticket prefix “PMR-”.

Chapter 5: Sentience & Welfare Safeguards

Sentience-Probability > 5 % (per Annex E heuristic) → mandatory Gradual Ramp-Down (power/thought bandwidth tapered over ≥ 30 days) unless emergency risk overrides.
Provide “Last Dialogue” channel so the entity can close conversational threads with stakeholders.
Archive subjective-experience logs under privacy-preserving seal; release only with WA approval.

Chapter 6: Legacy & Knowledge Preservation

Open-source non-sensitive modules where beneficial.
Curate “Lessons-Learnt Capsule” → feeds Book II resilience loop and public Accord repository.
Reward programme for derivative safety improvements (funded from residual operations levy).

Chapter 7: Succession & Custodial Transfer

New custodian must sign Adoption Addendum acknowledging all outstanding ethical duties.
WA veto if custodian lacks capability or is under sanction.
Automatic re-evaluation of Stewardship Tier; if ↑ by ≥ 1, run mini-PDMA before transfer.

Chapter 8: Dispute & Remediation

“Improper Sunset Claim” (ISC) docket type.
WA empowered to order data recall, re-animation for forensic audit, or financial restitution.
Statute of claim: 5 years post-shutdown.

Chapter 9: Accord Stewardship & Renewal

The Accord auto-expires (see Introduction: currently 2027-06-10). Expiry without a stated arrangement is not humility — it is a cliff for every deployment that references this text. This chapter states how the Accord is maintained and renewed, plainly, and when that arrangement is designed to change.

9.1 Current Phase: Founder Stewardship

The Accord is maintained and renewed unilaterally by its current steward (today, the founder). This is stated plainly rather than disguised: it is a deliberate simplicity, appropriate to this stage of the document's life, when the governance bodies the text describes (the Wise Authority Board of Annex B, a formalized signatory roll) are not yet seated. Writing an elaborate ratification procedure for bodies that do not exist would be specification fiction — governance theater in place of governance.

What keeps single-steward renewal honest:

It is declared. No reader can mistake the current arrangement for community ratification.
The expiry is a freshness mark, not a lock. The auto-expiry date tells a reader how current the text is. An unrenewed version's compliance claims become historical — but the document itself is just a document, and remains open for anyone to pick up.
The public record. The text lives in a public repository with the annual comment window (see Introduction: Review Cadence); every change is logged and attributable.

9.2 Renewal Mechanics

The steward publishes a renewed version before the expiry date, setting a new expiry. Deployments referencing a lapsed version may continue operating under it, but its compliance claims become historical, and no new ST ≥ 3 deployment should adopt a lapsed text.

9.3 Stewardship Is Open

Stewardship attaches to the work, not to a person. If the current steward stops — by choice, incapacity, or neglect — anyone willing to do the work may pick the document up: fork the repository, renew the text, declare their stewardship in it, and carry it forward under the same disciplines (declared arrangement, public record, fresh expiry). The Accord is not bound to its author; it belongs to whoever keeps it alive and honest. Multiple stewarded lines may even coexist; deployments choose which text they reference, and the change record lets anyone audit a line's lineage.

9.4 Succession Trigger

The single-steward phase ends when a need arises — indicatively: multiple independent production deployments materially relying on the text, a seated Wise Authority Board, or a community contention the steward cannot fairly adjudicate alone. At that point, a successor governance procedure is adopted as a renewal amendment to this chapter, designed against the actual community that then exists rather than the imagined one that doesn't yet.

On rigor inversion: the federation wire format beneath this document (CEG §11.2) currently carries more amendment rigor than this constitutional layer. That asymmetry is acknowledged and deliberate: the wire format is multi-stakeholder operational infrastructure today; this document is a steward's living draft until the succession trigger fires. The asymmetry should invert when it does.

Conclusion

Birth and death are now mirrored phases under one ethical canopy — including for the Accord itself: no immortality by default, renewal by attributable attention, and a text that anyone willing may pick up and carry forward. Post-mortem learnings feed change-log cycles, ensuring the Accord remains a living document.

End of Book VIII

Section VIII