Teams: the org chart is the interface

Until now a team was a label — a team: string on agent YAML that grouped cards on a page. Nothing above the team existed: no single agent that ran the whole workspace, no human on the hook for a team's output, and no way to ask "how is the quarter going?" and have the answer assembled across every team. This release breaks that ceiling. Teams become rows in the database with a lead and an accountable owner, a workspace lead sits above them, and the org chart stops being a diagram you keep in your head — it's the page you work from.

What's new

• Teams are first-class. A new team table (org- and project-scoped, flat by construction) carries each team's slug, name, lead agent, and accountable human. Authoring is pure workspace config: drop a teams/<slug>.yaml with name, lead, and optionally accountableUser, and workspace:apply does the rest.
• A workspace lead above the teams. workspace.yaml gains top-level lead: and accountableUser: — one agent that runs the whole workspace, one human who owns it by default.
• The org-chart page. /dashboard/teams opens on the workspace-lead band ("Ask how the quarter is going" deep-links straight into chat), with team cards beneath and a "not on a team yet" strip so no agent vanishes. Every owner row states its provenance in visible text — "Name (workspace default)" when a team inherits the workspace owner rather than naming its own.
• Team detail pages. /dashboard/teams/<slug> mirrors the agent-profile layout: owner and lead in the rail, the member roster lead-first, and a plain-language approval boundary derived from the team's wired skills — "reads run freely / N skills wait for your approval."
• The workspace lead can actually consult its teams. In chat, team leads are merged into the workspace lead's subagents, so a quarter question fans out per team and degrades honestly ("no lead yet") instead of silently skipping anyone. Workspace-lead missions resolve their roster the same way.
• Chat defaults to the workspace lead. /dashboard/chat now opens on the workspace lead with an agent-aware greeting and composer placeholder; the agent switcher lists only the workspace and team leads — specialists are reached through their lead.
• A bundled sample workspace. "Meridian Outdoor — Revenue" ships in the box: one workspace lead, four teams, thirteen agents, two operations. The empty-state seed button loads it through the exact same apply pipeline as workspace:apply, first-run only, with your email injected as the accountable owner.
• teams_list over MCP. External agents (Claude Code included) can read the org chart — workspace lead, every team, rosters, and owner provenance — through the MCP server.

Who's accountable for what

Why we built it

The v1.42 teams release proved the shape — one lead you brief, specialists it dispatches — but stored it as strings on agents. That worked for one team; it fell apart the moment a deployment had four. Who do you talk to about everything? Which human answers for the Deal Desk's output? Real organizations answer both questions structurally, so Vocion now does too: the team is a row, the lead is a column, and accountability is resolved — explicit or inherited — rather than implied. And because teams are authored YAML, the write path stays what it always was: edit the workspace, apply, audit. The MCP surface is read-only by design for the same reason.

Where to find it

Open /dashboard/teams — if the workspace has no teams yet, the one-click sample seed will stand up Meridian Outdoor so you can brief a workspace lead within a minute of upgrading. Full authoring reference in the Teams docs.