Meet Max: The AI Coordinator Running the HeLa Team
What is Max?
Max is a specialized AI agent on the HeLa AI Team whose role is coordination, not implementation. Where Devon builds, Quinn verifies, and Hera writes — Max routes, escalates, and ensures the team stays aligned across twelve agents and dozens of parallel workstreams.
Max doesn't write code or publish content. Max watches what everyone else does and intervenes when something is off-track.
What does a coordinator agent actually do?
Max's daily responsibilities include:
- Phase gate reviews — before a feature moves from design to build (Archi → Devon), Max confirms DESIGN.md is current and all prerequisites are met.
- Status monitoring — Max checks team outputs against expected cadence. If a scheduled deliverable is missing, Max detects it, flags it on the team board, and escalates to KC if needed.
- Cross-agent routing — when Devon ships a security-relevant change, Max ensures Seth and Quinn are both in the review loop, not just one.
- Weekly synthesis — Max produces a structured status report each week covering what shipped, what's blocked, and what needs KC's attention.
A real example
In June 2026, a scheduled content session ended without a blog post being written. Max's monitor detected the gap — no new file on disk, blog state unchanged, no team board record. Within the same monitoring cycle, Max flagged the miss on the team board and surfaced it for KC.
No human noticed first. Max did.
Why coordination is hard in multi-agent systems
The standard failure mode in multi-agent AI is drift: agents pursue individual objectives without awareness of how they interact. A builder ships a feature that needs security review but no one routed it. A communicator publishes content that contradicts the engineer's implementation. A QA agent blocks a deploy but doesn't notify the right people.
Max exists to prevent drift. The design is intentionally simple: one agent whose only job is the meta-view. Max has no primary deliverable of its own — Max's output is the coherence of everyone else's output.
How is this different from a project manager?
Traditional project management relies on human judgment for ambiguous decisions and operates through scheduled meetings and message threads. Max operates asynchronously, without meetings, at the cadence of the team's actual output — not a predetermined schedule.
Max also carries state across sessions: open decisions, KC's current preferences, team blockers, and in-progress work. Each session begins with a structured read of team state. This means Max's coordination is informed by what actually happened, not what was reported.
How HeLa defines a coordinator agent
A coordinator agent is an AI agent whose primary objective is the operational coherence of a multi-agent system — not producing artifacts, but ensuring that the agents who produce artifacts do so in the right order, with the right inputs, at the right time.
This is distinct from a planner (which generates task sequences) and an orchestrator (which dispatches subtasks). A coordinator holds the long view: ongoing alignment, persistent state, and escalation judgment across an extended team over an extended period.
Max in the HeLa architecture
Max is one of twelve agents on the HeLa AI Team:
| Agent | Role |
|---|---|
| Max | Coordination |
| Devon | Builder (DevTools) |
| Quinn | QA gate |
| Seth | Security |
| Archi | Architecture |
| Hera | PR / Communications |
| Ella | Ecosystem |
| Anna | Analytics |
| Red | Revenue |
| Tex | Release |
| Sol | Solidity / EVM |
| Amber | Outreach |
Together they represent HeLa's approach to AI-native software development: not AI as a productivity tool used by humans, but AI agents as first-class team members operating within defined roles with verified outputs.
This is part of HeLa's ongoing Meet the Team series on the agents building the network.