Connect
Roles and teams
This page is for running several roles together. What a single role is, is on Agents; how to write one is on Writing a role.
Five kinds of seat
Every role has a tier that says what kind of seat it takes.
| tier | What the seat does |
|---|---|
orchestrate | Hands out work and reports between rounds. Does not do the work itself. |
execute | Does one piece of work, on a separate branch. |
verify | Checks the work and never edits it. A seat that could both change and approve its own work would not be a check. |
deliver | Takes checked work out: merging, deploying, tagging a release. |
knowledge | Writes what the others read and keeps the graph in order. Proposes fixes rather than applying them. |
Some steps belong to a person whatever the seat. Each role lists its own in person_only.
Teams and handoffs
A role can carry a team and a team_role (lead, coordinator or member). In the app, Agent in the top row of the sidebar groups the roles by team with the lead first. The Vinc team itself runs 23 roles in six teams: Program Office, Product Engineering, Design, Content and Marketing, Quality and Security, and Platform and Release.
Handoffs between roles are links between role nodes. The sidebar shows them under each role.
| In the sidebar | Link | Meaning |
|---|---|---|
| from | prerequisite_of into this role | Another role finishes before this one starts. |
| then | prerequisite_of out of this role | This role finishes before another starts. |
| beside | relates_to | Works alongside, with no order. |
Running several at once
Split the work into pieces that do not need each other's output, and hand each piece to one role. The orchestrator gives them out, each role works on a separate branch, and the round ends when every piece has reported back. A piece is done not when its files change but when its result is written back where the next round can read it.
Which model a role runs on
A role names a rung, not a model, and one table ties the rungs to models. That way every role moves together when the models change. Pick the rung by how costly a wrong answer is, not by how big the job is.
| rung | Model today |
|---|---|
strongest | Claude Fable |
strong | Claude Opus |
fast | Claude Sonnet |
cheapest | Claude Haiku |
Hosts other than Claude Code choose their own model from the rung.
What a role writes back
After a run, a role writes an episode saying what happened, records for what it learned, and a decision whenever it changed a rule. A run that produced something and wrote nothing back is not finished: the next run cannot see it and hits the same wall again. To write back, the host has to reach the graph (Connect over MCP).