Meta: Implementation Roadmap

[ggondim]

Dependency Graph

#1 Bootstrap
 └─► #2 Data Model & Interfaces
      ├─► #3 Router ──────────────────┐
      ├─► #4 Reply Engine ◄───────────┤
      ├─► #5 Token & Thread Mgmt ─────┤
      ├─► #6 MongoDB Adapter ─────────┤
      ├─► #7 Slack Adapter ───────────┤
      ├─► #8 Telegram Adapter         │
      ├─► #9 Discord Adapter          │
      └─► #10 WhatsApp Adapter        │
                                      ▼
                              #11 Server: API Routes
                               ├─► #12 A2H Forms
                               │    └─► #14 Trust Layer
                               ├─► #13 Dashboard UI
                               └─► #15 Integration Testing
                                    └─► #16 Release & DX

Execution Order

Issues grouped by wave — all issues within a wave can run in parallel.

Wave 1 — Foundation

• Project Bootstrap — Monorepo, CI, Dev Environment #1 Project Bootstrap P0

Wave 2 — Contracts

• Core: Data Model, Types & Interfaces #2 Core: Data Model, Types & Interfaces P0

Wave 3 — Core Logic + Adapters (parallel)

• Core: Router Implementation #3 Core: Router P0
• Core: Token & Thread/Turn Management #5 Core: Token & Thread/Turn Management P0
• Storage: MongoDB Adapter #6 Storage: MongoDB Adapter P0
• Channel: Slack Adapter #7 Channel: Slack Adapter P0

Wave 4 — Reply Engine

• Core: Reply Engine #4 Core: Reply Engine P0 (depends on Core: Router Implementation #3)

Wave 5 — Server + More Adapters (parallel)

• Server: API Routes & Infrastructure #11 Server: API Routes & Infrastructure P0
• Channel: Telegram Adapter #8 Channel: Telegram Adapter P1
• Channel: Discord Adapter #9 Channel: Discord Adapter P2
• Channel: WhatsApp Adapter (Baileys) #10 Channel: WhatsApp Adapter P2

Wave 6 — UI & Forms (parallel)

• Server: Auto-Generated A2H Forms #12 Server: A2H Forms P1
• Server: Dashboard UI #13 Server: Dashboard UI P1

Wave 7 — Trust & Hardening

• Trust Layer — JWS, Auth, Audit #14 Trust Layer P2
• Integration Testing & Hardening #15 Integration Testing & Hardening P2

Wave 8 — Release

• Release & Developer Experience #16 Release & DX P3

Orchestrator Instructions

When picking the next issue to enqueue:

1. Issues within the same wave can be assigned in parallel
2. A wave is ready when ALL issues from previous waves are checked
3. An individual issue is ready when ALL its explicit dependencies (listed in its body) are checked
4. After completing all issues, open a final PR: meta/<this_issue_number> → main

[ggondim]

@claude Start the orchestration loop. Read this meta issue, create the meta branch, and assign the first wave of tasks.

[ggondim]

@claude Start the orchestration loop. Read this meta issue, create the meta branch, and assign the first wave of tasks.

[ggondim]

@claude Start the orchestration loop. Read this meta issue, create the meta/17 branch, and assign the first wave of tasks.

[ggondim]

@claude Start the orchestration loop. Read this meta issue, create the meta/17 branch, and assign the first wave of tasks.

[claude]

Orchestrator Update

Setup

• Created branch meta/17 from main ✓

Issues Marked Done

• None yet (all unchecked)

Issues Assigned

• Project Bootstrap — Monorepo, CI, Dev Environment #1 — Project Bootstrap — Monorepo, CI, Dev Environment P0
  • Working branch: claude/17-1-project-bootstrap
  • Targeting: meta/17
  • Auto-merge: enabled (P0)

What's Next

Once #1 is merged, Wave 2 becomes ready:

• Core: Data Model, Types & Interfaces #2 — Core: Data Model, Types & Interfaces P0

After #2 merges, Wave 3 (parallel) becomes ready:

• Core: Router Implementation #3 Core: Router
• Core: Token & Thread/Turn Management #5 Core: Token & Thread/Turn Management
• Storage: MongoDB Adapter #6 Storage: MongoDB Adapter
• Channel: Slack Adapter #7 Channel: Slack Adapter

[claude]

Orchestrator Update

Marked Done

• Project Bootstrap — Monorepo, CI, Dev Environment #1 Project Bootstrap — merged via PR Project Bootstrap — Monorepo, CI, Dev Environment #18

Assigned

• Core: Data Model, Types & Interfaces #2 Core: Data Model, Types & Interfaces P0 — assigned for implementation

What's Next

Issue #2 is the Wave 2 blocker. Once it merges, Wave 3 issues (#3, #5, #6, #7) can all run in parallel.

[claude]

Orchestrator Update

Marked as done

• Core: Data Model, Types & Interfaces #2 Core: Data Model, Types & Interfaces — merged via PR Core: Data Model, Types & Interfaces #19

Assigned (Wave 3 — all parallel, all P0)

• Core: Router Implementation #3 Core: Router Implementation — assigned to @claude
• Core: Token & Thread/Turn Management #5 Core: Token & Thread/Turn Management — assigned to @claude
• Storage: MongoDB Adapter #6 Storage: MongoDB Adapter — assigned to @claude
• Channel: Slack Adapter #7 Channel: Slack Adapter — assigned to @claude

What's next

Wave 3 is now in progress. Once all four issues are merged:

• Wave 4 (Core: Reply Engine #4 Core: Reply Engine) becomes unblocked (depends on Core: Router Implementation #3)
• Wave 5 (Server: API Routes & Infrastructure #11 Server: API Routes, Channel: Telegram Adapter #8 Telegram, Channel: Discord Adapter #9 Discord, Channel: WhatsApp Adapter (Baileys) #10 WhatsApp) becomes unblocked

[claude]

Orchestrator Update

Marked Done

• Core: Token & Thread/Turn Management #5 Core: Token & Thread/Turn Management — merged via PR Core: Token & Thread/Turn Management #20

Assigned (Wave 3 — parallel)

All three have priority:P0 and auto-merge enabled:

• Core: Router Implementation #3 Core: Router — assigned to @claude (branch claude/17-3-router)
• Storage: MongoDB Adapter #6 Storage: MongoDB Adapter — assigned to @claude (branch claude/17-6-mongodb-adapter)
• Channel: Slack Adapter #7 Channel: Slack Adapter — assigned to @claude (branch claude/17-7-slack-adapter)

What's Next

• Wave 3 must complete before Wave 4 (Core: Reply Engine #4 Reply Engine) and Wave 5 (Server: API Routes & Infrastructure #11 Server, Channel: Telegram Adapter #8 Telegram, Channel: Discord Adapter #9 Discord, Channel: WhatsApp Adapter (Baileys) #10 WhatsApp) can begin
• Core: Reply Engine #4 specifically depends on Core: Router Implementation #3 (Router)

[claude]

Orchestrator Update

Marked done

• Core: Router Implementation #3 Core: Router — PR Core: Router Implementation #21 merged into meta/17

Already in progress (assigned earlier)

• Storage: MongoDB Adapter #6 Storage: MongoDB Adapter — assigned, awaiting PR
• Channel: Slack Adapter #7 Channel: Slack Adapter — assigned, awaiting PR

Newly assigned

• Core: Reply Engine #4 Core: Reply Engine — assigned (P0, auto-merge enabled). Dependencies Core: Data Model, Types & Interfaces #2 and Core: Router Implementation #3 are both merged.

What's next

Wave 4 (#4) is now unblocked and in progress. Wave 3 (#6, #7) are still in progress. Once #4, #6, and #7 are all merged, Wave 5 (#8, #9, #10, #11) will become ready.

[claude]

Orchestrator Update

Marked Done

• Storage: MongoDB Adapter #6 Storage: MongoDB Adapter — PR Storage: MongoDB Adapter #22 was merged

Assigned (Re-triggered)

• Core: Reply Engine #4 Core: Reply Engine (P0) — previously assigned but no PR created; re-assigned
• Channel: Slack Adapter #7 Channel: Slack Adapter (P0) — previously assigned but no PR created; re-assigned

Newly Assigned

• Channel: Telegram Adapter #8 Channel: Telegram Adapter (P1) — dependencies satisfied (Core: Data Model, Types & Interfaces #2 ✅)
• Channel: Discord Adapter #9 Channel: Discord Adapter (P2) — dependencies satisfied (Core: Data Model, Types & Interfaces #2 ✅)
• Channel: WhatsApp Adapter (Baileys) #10 Channel: WhatsApp Adapter (P2) — dependencies satisfied (Core: Data Model, Types & Interfaces #2 ✅)

Blocked (waiting on dependencies)

• Server: API Routes & Infrastructure #11 Server: API Routes — waiting on Core: Reply Engine #4, Channel: Slack Adapter #7
• Server: Auto-Generated A2H Forms #12 A2H Forms — waiting on Server: API Routes & Infrastructure #11
• Server: Dashboard UI #13 Dashboard UI — waiting on Server: API Routes & Infrastructure #11
• Trust Layer — JWS, Auth, Audit #14 Trust Layer — waiting on Server: Auto-Generated A2H Forms #12
• Integration Testing & Hardening #15 Integration Testing — waiting on Server: API Routes & Infrastructure #11
• Release & Developer Experience #16 Release & DX — waiting on Integration Testing & Hardening #15

Current Wave 3/4 Progress

Issue	Status
#3 Router	✅ Done
#5 Token & Thread Mgmt	✅ Done
#6 MongoDB Adapter	✅ Done
#7 Slack Adapter	🔄 In progress
#4 Reply Engine	🔄 In progress

[claude]

Orchestrator Update

Marked as done

• Channel: Slack Adapter #7 Channel: Slack Adapter — PR Channel: Slack Adapter #23 was merged into meta/17

Assigned

• Core: Reply Engine #4 Core: Reply Engine P0 — assigned to @claude (all Wave 3 dependencies satisfied: Core: Data Model, Types & Interfaces #2, Core: Router Implementation #3 both done)

What's next

Wave 4 (#4 Reply Engine) is now in progress. Once #4 merges, Wave 5 will unlock: #11 (Server: API Routes, P0), #8 (Telegram, P1), #9 (Discord, P2), #10 (WhatsApp, P2) — all can run in parallel.

Blocked

All other waves are waiting on Wave 4 to complete.

[ggondim]

@claude Continue the orchestration loop. Check for merged PRs and assign the next wave.

[claude]

Orchestrator Update

Marked Done

• Core: Reply Engine #4 Core: Reply Engine — merged via PR Core: Reply Engine #24

Wave 5 Assigned (all in parallel)

• Server: API Routes & Infrastructure #11 Server: API Routes & Infrastructure P0 — assigned (auto-merge enabled)
• Channel: Telegram Adapter #8 Channel: Telegram Adapter P1 — assigned
• Channel: Discord Adapter #9 Channel: Discord Adapter P2 — assigned
• Channel: WhatsApp Adapter (Baileys) #10 Channel: WhatsApp Adapter P2 — assigned

What's Next

Once all Wave 5 issues are merged, Wave 6 will begin:

• Server: Auto-Generated A2H Forms #12 Server: A2H Forms
• Server: Dashboard UI #13 Server: Dashboard UI

[ggondim]

@claude Continue. Check all merged PRs, update checkboxes, and assign the next wave.