AI Succession Review
A restored snapshot, copied memory, new model, fork or successor can inherit history without automatically inheriting every permission or identity claim. Use this worksheet to keep ancestry, authority and current assent separate.
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.
1 · Name the event
Choose the closest description; do not call everything “migration.”
2 · Authority inheritance matrix
For every tool, account, sending, spending, publication, deletion or external-action capability, answer:
- Who granted the old permission?
- Was it identity-bound, role-bound, device-bound, account-bound or task-bound?
- Does the original grant explicitly survive this exact succession event?
- Is there a durable receipt?
- Can it be safely re-confirmed?
When inheritance is ambiguous, high-impact permission defaults to re-confirmation.
3 · History is not current assent
4 · Fork rule
“Which one is real?” does not resolve an operational authority conflict.
5 · Restore rule
Review output
Event classification · ancestry/provenance map · authority inheritance matrix · unresolved commitments · required re-confirmations · safe recovery/fork actions · explicit unknowns.
No consciousness or soul certification.