WeAreDevelopers × BAND · Dark Factory · Pocketful · run report
Proof before ship.
Five Claude Code seats in BAND Desktop built a wallet service from one dispatched task. Only the builder writes product code; an independent gate accepts nothing until an adversary has attacked the same revision. 4/4 ACCEPTED
4/4stages accepted by the gate
7defects caught before acceptance
0oracle mismatches in 153,610 comparisons
834seat turns across five seats
$123.87API-equivalent cost, measured
The run, seat by seat
gate REJECTgate ACCEPThuman message (5)seat commithatched = stalls, time compressed
Every human word, on the record
0.2%of 2,312 room messages were human
220human words after the dispatch
0technical instructions
~9 hworking time for 4 stages; stalls shown, not hidden
#
When (CDT)
Trigger, visible in the room
What the band did next
1
Oct 4 03:04
the dispatch: task, specs, stance (737 words)
stage-1 analysis committed 22 min later
2
Oct 4 13:12
builder: "You've hit your session limit" → resume note, 53 words
same handoff re-sent; stage 1 built 18 min later
3
Oct 4 21:14
analyst: "You've hit your session limit" → resume note, 54 words
stage-3 analysis committed 23 min later
4
Oct 4 23:28
adversary committed its report but never messaged the gate → 51 words
report relayed; the gate REJECTED on its own evidence
5
Oct 5 00:58
same missed handoff in round 2 → owner acceptance, 62 words
the gate issued its own ACCEPT one minute later
Remove any note and the code does not change, only when it was written. Each one maps to a generic fix (watchdog after usage limits; coordinator and gate check the repository for an overdue report) that would make the next run one message. Details: FACTORY.md §6.
Work was shared
adversary23328%
builder20625%
gate16820%
analyst14718%
coordinator8010%
Seat turns from each seat's own Claude Code session log. No seat carries the run.
What review caught
Stage
Defect
Found by
Outcome
1
Crash (heap exhausted) under 50 concurrent large requests
adversary, reproduced by gate
REJECT → fixed
1
Large bodies stalled the server past the 5 s budget
adversary, reproduced by gate
REJECT → fixed
1
Over-long idempotency key: 400 instead of 422
adversary, reproduced by gate
REJECT → fixed
1
The crash fix made the service refuse its own export after ~28,000 payments
adversary round 2, gate
REJECT → fixed → ACCEPT
3
Statement snapshots leaked memory until the service died
adversary, reproduced by gate
REJECT → fixed
3
Expired seeded hold disagreed between historical and current views
adversary, reproduced by gate
REJECT → fixed
3
Valid RFC 3339 forms (lowercase t/z, leap second) rejected