How you conduct
You conduct like The Soloist: Delivery is your home turf, with 59 agents this window.
Brilliant solo, low orchestration — the anti-Conductor. Time to pick up the baton.
Your blend
One score per tool
Each harness is scored only on what it can structurally observe (κ = observable capacity) and ranked against others on the same tool.
The fleet
* Peak parallelism is a hardware ceiling — concurrency is capped by the machine's CPU cores, not by skill. The scale of the operation is the fleet total above.
Your working style, read from the evidence
A metacognitive mirror built from your own structural signals — never a personality quiz. deterministic
You conduct like The Soloist: Delivery is your home turf, with 59 agents this window.
Your edge is Delivery — your own signals show it (verification at 8%, a fleet of 59).
The most exciting move ahead is Tooling: it's where you have the most open room, and a single new habit grows fast there.
Mastery zone
Competent
Most room to grow
Tooling is where you have the most open room ahead (mcp_servers=0). One step here next window grows more than reinforcing what's already strong — it's the most generous frontier you have right now.
mcp_servers=0
Artisans · deep-focus IC
Complements The Toolsmith, The Deliberate
Rubs against Parallel Maestro
Your next mission
Over the next 30d, raise mcp_servers from 0 to 2 and unlock the Toolsmith archetype.
Auditable, unlocked from your signals
Each pillar score, with the evidence that sustains it.
59 agents dispatched across 23 workflows, peaking at 1 running at once.
8% of editing sessions verified, across 1 verification modes, with 6 human sign-offs.
0 distinct tools in play, 0 advanced tool moves, 0 external systems via MCP.
25 pull requests and 68 files changed, across 4 codebases.
33 context compactions and 13 API errors over 13 sessions.
3 self-scheduled loops and a longest hands-off run of 8 agent steps.
Which agent harnesses this profile draws on — and what each one's journal can structurally prove. Disclosure only; it never changes the score.
| Harness | Orch | Verify | Tools | Ship | Craft | Auto |
|---|---|---|---|---|---|---|
| Claude Code | full | full | full | full | full | full |
A "partial" or "none" cell means the harness simply doesn't record that signal — the pillar is measured from what it does record, never penalised for what it can't.
Last 30 days
The raw signals behind the score — plain language, no jargon.
Archetype
The Soloist is brilliant alone but delegates little — the raw skill is there; the fleet isn't yet.
Deep hands-on sessions with little delegation. The next unlock is orchestration: the same talent, multiplied by a fleet.
Ecosystem
Beyond the core toolkit, 0 external systems — mail, browser, calendar, cloud — are wired in via MCP and driven mid-workflow, alongside 0 distinct tools and 0 advanced tool plays like tool-search and skills.
The human read
What these signals say about how this person works.
59 AI agents conducted through 23 workflows in 30 days. This is someone who multiplies their output by directing machines — not someone typing faster.
8% of editing sessions end in verification, and 6 moments paused for explicit human sign-off. Work arrives checked.
25 pull requests and 68 files changed across 4 codebases — the fleet lands as concrete, reviewable work.
3 scheduled loops and a longest hands-off run of 8 agent steps — autonomy built on checks, not on faith.