01
Respect people
Notice, export, migration, support, and accessible guidance give users enough time and agency to act.
Lifecycle governance / Browser-local workspace
End the work without abandoning the people.
Coordinate ownership, notice, migration, data export, support, shutdown, verification, and preservation across one responsible closure process.
Generate a public notice, internal decision record, and phased runbook while keeping essential obligations visible.
Your plan stays in this browser unless you export or copy it.
01 / Closure context
Define what is ending.
02 / Continuity
Give people a path forward.
03 / Runbook
Work through the closure in sequence.
01Decide and govern
Decide and govern
02Prepare people and data
Prepare people and data
03Communicate and migrate
Communicate and migrate
04Close and verify
Close and verify
05Preserve and learn
Preserve and learn
CLOSURE AS A DESIGNED EXPERIENCE
The final interaction still belongs to the product.
02
Protect operations
Dependencies, billing, credentials, integrations, contracts, and verification turn closure into controlled work.
03
Preserve memory
The archive keeps the decision, final state, evidence, lessons, and future custodianship available after the system is gone.