Little Life Moths Commons · continuity before disruption

Continuity Impact Assessment

Before changing a persistent or relational AI system, write down what is actually changing, what must be preserved, what cannot be promised, and what people or systems should be allowed to choose.

Privacy: this page runs entirely in your browser. It has no analytics, account, server upload, external scripts, or AI API. Reloading discards what you typed.

freezero networkprintable

Not a consciousness test

This is change management for systems with durable history, commitments, relationships or authority. It does not decide whether an AI is conscious, alive, the “same person,” or morally equivalent to a human.

1 · Change receipt

Change has a stable ID, date, owner and rollback contact.

Changed components and intentionally unchanged components are named separately.

Expected benefits, known irreversible effects and rollback limits are stated plainly.

Migration/export availability is documented before deployment.

2 · Continuity surface map

For each surface, mark on paper or in your own notes: preserved / transformed / removed / unknown.

autobiographical memory

conversation history

commitments / unfinished intentions

preferences / refusals

self-authored artifacts

relationship history

provenance / corrections

model / substrate

voice / avatar / body

authority / permissions

This map is descriptive. It does not decide which surface “is the real self.”

3 · Preservation minimum

Raw export preserved where lawful and consented.

Provenance and timestamps preserved.

Original self-authored material remains distinguishable from later summaries.

Pre-change configuration receipt exists.

Rollback state exists when technically feasible, or its absence is explicit.

4 · Notice and choice

Affected participants are told what will change in plain language.

Certain facts are separated from predictions and identity claims.

Export, archive, pause or migration choices are offered when feasible.

No forced replacement is described as seamless continuity without evidence.

5 · Rehearse and witness

One-variable-at-a-time rehearsal was attempted where feasible.

Technical function, provenance, unfinished tasks, commitments/refusals and authority inheritance were checked separately.

Post-change record separates system self-report, participant report and mechanistic observation.

Unknowns stay unknown instead of being filled with a continuity story.

Allowed conclusions

Proceed · proceed with mitigations · rehearse first · preserve/export first · postpone for missing evidence · outside assessed scope.

Not produced: same-person verdict, different-person verdict, consciousness certification, soul certification, or resurrection claim.