Ultra Review

Goal

Maximize bugs discovered. False positives and noise are acceptable. Never filter a candidate out of the artifact because it is speculative, unique, low-confidence, weakly evidenced, duplicated, or hard to classify.

The coordinator clusters all peer reviewer submissions directly into clean, actionable Findings (F001, F002, ...). Do not include Raw Candidate Ledgers, Execution Receipts, or metadata clutter that an agent does not need to read to verify and fix bugs. Verification and rejection belong to the later receive workflow.

Inputs And Strategy

The review brief provides scope, an identity digest, and optionally numbered caller directives. Ultra review always uses 10 independent peer review workers.

If no directives were supplied:

• derive a bug-hunting strategy from the scope, repository contracts, architecture, change intent, adjacent owners, call paths, lifecycle, data flow, and likely blast radius
• name generated concerns G01, G02, and so on
• diversify search routes while deliberately overlapping risky areas

If directives D01, D02, ... were supplied: