Orchestrator-workers vs peer teams

Red-team lab (Module 9, L9.3): one decider and one queue. Twelve serial dispatch decisions at two ticks each finish the run in 27 ticks, and 60 of the crew's 108 worker-ticks are spent waiting for a decision -- only 33.3 percent of the shift did any work. Nothing errors; the decider is correct, careful and serial, and serial means the queue at one node is the schedule. Four peers finish the same work in 13 ticks with 4 disputes adjudicated at 4 ticks each (16 of 52 booked worker-ticks), but give the team one adjudicator instead of one per worker and it takes 19 ticks: the serial decision moved, it did not disappear. With one adjudicator the hierarchy wins from 7 disputes (58.3 percent), and at 80 percent the peer team takes 43 ticks against 27. The other clock decides too: at 4 disputes four peers lose once one adjudication costs 8 ticks. Then red-team the peer protocol: two peers, opposite verdicts on the same artifact, first-to-arrive wins, and 6 of 10 runs ship what the strict peer would have failed. Harden it with the three-step contract -- verifier, exception file, cheaper-to-verify -- which resolves 10 of 10, because averaging a PASS and a FAIL is 0.5 and a 0.5 threshold ships PASS. At 120 tasks and 40 workers the hierarchy takes 243 ticks against an ideal of 9.0. In-memory only; scripted ticks, no threads, model or provider call.

This Harness Engineering lesson is part of a paid plan. Sign in with a plan that includes this course to read it.