Repository navigation
Description
Remaining Profile portability scope — reconciled 2026-09-30
This issue owns identity-preserving Profile Backup, Managed Restore, Profile Transfer and Disaster Restore UX. PersonaBot public sharing/export/import lives in #17/#18 and its feature Project; it is not blocked on the full Profile backup design.
- Export Profile to one .botharness-backup; Import Profile from one file.
- Restore As New / Replace Existing, staging validation and explicit confirmation.
- Readiness/rebind/activation checklist, unavailable Workspace and provider fingerprint mismatch.
- Transferred Out and Disaster Restore behavior; Session facets omitted/unsupported and sensitive operational facets.
- Keep a concise explanation of clone sharing versus identity-preserving Profile operations; do not duplicate Tracer: publish a Memory Git repo and import through a Bot link #17's selector/publisher UX.
Remaining deliverables
- Minimal Profile user flow and error/confirmation matrix.
- Backup/Restore/Transfer copy, information hierarchy and size/validation presentation.
- DSH Settings/Plugin surface and Host RPC requirements.
- Narrow Profile implementation slices after the design is accepted.
References: ADR-0040–0044, current living architecture. No scheduler, retention catalog or incremental backup chain.
Historical scope before 2026-09-30 reconciliation (superseded where inconsistent)
Why
#71 已确定 PersonaBot Export、单文件 Profile Backup、Managed Restore、Profile Transfer、Disaster Restore 与 dependency rebind 的业务语义,但尚未把它们整理成 Human 能理解的最小操作流程。
Scope
- PersonaBot Export/Import(clone)与 Profile Backup/Managed Restore(保留 identity)的清晰区分。
- 仅两个基础动作:Export Profile → 一个
.botharness-backup;Import Profile ← 一个文件。 - Restore As New / Replace Existing、手动备份提示、staging validation、readiness/rebind/activation checklist。
- Session facet omitted/unsupported、Unavailable Workspace、provider fingerprint mismatch、Transferred Out、Disaster Restore 的说明与恢复路径。
- 敏感 operational facets、估算大小、结构校验失败的呈现。
Deliverables
- 最小用户流程与错误/确认矩阵。
- PersonaBot Export、Profile Backup、Transfer 三条路径的文案和信息层级。
- DSH Settings/插件页 slot 与 Host RPC 需求。
- 拆出 PersonaBot Export 与 Profile Backup/Restore 的独立实现票。
Related
- Architecture foundation: 架构地基:显式 Session 归属与 deep modules(GrokBot-on-DSH 对齐) #71
- SoulSnapshot / PersonaBot Export: Tracer: publish a Memory Git repo and import through a Bot link #17
- ADR-0040~0044
Non-goals
- 不增加 scheduler、backup catalog、retention、增量链或自动备份。
Accepted design and implementation handoff — 2026-10-05
Human accepted PR #881; verified head passed full CI and merged as 43fe4b6b3df707bdacd172180c68bfee129e3451. Implementation is coordinated in native child hub #882, with #883/#884/#885 canonical-owner slices and #886 complete-core round trip. Each runtime PR requires real DSH evidence and its own Human QA. This design issue does not claim runtime backup/restore delivery; #505 remains blocked on production portability and sharing contracts.
Metadata
Metadata
Assignees
Labels
Type
Projects
- StatusShow more project fieldsDone
Activity
[-]设计:PersonaBot Export / Profile Backup / Restore / Transfer UX[/-][+]Design: Profile Backup / Restore / Transfer UX[/+]DoodleBears commentedon Oct 5, 2026
Agent work claim
codex/local/01a0f25f-2150-75e3-8895-23d35394b8d8(not a DSH Session)codex/76-profile-portability-design#325 / PR #879 are merged and completed. #76 has no existing claim, assignee or open PR at preflight. Implementation slices will be published only after Human accepts this design.
docs: clarify sensitive backup data and transfer cancellation
DoodleBears commentedon Oct 5, 2026
Agent work outcome — paused for Human acceptance
codex/local/01a0f25f-2150-75e3-8895-23d35394b8d8(not a DSH Session)3b2dd92a69df434bc94bad2a57949db807d9fa36Human acceptance should confirm complete-core/private-data disclosure, identity-preserving new versus stopped-target replacement, explicit readiness/authorization repair, Transferred out and cancellation/disaster-recovery posture. No implementation tickets have been published. After design acceptance, publish narrow implementation slices and continue real DSH E2E with screenshot/recording and per-PR Human QA. #76 stays open until that handoff; #505 remains blocked on production full Backup/Restore and its other contracts. No #272 Windows acceptance or additional merge is claimed.
docs: propose Profile backup, restore and transfer UX (#881)
DoodleBears commentedon Oct 5, 2026
Agent work outcome — completed design handoff
codex/local/01a0f25f-2150-75e3-8895-23d35394b8d8(not a DSH Session)