docs(handbook): frame the classical→post-quantum live migration (#110) #208
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "docs-pq-migration"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Adds one customer-facing framing paragraph to the Post-quantum mode section of
docs/handbook/encryption.md, right before the existing "Facts to know" list.Makes explicit what the surrounding bullets only imply: instances are classical by default, so the common real-world path is to migrate a running, populated instance to post-quantum later — and that migration is live and lossless (classical key retained in
recoveryIdentityLegacy, upgrade-on-touch, new writes PQ, safe rollback). Starting classical, by choice or by oversight, is never a dead end. Confirmed end-to-end by the #110 sovereignty proof (pre-migration object opens with the classical key; post-migration object only with the hybrid).Non-redundant: it frames and points to the existing Migration is automatic / Rollback is safe notes and the migration checklist rather than restating them. Product-neutral. Spliced in by a self-removed one-shot workflow; existing content untouched.