You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Follow-up from the 2026-07-02 docs audit. Four feature docs describe shipped features but still read as pre-build plans/specs. Each needs an editorial rewrite from plan-tense ("we will build", "Proposed capabilities", phased roadmaps) to current-state documentation, verifying claims against the code while rewriting:
docs/features/digital-twin.md — still carries a "Planned Phases" section (3/5/6/7) with inline "done" annotations; reconcile into a clean current-state doc. All three claimed UI components exist (PersonalityMap.jsx, ConfidenceGauge.jsx, GapRecommendations.jsx).
docs/features/openclaw-operator-chat.md — Status header is accurate, but the body is still a proposal ("Proposed capabilities", "Open questions", "Recommended design decisions", "Initial deliverables"). Trim to a living doc; keep the honest list of proposed-but-unbuilt endpoints (POST /sessions, /jobs, /subagents, /context/compose).
docs/features/writers-room.md — reads as an implementation plan (PR feat(creative-director): autonomous long-form video projects + media job queue #191 baseline, "Phase 0 complete"). Caution: source code references this file (server/lib/planIds.test.js, server/services/writersRoom/local.js, server/services/writersRoom/syncedReview.js) — check what those depend on (likely plan-item IDs) before restructuring; run the full server suite after.
Also worth considering in the same pass (not required): soul-system.md / digital-twin.md / identity-system.md are three angles on the same subsystem (document workflow vs quantitative modeling vs unified architecture) — cross-link them clearly or consolidate.
Deferred from the audit because these are content rewrites needing per-doc code verification, not mechanical reorganization.
Follow-up from the 2026-07-02 docs audit. Four feature docs describe shipped features but still read as pre-build plans/specs. Each needs an editorial rewrite from plan-tense ("we will build", "Proposed capabilities", phased roadmaps) to current-state documentation, verifying claims against the code while rewriting:
docs/features/digital-twin.md— still carries a "Planned Phases" section (3/5/6/7) with inline "done" annotations; reconcile into a clean current-state doc. All three claimed UI components exist (PersonalityMap.jsx,ConfidenceGauge.jsx,GapRecommendations.jsx).docs/features/openclaw-operator-chat.md— Status header is accurate, but the body is still a proposal ("Proposed capabilities", "Open questions", "Recommended design decisions", "Initial deliverables"). Trim to a living doc; keep the honest list of proposed-but-unbuilt endpoints (POST /sessions,/jobs,/subagents,/context/compose).docs/features/post.md— framed as an implementation spec with "Existing" vs "New (M55)" sections and a full data model; trim to current-state. Note the POST overhaul epic Epic: POST feature overhaul — responsive layout, analytics, spaced repetition, adaptive difficulty & Morse improvements #1985 may churn this area — coordinate.docs/features/writers-room.md— reads as an implementation plan (PR feat(creative-director): autonomous long-form video projects + media job queue #191 baseline, "Phase 0 complete"). Caution: source code references this file (server/lib/planIds.test.js,server/services/writersRoom/local.js,server/services/writersRoom/syncedReview.js) — check what those depend on (likely plan-item IDs) before restructuring; run the full server suite after.Also worth considering in the same pass (not required):
soul-system.md/digital-twin.md/identity-system.mdare three angles on the same subsystem (document workflow vs quantitative modeling vs unified architecture) — cross-link them clearly or consolidate.Deferred from the audit because these are content rewrites needing per-doc code verification, not mechanical reorganization.