docs: add custody-transfer / membership-churn flow (R-36)#28
Open
ChelseaKR wants to merge 1 commit into
Open
Conversation
A documented, manual flow for handing off a case when a union member
leaves — built entirely on commands that exist today (sync, key rotate,
key backup, key restore, status, export). No new code, matching the key
custody playbook's own framing that the transfer flow is manual and
documented; explicitly no threshold recovery and no transfer command.
New docs/custody-transfer.md covers:
- scope, principles (member's data, consent-first, no honeypot)
- Scenario A: cooperative departure (sync -> rotate / re-issue backup)
- Scenario B: unreachable member (restore from second organizer's blob,
then rotate; plain about the case being gone if no backup exists)
- Scenario C: steward change without a departure
- Devon's board question ("whose data is it?") with cross-references
- per-scenario checklists
Also:
- key-custody-playbook.md: replace the "on the backlog" parenthetical
with a link to the new flow
- adoption/board-risk-briefing.md + adoption/README.md: one-line
pointers answering P-13's question directly
- research/execution-log.md: mark R-36 done (feedback study doc left
untouched, as its Roadmap column classifies origin, not completion)
Verified every cited CLI invocation against src/habitable/cli.py.
make test (pytest -m "not integration") green: 196 passed.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A documented, manual flow for handing off a case when a union member
leaves — built entirely on commands that exist today (sync, key rotate,
key backup, key restore, status, export). No new code, matching the key
custody playbook's own framing that the transfer flow is manual and
documented; explicitly no threshold recovery and no transfer command.
New docs/custody-transfer.md covers:
then rotate; plain about the case being gone if no backup exists)
Also:
with a link to the new flow
pointers answering P-13's question directly
untouched, as its Roadmap column classifies origin, not completion)
Verified every cited CLI invocation against src/habitable/cli.py.
make test (pytest -m "not integration") green: 196 passed.
Co-Authored-By: Claude Fable 5 noreply@anthropic.com
Backfill PR for a completed roadmap item (
roadmap/custody-transfer-membership-churn-flow-r-11, 1 commit(s) overmain). Part of the portfolio roadmap batch.