[Retired] Post-M4: Messaging / Bot Inbox / Orchestrator / Assignments #30

Purpose

v1.1 Messaging / Bot Inbox / Orchestrator / Assignments产品树的umbrella。它维护架构边界、依赖与tracer-bullet顺序，不承载巨型实现PR。Memory / Workspace / Assignment cwd的当前边界由#114负责，本map只引用，不复制第二套设计。

Locked architecture

• Source Event是唯一social content authority；Channel placement与Inbox Admission只保存关系和引用。
• botharness.db是profile-scoped operational authority；调用方只能通过owning deep module commands/queries操作。
• Provider adapter只负责verified normalization、Capability declaration与side-effect execution，不拥有Inbox、Trigger、authorization或Channel truth。
• 每个PersonaBot最多一个active Orchestrator；Assignment Session是independent DSH root；Subagent只属于其内部delegation。
• Chat是DM Channel的Human-facing surface，不是第三种Session；执行层只有Orchestrator与Assignment两种Bot-mode root role。
• DM-only PersonaBot navigation显示Chat、Memory与subordinate Assignments；Orchestrator不显示为Assignment row，group Channel无此导航。
• Memory默认启用并自动创建真实Git repo；Orchestrator cwd固定到repo；V1用普通file/Shell/grep/git，不暴露memory_* model tools。
• Memory Service拥有validation/reconciliation与accepted Memory Commit history/query；Cordis Event不通过监听.git充当authority。
• project access只通过PersonaBot级durable Workspace Grant；每个Assignment一个cwd；Composite Execution World后置。
• Reply使用trusted Reply Route；主动provider action需要Capability + Human Service Grant。
• SQLite/DSH/provider边界使用minimal intents、stable ids与bounded reconciliation，不宣称exactly-once。

Foundation status

• ✅ 架构地基：显式 Session 归属与 deep modules（GrokBot-on-DSH 对齐） #71 ownership/Messaging architecture foundation。
• ✅ Spike：验证 BotWork 所需 DSH Agent / SessionPersistence / Subagent seams #77 DSH Agent/SessionPersistence/Subagent seam validation。
• ✅ Foundation：operational database owner / writer lease / schema generation #79 operational database owner。
• Current Memory/Workspace map：Wayfinder: Memory Repository / Workspace Grant / Assignment cwd #114；tasks：Foundation: Git working tree as PersonaBot Memory #115、Workspace Grants: folder access UI and enforced PersonaBot file boundary #116。
• v1.0 foundation：Foundation：explicit Session ownership 与 DSH activity projection #80 explicit ownership/activity；Foundation：Assignment Runtime / Assignment Directory / Orchestrator tools #81 Assignment Runtime。

Tracer-bullet delivery

Slice 0 — default Memory + one Workspace

#115：create PersonaBot → Git repo → Orchestrator cwd → ordinary file/git change → accepted Memory Commit → minimal Human file/history/diff。

#116：grant one Workspace once → reuse acrossAssignments → revoke → new create/request/resume/wake fail closed。

Slice 1 — local Assignment loop

#80/#81/#24/#11协同：DM Source Event/Inbox → Orchestrator in Memory repo → one independent Assignment with one granted Workspace cwd → Assignment Report → same-DM reply → visible list/detail → restart recovery。首个增量Human验收后再扩capacity、pagination、repair与fault matrix。

Slice 2 — one external reply

#46/#47/#48/#12协同：verified Feishu/Lark DM → Messaging command → Source Event + Admission → Wake/Orchestrator → trusted Reply Route。先让Human收到一条真实回复。

Slice 3 — reliability and breadth

扩group/thread、edit/recall/replay、Provider Echo、attachments、Service Grant、Outbox reconciliation、Unknown Outcome、Human Inbox与#67 post-commit stream。

Supporting tickets

• Messaging: external ingress, Provider contracts and Outbox #46 Messaging deep module与provider-neutral seams。
• Bot Attention: causal aggregation, escalation and recovery acceptance #47 Bot Inbox、Wake/Delivery、Orchestrator coordination 与 durable Attention facts，等待 Foundation：Assignment Runtime / Assignment Directory / Orchestrator tools #81；不拥有 Human Inbox aggregate UI。
• IM identities and messaging: provider coordination #48 是 External Messaging Provider coordination parent；IM tracer: dsh-im outbound adapter and explicit Bot binding #117 交付 outbound-first dsh-im adapter，IM tracer: work-group @Bot → PersonaBot Inbox → same-topic reply #12 在 Bot Attention: causal aggregation, escalation and recovery acceptance #47/Research：Feishu/Lark Messaging provider contract（events / capabilities / identity） #78/IM tracer: dsh-im outbound adapter and explicit Bot binding #117 后交付首个真实 inbound DM。
• Spec: Human Inbox unread, personal attention and actions #126 从已交付的 Human Inbox action/info projection 扩展个人 Group 未读、Human 提及／回复与卡片内回应；Tracer: Activity Center Overview shows Bot status and active Sessions #541 独立交付活动中心总览，Tracer: Human @所有 Bot mentions current Group members #542 交付 Human 在当前 Group 的 @所有 Bot 快捷输入。
• 设计：PersonaBot navigation / Assignments / recovery 的 DSH-native UI #75 PersonaBot navigation / Memory / Assignments / Grant / recovery breadth。
• #78只按下一项provider behavior需要推进。

Current dependency order

• Foundation: Git working tree as PersonaBot Memory #115 + Workspace Grants: folder access UI and enforced PersonaBot file boundary #116 + Foundation：explicit Session ownership 与 DSH activity projection #80 → Foundation：Assignment Runtime / Assignment Directory / Orchestrator tools #81。
• Foundation：Assignment Runtime / Assignment Directory / Orchestrator tools #81 → M3.5: 本地安装验证门（DSH 实机 + 插件 UI 冒烟） #24/M4: 演示闭环（Orchestrator → Assignment → Report → Reply） #11/Bot Attention: causal aggregation, escalation and recovery acceptance #47。
• #46可与v1.0 runtime slice并行；#47等待Foundation：Assignment Runtime / Assignment Directory / Orchestrator tools #81。
• IM tracer: dsh-im outbound adapter and explicit Bot binding #117 等待 Messaging: external ingress, Provider contracts and Outbox #46，先交付 outbound-first dsh-im adapter。
• IM tracer: work-group @Bot → PersonaBot Inbox → same-topic reply #12 等待 Bot Attention: causal aggregation, escalation and recovery acceptance #47 + Research：Feishu/Lark Messaging provider contract（events / capabilities / identity） #78 + IM tracer: dsh-im outbound adapter and explicit Bot binding #117，交付第一条真实 Feishu/Lark inbound DM；IM identities and messaging: provider coordination #48 作为 parent 不再充当粗粒度 blocker。
• Spec: Human Inbox unread, personal attention and actions #126 下一条 tracer：本地 Human 的 Group 未读汇总 → 准确来源定位 → 已读；Tracer: Activity Center Overview shows Bot status and active Sessions #541 先交付行动数、Bot 状态和活跃 Session，后续统计复用 Wayfinder: per-PersonaBot 费用与用量可见性 #34/Usage read model / Typert remote / Profile contract #39/Group Profile：群活跃与成员活跃（按消息数） #424；Tracer: Human @所有 Bot mentions current Group members #542 沿用既有逐 Bot 直接提及与 Wake Policy。v1.1: read-model 实时同步流（post-commit frames） #67 等待 Messaging: external ingress, Provider contracts and Outbox #46 + Foundation：explicit Session ownership 与 DSH activity projection #80，且不阻塞 V1 PersonaBot-only stream Bot activity: revisioned live sync and reconnect #121。

References

• Wayfinder: Memory Repository / Workspace Grant / Assignment cwd #114、Foundation: Git working tree as PersonaBot Memory #115、Workspace Grants: folder access UI and enforced PersonaBot file boundary #116
• CONTEXT.md
• docs/architecture/botharness-architecture.md
• docs/architecture/bot-runtime-architecture.md
• ADR-0024/0025/0026、0035～0039、0041、0045

Published dsh-im provider spec

• IM tracer: dsh-im outbound adapter and explicit Bot binding #117 is the outbound-first dsh-im Provider Adapter tracer.
• Order: Messaging: external ingress, Provider contracts and Outbox #46 provider-neutral authority → IM tracer: dsh-im outbound adapter and explicit Bot binding #117 outbound adapter; in parallel Foundation：Assignment Runtime / Assignment Directory / Orchestrator tools #81 → Bot Attention: causal aggregation, escalation and recovery acceptance #47 and Research：Feishu/Lark Messaging provider contract（events / capabilities / identity） #78 supplies minimum provider evidence; then IM tracer: work-group @Bot → PersonaBot Inbox → same-topic reply #12 owns the real Feishu/Lark inbound DM acceptance.