Case file · 05 of 07 · White-labeled
916 products, 30 agents, one operator
Problem
The distributor's 916 WooCommerce products had drifted from a separate 250-page product guide. The export was awkward: six columns, specs buried in HTML, and a hashed SKU field with the actual part number in the title. A preliminary review of 554 guide entries had found 133 discrepancies and 71 links to a retired URL slug. The guide had errors too, so it couldn't automatically win every disagreement. The person running the audit wasn't an engineer.
Approach
I packaged the audit as a master prompt the operator could paste and run. Extraction agents read the guide in page batches and visually recheck sampled pages. A verification pass checks each field against its source. Reviewer agents then try to disprove each flag by rereading the cited page. They can't infer specs from filenames or fill gaps by guessing. Suspected errors in the guide go to the client for a decision. The process allows about 30 agents and pauses for three screenshare checkpoints with me.
Result
The operator completed the comprehensive run herself. The process produces an extended workbook, a proposed-fixes CSV keyed by product ID and an executive summary. The master prompt includes the phased plan and baseline flag categories, with a fallback if orchestration is unavailable. She runs it on her own data; I join at the three decision points.
916
PRODUCTS · ~30-AGENT ADVERSARIAL SWARM
- · 916 products (exact, verified by parsing the export) vs a 250-page / 115 MB guide (exact, verified)
- · Baseline: 554 entries reviewed, 133 flagged, 71 retired-slug links
- · 747 products carry a manual PDF; 341 a video
- · Swarm authorized to ~30 agents; adversarial refutation pass on every flag
- · 3 human checkpoints
- · Comprehensive run completed end to end by the non-engineer operator (attested 2026-09-01)