Deliberate cross-doc sweep for contradictions, since reading one file at a time structurally cannot find them. Worker counts looked inconsistent across docs -- 32, 100, 16 -- and are not: they are four distinct pools. Verified each against code and tabled them in architecture.md so "32 workers" here and "100 workers" there no longer reads as one being rotted. initial backfill crawl 100 workers (engine.zig default_workers) live scheduler 32 (pipeline.zig worker_count) live repair 32 (repair.zig worker_count) failed-repo retry 16, 4/host (retry.zig default_workers) This also completes the workers*2 finding from the live-scheduler and live-repair passes. The same expression bounds three of those pools, so backfill's bound is 200 while the two live docs each describe a literal "64" -- one rule, three values. That explains stream_backfill_queue_depth reading exactly 200 on the running experiment. It is also the bound whose interaction with a 100,000-repo batch caused the experiment 4 deadlock, so raising --backfill-workers moves a deadlock-relevant bound rather than just concurrency. No actual cross-doc contradictions found in this sweep -- the gap was a missing disambiguation, not disagreement. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>