Organisational Intelligence
Case study — build log, n=1

Four Models, One Brief

A CEO-model orchestrating disposable frontier-model workers: the first pilot run, measured, not marketed.

The task

Fan an identical brief — write a hermetic unit-test suite for a 296-line pure-logic module (the queue arranger) — to 4 frontier models in parallel, each an agentic worker in its own git worktree. Grade objectively by mutation testing: seed bugs, count how many each suite catches.

Results

ModelMutation killTestsAssertsCostLatency
Kimi K3WINNER5/677136$0.65814s
Grok 4.55/65299$0.36163s
Qwen3.7 Max5/64971$0.11190s
Grok 4.35/61621$0.12102s

Kimi K3 merged — only suite to cover the side-effecting orchestration layer. Qwen3.7 Max: best coverage-per-dollar. Grok 4.3: most efficient, best for a quick check.

The honest finding

All 4 models tied at 5 of 6 killable mutants (7 seeded, 1 proven behaviourally equivalent by design — an initial-sort flip the greedy re-selection makes irrelevant, so no suite could have killed it) — with an identical blind spot: none pinned an exact score for a non-exempt aged piece.

Test count did not predict bug-catching power — Kimi K3's 77 tests beat Grok 4.3's 16 by breadth, not by a wider kill rate; both killed the same 5. The real differentiator was thoroughness vs. efficiency, not correctness.

Build notes

  • Muse Spark 1.1 was excluded — Meta gates it to US developers; we operate from HK.
  • Native-Windows quirk: the npm .CMD shim mangled multi-line prompts — fixed by calling the .exe directly.
  • The deny-by-default bash allowlist visibly blocked a worker's compound python && ls command mid-run — guardrail working.

This is a single measured run (n=1) — a build log, not a model ranking. Claude subagents remain our engineering default; this is the operational exit door and our own owned measurement, not a replacement.