公开进度摘要

用一页看懂 Roadmap 顺序和 implementation 状态。

Mycel 目前仍处在窄版 first-client lane。`M2` 在当前窄版 replay/storage/rebuild 范围内已经完成收口, 因为 richer mixed content/metadata competing-branch classification、多文档 index-loss 后 rebuild proof,以及 richer metadata multi-variant rebuild/reporting proof 都已落地;因此现在的 active lane 已明确转为 M3 / M4。`M3` 也已经越过已落地的最终独立 dual-role 收尾,接下来直接面对建立在当前 inspect/list/publish、per-document current-governance summaries 与 store index governance source/context 摘要基线之上的更广 governance persistence、更完整的 governance tooling,以及 reader-facing profile ergonomics;再加上剩余的 M4 session/capability/error-path interop proof,而更广的 pre-HELLO / pre-root / pre-MANIFEST gating、 HEADS 先于 MANIFEST 建立 sync roots、 HEADS replace=true 后的 stale root/dependency、stale snapshot 与 stale object WANT rejection、unadvertised WANT、unrequested OBJECT、unknown-sender 与 HELLO sender-identity mismatch rejection、 ERROR-before-HELLO acceptance、explicit ERROR-only 与 unreachable WANT proof,以及常设 messages-after-BYE rejection 与 missing-BYE warning handling 也都已补上。

  1. 维持 M2 在当前窄版 replay/storage/rebuild 范围内的已关闭状态,并以 richer mixed content/metadata competing-branch rebuild/reporting proof 作为基线。
  2. 在 accepted-head inspect/render、更清楚的 available-profile 和 profile-error feedback、editor-admission-aware profile base、bounded viewer score surfaces、初始 governance inspect/list/publish/current surfaces、persisted governance relationship summaries、per-document current-governance summaries,以及 store index governance source/context 摘要之上,谨慎扩展 M3 的 reader-plus-governance workflows;既然最终独立 dual-role 收尾已经落地,接下来就把更广的 governance persistence、更完整的 governance tooling,以及超出当前初步打磨的 profile ergonomics 明确保留下来。
  3. M4 保持窄范围;现在更广的 pre-HELLO / pre-root / pre-MANIFEST gating、HEADS 先于 MANIFEST 的 sync-root setup、HEADS replace=true 后的 stale root/dependency、stale snapshot 与 stale object WANT rejection、unadvertised WANT、unrequested OBJECT、unknown-sender 与 HELLO sender-identity mismatch rejection、ERROR-before-HELLO acceptance、explicit ERROR-only、unreachable WANT,以及 messages-after-BYE / missing-BYE coverage 都已有 proof,接下来把 peer-store sync proof 往剩余的 session/capability/error-path interop closure 收敛。

里程碑时间线

这份 roadmap 是串行推进的:后面的 phase 都默认前面的 phase 已经稳定。现在的重心是维持 M2 在当前窄版范围内的已关闭状态、M3 的谨慎扩展,以及剩余的 M4 互操作 proof。

最小核心

M1

已关闭门槛
  • minimal-client proof 已保留为完成的 checklist 历史
  • Ready-to-Build Gate 仍然保持全绿
  • 活跃工作已经转到 M2 / M3 / M4
最小核心

M2

已在当前窄版范围内关闭
  • Replay 和 state_hash
  • Store rebuild、indexes、带 ancestry-aware 的 render/store verification,以及多文档 index-loss 后 rebuild proof
  • Narrow write-path closure
  • 带更广 structural coverage、较新 manual-curation smoke proof、更清楚 metadata merge 边界、更完整 mixed content/metadata competing-branch 细节,且在当前窄版范围内已无剩余收口缺口的 conservative merge authoring
阅读器加治理

M3

早期部分完成
  • Accepted-head reader workflows
  • Bundle 和 store rendering,并保留 ancestry context
  • 命名 fixed-profile reading,并带有更清楚的 available-profile 与 profile-error feedback
  • 具备 editor-admission 感知的 inspect/render flows
  • head inspection 中的 bounded viewer score surfaces
  • Filtered governance inspect/list/publish workflows
  • Persisted governance reverse indexes
  • view inspect / view list 里可见的 persisted governance relationship summaries
  • view current 里提供的 per-document current-governance summaries
  • store index 输出里可见的 governance source labels 与 current-view context 摘要
  • 剩余工作:更广的 governance persistence、更完整的 governance tooling,以及超出当前初步打磨的 profile ergonomics
全栈

M4

早期部分完成
  • Wire validation 与 OBJECT body 检查
  • Session reachability 与 store-backed bootstrap
  • Peer-store 的 first-time / incremental sync proof
  • Capability-gated 的 SNAPSHOT_OFFER / VIEW_ANNOUNCE
  • localhost multi-process、re-sync idempotency、depth-N catchup 与 partial-doc selective sync proofs
  • 更广的 pre-HELLO / pre-root / pre-MANIFEST gating
  • HEADS 先于 MANIFEST 的 sync-root setup,以及 HEADS replace=true 后的 stale root/dependency、stale snapshot 与 stale object WANT rejection
  • unadvertised WANT 与 unrequested OBJECT rejection
  • unknown-sender 与 HELLO sender-identity mismatch rejection
  • ERROR-before-HELLO acceptance,以及 explicit ERROR-only 与 unreachable WANT rejection proof
  • messages-after-BYE rejection 与 missing-BYE warning proof
  • 剩余工作是更广的 session/capability/error-path interop proof
全栈

M5

后续
  • Selective app-layer growth
  • Profiles on stable core
  • Limited surface expansion

Implementation Matrix

这张表把 checklist 压缩成 section-level 状态,让我们快速看到哪些部分已经大致完成、哪些仍然是 partial、哪些仍属于后续 phases。

Area Status Milestone Current read
1. Repo and Build Setup Done M1 这一块现在属于已关闭的 minimal-client gate;这里已经没有活跃的 follow-up。
2. Object Types and IDs Done M1 必需的 v0.1 families 与 minimal-client role modeling 现在都保留为已关闭 gate 的 proof,不再是活跃的 checklist debt。
3. Canonical Serialization and Hashing Done M1 minimal gate 所需的 canonical rules 与 shared helper reuse 已关闭;post-M1 的 wire follow-up 现在属于更广的 M4 lane。
4. Signature Verification Done M1 / M4 minimal gate 所需的 object 与 wire signature verification 已关闭;更广的 interop/error-path follow-up 仍在 M4
5. Patch and Revision Engine Mostly done M2 Replay 与 state_hash 已到位;dependency verification、wrong-type 与 multi-hop ancestry proofs、sibling declared-ID determinism,以及 render-path ancestry context 都更完整。
6. Local State and Storage Mostly done M2 Store ingest、rebuild、indexes,以及可直接证明多文档 indexes 能在 index loss 后只靠 stored canonical objects 重建的 CLI proof 都已存在;local transport/safety policy 现在也会保存在独立的 local policy file,而 rebuild smoke 会同时保留 replicated indexes 与 local policy state。
7. Wire Protocol Partial M4 Canonical wire-envelope parsing、field validation、RFC 3339 checks、minimal-message payload validation、sender checks、session sequencing/head tracking、reachability gating、store-backed bootstrap、OBJECT body verification、capability-gated optional-message handling、更广的 pre-HELLO、pre-root 与 pre-MANIFEST gating、HEADS 先于 MANIFEST 的 sync-root setup、HEADS replace=true 后的 stale root/dependency、stale snapshot 与 stale object WANT rejection、unadvertised WANT 与 unrequested OBJECT rejection、unknown-sender 与 HELLO sender-identity mismatch rejection、ERROR-before-HELLO acceptance、explicit ERROR-only 与 unreachable WANT rejection proof、messages-after-BYE 与 missing-BYE warning proof,以及最小 peer-store sync driver 都已存在于 mycel-core;主要剩余 interop 工作是更广的 session/capability/error-path proof。
8. Sync Workflow Partial M4 Peer-store 驱动的 first-time 与 incremental sync 现在已通过 mycel-core、CLI 与 simulator positive-path coverage 证明 shared verify/store flow,并覆盖 snapshot-assisted catch-up、announced-view fetching、localhost multi-process proof、re-sync idempotency、depth-N incremental catchup、partial-doc selective sync、更广的 pre-HELLO / pre-root / pre-MANIFEST gating、HEADS 先于 MANIFEST 的 sync-root setup、HEADS replace=true 后的 stale root/dependency、stale snapshot 与 stale object WANT rejection、unadvertised WANT 与 unrequested OBJECT rejection、unknown-sender 与 HELLO sender-identity mismatch rejection、ERROR-before-HELLO acceptance、explicit ERROR-only 与 unreachable WANT rejection,以及 messages-after-BYE 与 missing-BYE warning handling;剩余工作是更广的 session/capability/error-path proof。
9. Views and Head Selection Mostly done M3 Deterministic selector core、命名 fixed-profile selection、更清楚的 available-profile summaries 与 profile-error feedback、分开的 editor/view admission-aware inspect/render flows、bounded viewer score channels、在 view inspect / view list 里可见的 persisted governance relationship summaries、在 view current 里提供的 per-document current-governance summaries、store index governance source/context 摘要,以及直接锁定 shared-key / mixed-role dual-role admission、weight 与 support 关系的 core-level selector regressions 都已经存在;现在剩下的 M3 缺口是更广的 governance persistence、更完整的 governance tooling,以及超出当前初步打磨的 profile ergonomics。
10. Merge Generation Partial M2 Replay verification 与保守型 local merge-authoring profile 已存在,涵盖 structural move/reorder、新 parent reparenting、简单 composed parent-chain coverage、更广的 nested structural matrix、更细的 direct/anchor-based placement reasons、更清楚的 metadata competing-branch 边界,以及 richer mixed content/metadata competing-branch 细节;当前窄版 M2 收口已经完成,因此后续工作可以留在 active M2 债务之外。
11. CLI or API Surface Partial M2 / M3 / M4 Verification、authoring、保守型 merge authoring、editor-admission-aware reader inspection/render、governance inspect/list/publish/current、persisted governance index query surfaces、在 view inspect / view list 里可见的 persisted governance relationship summaries、store index governance source/context 摘要、transcript-backed sync pull,以及内部 sync peer-store 都已存在,并包含 optional snapshot/view flows、localhost multi-process proof、re-sync idempotency、depth-N catchup、partial-doc selective sync、更广的 pre-HELLO / pre-root / pre-MANIFEST gating、HEADS 先于 MANIFEST 的 sync-root setup、HEADS replace=true 后的 stale root/dependency、stale snapshot 与 stale object WANT rejection、unadvertised WANT 与 unrequested OBJECT rejection、unknown-sender 与 HELLO sender-identity mismatch rejection、ERROR-before-HELLO acceptance、explicit ERROR-only 与 unreachable WANT rejection,以及 messages-after-BYE 与 missing-BYE warning handling;剩余的 M4 gap 是更广的 session/capability/error-path interop proof。
12. Interop Test Minimum Partial M1 / M2 / M4 Fixture isolation、reproducibility、更严格的 parser/replay smoke coverage、直接的 wire-envelope/signature/session tests、peer-store first-time / incremental sync proofs、optional-message coverage、localhost multi-process proof、re-sync idempotency coverage、depth-N incremental catchup coverage、partial-doc selective sync coverage、更广的 pre-HELLO / pre-root / pre-MANIFEST gating coverage、HEADS 先于 MANIFEST 的 setup coverage、HEADS replace=true 后 stale root/dependency、stale snapshot 与 stale object WANT rejection 的 coverage、unadvertised WANT 与 unrequested OBJECT coverage、unknown-sender 与 HELLO sender-identity mismatch coverage、ERROR-before-HELLO acceptance coverage、explicit ERROR-only 与 unreachable WANT coverage,以及 messages-after-BYE 与 missing-BYE warning coverage 都已存在,但更广的 session/capability/error-path cases 仍未完成。
13. Ready-to-Build Gate Done M1 minimal-client gate 已关闭;剩余工作现在都改由 post-M1 follow-up checklist 追踪,而不是留在这个 gate。

Source Files

这个页面刻意只做摘要。真正的权威表述仍然在仓库级 planning files 里。

Progress Source

这个公开页面所依据的 Markdown 摘要来源。

Open PROGRESS.md

GitHub Adoption

Repo workflow 与 security adoption 的规划文档,包含已启用的 CodeQL default setup,以及已修复的第一批 workflow-permissions findings。

Open GITHUB-ADOPTION-PLAN.md