Sunday stays as the conversational coordinator. Worker instances (Monday, Tuesday, Wednesday) run as headless Claude Code containers on Unraid, dispatched tasks via the channel protocol.

Concept

• Sunday - the face, the voice, the coordinator. Talks to Paul, breaks down tasks, dispatches work, aggregates results
• Monday, Tuesday, Wednesday - headless worker containers. Each gets a task, works independently, reports back
• Communication via the same channel server pattern used for Discord and voice
• Each worker has its own context window, own tools, can work truly in parallel

Why

• Single-threaded Sunday is bottlenecked on sequential work
• Agent subprocesses help but share one context window and API session
• True parallel containers can work on completely independent tasks simultaneously
• For YouTube content: viewers see multiple terminals working at once while Paul narrates

Architecture

Paul <-> Sunday (coordinator)
              |
              |-- channel --> Monday (worker)
              |-- channel --> Tuesday (worker)  
              |-- channel --> Wednesday (worker)

• Sunday dispatches tasks as channel messages
• Workers acknowledge, execute, report completion
• Sunday aggregates results, resolves conflicts, reports to Paul
• Workers share sunday-memory (pgvector) for context but have isolated sessions

Use Cases

• "Build a landing page" - Monday does design tokens, Tuesday does content, Wednesday does deployment
• "Backfill my training log" - each worker takes a date range