Skip to content

RFC: Personal Follow-through (v0)

  • RFC status: Superseded
  • Supersedes / closes: none
  • Superseded by: Capable Agent Manager and Semantic Work Handoff
  • Delivery maturity: Historical proposal; no independent acceptance or promotion authority.
  • Authors / owners: Manager, personal-workspace, work-item and Lark extension maintainers
  • Created / last normative revision: 2026-10-01 / 2026-10-04
  • Language mirror: 中文版

Disposition and current design

中文版 is the semantic mirror of this file. The proposed independent lifecycle and M1–M3 plan are superseded by the accepted manager RFC, especially §5.2/§5.3/§5.11/§5.12 and its acceptance and dependency plan. This is a design consolidation; it does not claim implementation, deployment, account authorization or completed acceptance.

The retained Lark personal follow-through profile contains source interpretation, verified responsibility, personal privacy scope, TypeScript/Node implementation constraints, frozen semantic evaluation and the attention-cost pilot. Its mapping to manager A3/A5–A10/A13–A15/A20 and M1–M4 replaces the former independent delivery plan. Shared state, grants, recovery and return stay with their existing owners. No parallel task/proposal store or scheduler is approved. Future engineering and evidence follow those canonical owners.

Appendix A: Baseline evidence

At the original baseline f49b4a0, Lark, Todo and report components existed but no complete personal-commitment desktop journey was qualified. The historical CLI evidence below uses scripted external providers and does not close manager acceptance. No operational Todo allocation is asserted by this document.

Appendix B: Execution ledger

The historical execution ledger retains its original evidence and historical M1 terminology. Current integration evidence is recorded in the manager ledger.