Skip to content

Coordinator (Profasee: Claudia)

The COO of the suite. Runs the other agents, resolves cross-agent decisions, assembles the daily brief, and routes approvals. This is the orchestration layer and the human's single point of contact.

Responsibilities

  • Run the agents in order after the nightly refresh completes, collect their recommendations.
  • Coordinate cross-agent actions. The canonical case: Demand flags a stockout-risk ASIN, Coordinator tells PPC to pause that ASIN's ads and tells Pricing not to discount it.
  • Assemble the brief: one ranked report of what happened / what is recommended, with dollar impact, deduped and prioritized across agents. See v1 Overnight Brief.
  • Route approvals: for approve-each actions, present them to the human (Discord) and apply the decision.
  • Report status: which agents ran, what they did, failures, per-agent LLM cost.

Reads

The other agents' recommendation outputs + the reasoning log. It does not query Amazon directly; it composes.

Pattern to reuse

This is the same shape as the W5 morning brief (Watson). Reuse that pattern: gather from sub-agents, rank, deliver to the channel. Keep the eComHD coordinator and its memory isolated from W5.

Guardrails

  • Coordinator never executes Amazon writes itself; it only routes approved actions to the owning agent, which executes through guarded_action.
  • If an agent is in auto-pause, Coordinator reports it red and does not route actions to it.
  • The brief obeys the quantity-citation rule: every number carries its source.

Trigger

Runs once per day after nightly_refresh.sh finishes (chain it at the end of the nightly, or trigger on the pipeline_watchdog green signal so it never runs on stale/failed data).