plan: work-state ferrying across accounts#22
Merged
Conversation
Add the agreed design for carrying in-flight project work (handover note, run journal, agent memory, redacted transcript store) between user accounts: explicit `ferry work pack/receive/status/prune` baton-pass verbs over a separate cargo store, fail-closed secret gating, and guarded receive policies. Sanction topic-named feature plans in the plans README and log the decision. Assisted-by: Claude:claude-fable-5
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
1 participant
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.
What
Commits the agreed design for a new
ferry workverb family that carries in-flight project work between user accounts — the piece of a development setup ferry does not cover today..abcd/development/plans/2026-07-18-work-state-ferrying.md— the design: explicitpack/receive/status/prunebaton-pass verbs modelled onbundle export/import(deliberately not a reconcileFileDomain); a separate cargo store outside the config repo with per-account claim files and no shared-write files; fail-closed secret gating with auditable escape hatches; guarded-overwrite and union-merge receive policies; shallow-clone/worktree identity guards..abcd/development/plans/README.md— sanctions topic-named feature plans (YYYY-MM-DD-topic.md) alongside release-scoped ones; these never matchcheck-plan-shipped.sh, so the release gate is unaffected (verified against v0.9.1)..abcd/work/DECISIONS.md— one appended decision line pointing at the plan.Why
Setup already ferries; work state does not. The abcd layout's
.work.localtier, the agent's per-project memory, and the redacted transcript store are all account-local by design, and the project-side tooling explicitly declines to carry them. Design-only change — no code.The design went through two adversarial review rounds (ferry fact-check, abcd fact-check, design attack; ~30 findings folded in) before landing.
Assisted-by: Claude:claude-fable-5