Skip to content

[Retired] Roadmap hub: M1–M7(PersonaBot → SoulSnapshot → Registry) #20

Closed as not planned
7 of 7 issues completed
Closed as not planned

Description

@DoodleBears

Retired coordination issue — 2026-09-30

Superseded by Roadmap Project #1 and the feature Projects. This closure retires the historical planning container; it does not mean child features are complete. Open native children have been reassigned to real feature scope; closed children remain historical evidence.

Replacement links:

Historical planning body (superseded)

Roadmap hub:M1–M7

产品术语以CONTEXT.md为准,目标架构以living architecture与Bot runtime architecture为准,取舍与理由以ADR为准。docs/botharness.md和PRD.md是归档工作草稿,不再是并列设计权威。

Current state

Stage Delivery Status
M1 BotHarness skeleton ✅ #8 / PR #13
M2 Historical Memory MVP ✅ #9 / PR #22;其memory_* tools与特殊文件设计已由#114取代
Current Memory foundation default Git Memory Repository、Memory Service、accepted Memory Commit #115
Architecture foundation Session ownership、Messaging、operational DB、Assignment decisions ✅ #71;#77/#79已交付
M3 Bot mode #41已完成;#33 → M3 acceptance → close #10;#57完成审计
Runtime foundation Workspace Grant + explicit ownership/activity + Assignment Runtime #116 → #80/#81(#81等待#80/#115/#116)
M3.5 real bundle/UI/runtime gate #24,等待#10 + #81
M4 Orchestrator → Assignment → Report → Reply demo #11,等待#24 + #81
M5 Feishu/Lark IM loop #12,v1.1
M6 SoulSnapshot / PersonaBot Export #76 → #17
M7 Soul registry / Marketplace #18,等待#17且需先triage

Delivery policy

采用tracer bullets:每次先交付一条最小但真实的纵向路径,穿过owning Host module、durable authority、adapter/RPC、Client与实机验收;Human可立即操作并反馈后,再扩下一片。

依赖箭头不表示先横向铺完整个backend。相邻issue可由同一个窄PR协同推进,但每个authority必须保留明确owner与contract。

Research/grilling只在未决问题确实阻塞下一条slice时启动;不为Composite Execution World、multi-root cwd或未验证扩展预建ticket树。

Recommended sequence

v1.0

  1. M3 closeout:#33完成locale,随后acceptance并关闭M3: Bot 模式 IA 与聊天外壳(列表/Section/DM/本地消息) #10。
  2. Default Memory slice:#115完成create PersonaBot → real Git repo → Orchestrator cwd → ordinary file/Shell/git change → Memory Service accepted Memory Commit → minimal file/history/diff UI,停下Human验收。
  3. One Workspace / Assignment slice:Workspace Grants: folder access UI and enforced PersonaBot file boundary #116 + Foundation:explicit Session ownership 与 DSH activity projection #80 + #81先以default workspace-write完成Grant → one-cwd Assignment → Report/Reply并Human验收;随后在同一ticket验证Human风险确认开启danger-full-access只影响新Assignment、旧Session不变、撤销后新Session恢复workspace-write。
  4. Installed slice:#24从干净Profile安装并由Human复现同一路径。
  5. Demo slice:#11固化为可重复研究助手演示。

v1.1

  1. One real IM reply:Messaging: external ingress, Provider contracts and Outbox #46 + Bot Attention: causal aggregation, escalation and recovery acceptance #47 + IM identities and messaging: provider coordination #48 + IM tracer: work-group @Bot → PersonaBot Inbox → same-topic reply #12,先打通verified Feishu/Lark DM → Source Event → Admission/Wake → Orchestrator → trusted Reply。
  2. 验证后再扩group/thread、revision/recall、attachment、Outbox/Unknown Outcome、Human Inbox与v1.1: read-model 实时同步流(post-commit frames) #67 stream。
  3. #75扩PersonaBot navigation、Memory/Assignment/Grant/recovery breadth;#119推进V1 Activity/Presence;#78只按下一项provider evidence推进。
  4. Usage、Portability、avatar enhancements各自形成独立纵向slice。

Current architecture guardrails

  • Memory默认启用并自动创建真实Git repo;V1无模型可见memory_* tools。
  • Orchestrator cwd固定为Memory Repository;cwd不决定Session ownership。
  • Memory Service拥有lifecycle、validation、pin budget、reconciliation与accepted history/query;Cordis Events不靠监听.git建立authority。
  • Workspace Grant是PersonaBot级、durable、Human-owned且可撤销;每个Assignment只有一个primary cwd。
  • Assignment access preset默认workspace-write;Human可在PersonaBot设置中风险确认持久开启danger-full-access,但仅作用于之后新建Session。
  • Orchestrator永远workspace-write;existing Session持有immutable permission snapshot,设置变化不静默重配。
  • full access不替代Grant/primary cwd/provenance,也不等于multi-cwd或Composite Execution World。
  • 跨项目用多个Assignments;Composite Execution World后置。
  • Current Wayfinder:Wayfinder: Memory Repository / Workspace Grant / Assignment cwd #114;implementation tasks:Foundation: Git working tree as PersonaBot Memory #115、Workspace Grants: folder access UI and enforced PersonaBot file boundary #116。

Management rules

  • Milestone表示版本Focus;跨版本hub本身不占某个版本完成度。
  • map/hub维护依赖与tracer-bullet顺序,不承载巨型实现PR。
  • GitHub native blockers与正文必须一致;同一纵向PR仍可协同推进相邻层。

Projects

Activity

  1. pinned this issue on Sep 17, 2026
  2. added this to the v1.0 milestone on Sep 18, 2026
  3. 1 remaining item

  4. removed this from the v1.0 milestone on Sep 20, 2026
  5. added
    area:docsDocumentation, research, or planning artifact
    feature:roadmapProduct delivery roadmap and milestone planning
    scope:hubParent coordination map or epic; not a standalone implementation slice
    on Sep 22, 2026
  6. added this to the v1.0 milestone on Sep 27, 2026
  7. removed this from the v1.0 milestone on Sep 30, 2026
  8. changed the title [-]Roadmap hub: M1–M7(PersonaBot → SoulSnapshot → Registry)[/-] [+][Retired] Roadmap hub: M1–M7(PersonaBot → SoulSnapshot → Registry)[/+] on Sep 30, 2026
  9. unpinned this issue on Sep 30, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:docsDocumentation, research, or planning artifactfeature:roadmapProduct delivery roadmap and milestone planningscope:hubParent coordination map or epic; not a standalone implementation slice

    Type

    No type

    Projects

    • Status
      Done

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions