ADR 0002: deployment-key rotation — rotate, drain, verify, discard (#349) #408
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "adr-349"
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?
Records the #349 decision per the operator's bounded-keys direction: no growing keychain — keep the two-key shape (active + one retiring) and make rotation completable via a managed drain (background re-encrypt through the normal write pipeline), verification (#348's header scan reaching zero coverage), then discard. Adds a public-halves-only drain ledger in the state store with a refuse-to-boot tripwire replacing today's silent orphaning, confirms mixed-flavour decrypt windows are legal, and rejects header-surgery rewrap with reasoning (S3 IO cost identical, trust-surface, flavour homogeneity, PQ synergy). Docs only.