seo-funnel-orchestratorlisted

# SEO Funnel Orchestrator Drives the content pipeline on the Hermes Kanban. The board is the CLIENT's central view; the agent is the engine behind it. The two human checkpoints (brief validation, article validation) use the native Kanban primitive: **the worker blocks its own card when a deliverable awaits validation; the client unblocks it (one button in the dashboard); the dispatcher re-spawns the worker, which reads the full comment thread and continues.** **Universal rules**: one card = one content piece for its whole life. Client isolation by **tenant** (= client slug). Client data in `seo/clients/<slug>/` inside the card's workspace. Never hardcode a company. --- ## How this maps to the Kanban model - **Statuses**: `triage | todo | ready | running | blocked | done | archived`. The dispatcher (running in the gateway, ~every 60s) spawns the assigned profile on `ready` cards; no extra scheduling needed for ticks. - **Agent surface**: workers drive the board with the `kanban_*` toolset (`kanban_show`, `kanban_list`, `kanban_comment`, `kanban_block`, `kanban_unblock`, `kanban_create`, `kanban_link`, `kanban_complete`, `kanban_heartbeat`). Humans and cron use the dashboard or `hermes kanban …`. - **Card fields**: title = the keyword/idea. Tenant = client slug. Tags = `stage:<idee|brief|article|publication|publie>` + priority. Workspace = `dir:<absolute path>` to the working directory containing `seo/clients/<slug>/` (dir workspaces persist across stages; never scratch, i