Status:
ACTIVEgovernance index Audit date: 2026-08-23 Purpose: explain where every planning-like document belongs and prevent a new roadmap/backlog from appearing outsidedocs/planning/.
| Information | Canonical location | Examples |
|---|---|---|
| Feature status | docs/planning/FEATURES.md |
EVAL-001 = SPEC_READY |
| Non-terminal task status | docs/planning/BACKLOG.md |
EVAL-101 = READY |
| Terminal task/evidence | docs/planning/archive/YYYY-QN.md |
PLATFORM-401 = DONE |
| Product sequencing/gates | docs/planning/ROADMAP.md (EN; root ROADMAP_V2.md archived RU original) |
M0–M6, Z1–Z6 |
| Dependency delivery waves | docs/planning/EXECUTION_ROADMAP.md |
Wave 0–6, WIP and claiming |
| Feature specification | docs/roadmap/NN-*.md or a domain hub |
roadmap 08, evaluation hub |
| Architecture decision | docs/adr/ADR-NNN-*.md |
ADR-009 |
| Operational procedure | docs/runbooks/*.md |
rollback, failed posts |
| Code-review/audit evidence | docs/reviews/, docs/audit/ |
snapshot findings |
| Historical task breakdown | docs/refactor/, .forge/ |
reference only, frozen status |
| Research input | named research/audit file | not a backlog |
No new file outside docs/planning/ may call itself the active backlog, task tracker,
current sprint, feature register or single source of status.
- Planning rules
- Feature register
- Active backlog
- Execution roadmap
- Task archive
- Product roadmap
- Evaluation domain
- Roadmap specification index
- ADR directory
| Document | Feature ID | Role | Overlap decision |
|---|---|---|---|
roadmap/01-multi-account.md |
ACCOUNT-001 |
Product/component summary | Primary product outcome, scope and acceptance summary. |
roadmap/01-multi-account-plan.md |
ACCOUNT-001 |
Companion implementation detail | Explicit summary/detail split selected by PLAN-004; implementation sequencing and technical decisions live here, while status remains canonical in planning. |
roadmap/02-per-account-settings.md |
ACCOUNT-002 |
Component specification | Distinct child of multi-account. |
roadmap/03-gemini-nano-image-generation.md |
MEDIA-001 |
Feature specification | No duplicate runtime image feature found. |
roadmap/04-per-account-prompts-brand-voice.md |
PERSONA-001 |
Supporting component specification | Account voice/profile mechanics; roadmap 08 owns the broader persona product. |
roadmap/05-llm-token-cost-optimization.md |
COST-001 |
Feature specification | Cost mechanics; evaluation owns comparative quality/cost measurement. |
roadmap/06-self-healing-resilience.md |
REL-001 |
Feature specification | Technical recovery; roadmap 12 owns external policy/reputation authorization. |
roadmap/07-additional-features-research.md |
none | Research inbox | Decompose into feature IDs before work; never use its checklist as backlog. |
roadmap/08-editorial-personas-conversational-engagement.md |
PERSONA-001, ENGAGE-001, GROUND-001 |
Aggregate product/technical specification | Owns persona, reviewed conversation execution and memory boundaries. |
roadmap/09-ai-change-release-gate.md |
EVAL-001 |
Roadmap/milestone proposal | Detailed contracts are superseded by docs/evaluation/; safe reduction tracked by PLAN-003. |
evaluation/* |
EVAL-001 |
Normative domain specification | Owns rubrics, datasets, telemetry, CI and promotion contracts. |
roadmap/10-conversation-intelligence-demand-radar.md |
INTEL-001 |
Feature specification | Aggregates reviewed public demand; does not execute replies. |
roadmap/11-reply-to-revenue-assisted-attribution.md |
ATTR-002 |
Feature specification | Assisted/incremental layer; ADR-007 remains direct attribution. |
roadmap/12-platform-policy-reputation-control-plane.md |
POLICY-001 |
Feature specification | External authorization/reputation; not technical resilience. |
roadmap/13-creator-relationship-crm.md |
CRM-001 |
Feature specification | Public relationship workflow; not interaction memory or demand clustering. |
roadmap/14-soulwise-editorial-data-bridge.md |
BRIDGE-001 |
Cross-repository feature specification | Dedicated sensitive boundary; generic content adapters remain infrastructure. |
roadmap/15-network-api-first-posters.md |
NETWORK-001 |
Feature specification (2026-08-23) | Owns the API-first transport decision for Bluesky/Mastodon; browser posters conserved behind flag. |
roadmap/16-telegram-control-bot.md |
CONTROL-001 |
Feature specification (2026-08-23) | Operator transport only; no business logic duplication, editing stays in dashboard. |
| ADR | Decision status | Feature/role |
|---|---|---|
| ADR-001 Camoufox | Accepted | Browser transport foundation. |
| ADR-002 BullMQ | Accepted | Queue foundation. |
| ADR-003 LangGraph generation | Accepted | Generation foundation. |
| ADR-004 Hexagonal ports | Accepted | Architecture foundation. |
| ADR-005 SSE | Accepted | Realtime foundation. |
| ADR-006 autonomous architecture | Accepted | ORCH-001/autonomy foundation. |
| ADR-007 link attribution | Accepted | ATTR-001 direct attribution. |
| ADR-008 persona/memory/engagement | Accepted 2026-08-23 | PERSONA-001, ENGAGE-001, GROUND-001. |
| ADR-009 AI release gate | Accepted for design | EVAL-001. |
| ADR-010 demand radar | Accepted 2026-08-23 | INTEL-001. |
| ADR-011 assisted attribution | Accepted 2026-08-23 | ATTR-002. |
| ADR-012 policy/reputation | Accepted 2026-08-23 | POLICY-001. |
| ADR-013 creator CRM | Accepted 2026-08-23 | CRM-001. |
| ADR-014 editorial bridge | Accepted 2026-08-23 | BRIDGE-001. |
| ADR-015 API-first network transport | Accepted 2026-08-23 | NETWORK-001; Bluesky/Mastodon use free official APIs by default, browser transport remains rollback-only. |
ADR decision status is legitimate and separate from implementation status. An accepted
ADR does not make its feature DONE.
| Location | Role | Rule |
|---|---|---|
docs/features/ab-testing-infrastructure.md |
PLATFORM-001 completion dossier |
Further judge work belongs to EVAL-001. |
docs/features/content-adapters.md |
PLATFORM-002 completion dossier |
A new adapter receives a new task, not a reopened status table. |
docs/features/operator-dashboard.md |
PLATFORM-003 completion dossier |
Evaluation panels belong to EVAL-701. |
docs/features/prompt-versioning-langfuse.md |
PLATFORM-004 completion dossier |
Native trace linkage belongs to EVAL-103. |
docs/features/browser-e2e-replay.md |
BROWSER-001 supporting proposal |
Canonical work is BROWSER-101..102. |
docs/features/multi-instance-distribution.md |
DIST-001 supporting proposal |
Current readiness conflict is DIST-101. |
docs/DEEP_ANALYSIS_LLM_GENERATION_2026-07-05.md |
Historical technical research | Findings must be re-verified and converted into canonical tasks. |
docs/RESEARCH_JUDGING_v0.5.2.md |
Historical research/judging | Calibration design is now in docs/evaluation/07-*. |
docs/ARCHITECTURE_AUDIT_v0.5.1.md |
Historical audit | Evidence snapshot, not current architecture spec. |
| Document | Historical value | Current rule |
|---|---|---|
CONSTITUTION.md |
Original requirements, resolved questions and changelog | Historical requirements snapshot; no current feature/task status. |
ROADMAP.md |
Completed phases 0–6 and old release evidence | Archived. docs/planning/ROADMAP.md owns sequencing; root ROADMAP_V2.md is the archived RU v2.4 original. |
FEATURE_WISHLIST.md |
F1–F22 brainstorm history | Archived; ideas require a feature ID. |
docs/audit/08-BACKLOG.md |
June audit remediation order/evidence | Frozen audit snapshot. |
docs/reviews/ACTION_PLAN.md |
Review-derived task inventory | Frozen finding index. |
docs/refactor/* |
Detailed old acceptance/checklists | Frozen evidence; reconcile through PLAN-005. |
.forge/orchestrator/* |
Original orchestrator workstream design | Frozen task status; map through ORCH-101. |
Runbooks keep operational checkboxes because they are procedures, not task status.
Code comments and env docs from pre-planning-hub eras reference "Sprint X" letters and "F-numbers" that have no defining document. They are historical labels only — never sources of status. When touching a file, replace the legacy label with the canonical feature/task ID from the map below; do not do bulk comment sweeps in files owned by active workstreams.
| Legacy label | Meaning | Canonical reference |
|---|---|---|
| Sprint P | Prompt registry / Langfuse prompt versioning | PLATFORM-004 (done) |
| Sprint Q / F4 | Replies monitoring UI, question classifier, incoming comments | Replies module (REPLIES_ENABLED), conversation work → ENGAGE-001 |
| Sprint T | LLM-in-the-loop queue triage | CONTROL-001 adjacent ops tooling (queue.controller.ts) |
| Sprint I | Resumability + HITL review interrupt | Generation graph human_review node (generation.controller.ts resume/review endpoints) |
| Sprint J/K/L/N/O | Hardening waves: LLM quality, browser pool/perf, SSE+Redis pooling, resource limits, EDA+flagged modules | Superseded by HARDEN-001 (CI-*, REFACTOR-*, DESIGN-*) and REL-001 |
| F6 / F13 / F19 / F20 / F21 / F22 | Metrics scraping / recycling / quote cards / warm-up / ban detection / trending | AnalyticsModule metrics, RECYCLE-*, quote-cards flag, sessions warm-up, health monitor, trending module |
| F1 / F8 | Autonomous agent / A-B infra | ORCH-001 / PLATFORM-001 |
Similarity audit confirms material overlap, especially CI, rollout and observability.
Do not delete user-authored content during active work. After review, reduce roadmap 09
to product scope/milestones and keep technical contracts only in docs/evaluation/.
The explicit non-overlapping summary/detail split is selected: 01-multi-account.md
owns product outcome and scope; 01-multi-account-plan.md owns implementation detail,
technical decisions and sequencing. Neither document owns current task status, and the
two files are retained without destructive consolidation while ACCOUNT-101 remains
in external verification.
Old refactor/audit trackers contain hundreds of unchecked or snapshot-completed boxes. They cannot be bulk-copied into the active backlog because code has drifted. Reproduce each surviving finding, create a stable canonical task only if still valid, and archive or cancel the rest with evidence.
Before adding a planning-like Markdown file:
- Search this map and
FEATURES.mdfor the concept. - Reuse the existing feature ID or create one
IDEArow. - State document role and canonical feature status link in the header.
- Do not add live task status/checklists outside
BACKLOG.md. - Link an ADR for a real architectural decision.
- Add the document to this map.