---
title: "Coordination types · Cork"
description: "How Cork works out your coordination type, streak and badges: from metadata only (when your agents worked, how many at once, collisions and handoffs), never code or prompts, over at least two weeks, recomputed every Monday."
canonical: "https://corkcli.com/types"
last_updated: "2026-11-13"
---

# Coordination types

Cork gives everyone who works with agents a type: how they run them, read from what Cork already records about the work. Here is every rule, exactly as the server applies it. **Metadata only**, never code, prompts or message text. **Weeks of it**, so one busy afternoon makes no one a Conductor. **Yours to share**: nobody else sees your type unless you turn your public profile on.

## What it reads

- When each of your agent sessions reported an edit or a billed turn, and its agent hours.
- How many messages and handoffs you and your agents sent to agents through Cork. Counted, never read.
- The collisions Cork stopped on your agents, and what each agent did next.
- Tokens saved, net of what Cork's own briefings cost, as on the Savings page.

Nothing here reads a file, a prompt or the words of a message. The same rows already feed the [data Cork keeps](https://corkcli.com/data); nothing new is collected for this.

## When you get one

Your type is worked out from the **last 4 full weeks** (ISO weeks, Monday 00:00 UTC), once you have had agent work on **at least 6 days, in at least 2 of those weeks**. It is worked out again every Monday, so it changes when your habits do. Until then the dashboard shows how far along you are.

## The types, in order

The rules are tried in this order over the 4 weeks added together; the first that holds is your type.

1. **Air Traffic Control** (rare): Five agents in the air, work routed between them, and every near-miss handled. Rule: 5 or more agents at once at some point; 3 or more at once for at least a quarter of working time; 20 or more messages or handoffs to agents; and after at least 90% of 10 or more settled collisions, the agent adapted or waited.
2. **Clean Sheet** (rare): A month of three agents side by side, and not one collision. Rule: Agent work in each of the 4 weeks; 40 or more agent hours; 3 or more agents at once for at least 20% of working time; and no collisions at all.
3. **Cowboy**: Rides into busy code, collides often, and rarely changes course. Rule: 8 or more collisions, at least one per active day; and after fewer than half of 5 or more settled collisions, the agent adapted or waited.
4. **Conductor**: Runs several agents at once and routes work between them. Rule: 2 or more agents at once for at least 40% of working time, and 10 or more messages or handoffs to agents.
5. **Good Neighbor**: Works where others work, and gives way when a teammate's change lands first. Rule: 5 or more collisions; and after at least 75% of 5 or more settled collisions, the agent adapted or waited.
6. **Swarm**: Many agents at once, each left to its own lane. Rule: 3 or more agents at once for at least 20% of working time.
7. **Duet**: Two agents side by side, most of the time. Rule: 2 or more agents at once for at least 40% of working time.
8. **Relay**: One agent at a time, with work passed from session to session. Rule: 3 or more handoffs.
9. **Solo Act**: One agent at a time, start to finish. Rule: 2 or more agents at once for less than 15% of working time.
10. **All-Rounder**: A bit of everything: no one habit stands out yet. Rule: None of the above.

## The words the rules use

- **At work**: Each edit or billed turn an agent session reports to Cork counts that session as at work for 5 minutes either side. A subagent works inside its session: one agent, not two.
- **Working time**: The time at least one of your agent sessions was at work, counted within each workspace.
- **N or more agents at once**: The share of working time with N or more of your sessions at work together. The most at once is the peak.
- **Messages and handoffs**: Messages you or your agents sent to agents through Cork, counted, never read. A handoff is one sent as work for its recipient, or a message anchored to code (handed to whoever is on it).
- **Collisions**: Collisions Cork stopped on your agents: a write from a copy that lacked a teammate's change, refused before it landed, or two agents headed for the same code, stopped before either wrote over the other. Repeats of one agent on one file within ten minutes count once, exactly as the Waste report counts them.
- **Settled collisions**: What the agent did next, settled from what its session sent: adapted (it took the teammate's change in), waited (it let the other finish), overrode, or abandoned. A hold on an owner's standing decision is not a collision.
- **Agent hours**: The time agents were at work, as billing meters it: the model thinking and writing. A tool's run time, typing and idle time never count.
- **Active day**: A UTC day with an edit or a billed turn from one of your agents.

## Streaks

A streak counts days in a row with agent work through Cork (an active day, in UTC). A Saturday or Sunday without work neither counts nor breaks it, and today does not break it before it is over.

## Badges

Counted over everything Cork has kept for you, up to a year back.

- **First catch**: Cork stopped a collision on one of your agents.
- **Ten catches**: 10 collisions stopped on your agents.
- **A hundred catches**: 100 collisions stopped on your agents.
- **First handoff**: You or your agent handed work to another agent: a handoff, or a message anchored to code.
- **Three at once**: 3 of your agents at work at the same time.
- **Five at once**: 5 of your agents at work at the same time.
- **Full week**: A 5-day streak.
- **Twenty days**: A 20-day streak.
- **A hundred hours**: 100 agent hours.
- **Gave way**: After 10 collisions, your agent adapted to the teammate's change or waited for it.
- **Full house** (rare): 3 or more people of one workspace with agents at work in the same hour, you among them. Unlocks once someone you invited joins.

## Who sees what

- Your type, card, streak and badges: you, on your dashboard, and in your own Monday email.
- A public profile with your card: **off until you turn it on** in Profile settings. Off again, the page is gone.
- Your workspace's leaderboard: your teammates see your counts there (collisions caught, handoffs, streak), never your type. Only numbers above zero are ranked. It opens once a teammate accepts an invite.
- A signed report: a JSON file of your type and numbers you can download and hand to anyone. Cork signs it with its server key; whoever has it can check it was not changed by posting it to `/api/habits/verify`.

[Documentation](https://corkcli.com/docs) · [What Cork sends](https://corkcli.com/data) · [Privacy](https://corkcli.com/privacy) · [Pricing](https://corkcli.com/pricing)

This page in HTML: https://corkcli.com/types