Challenge apparent convergence with isolated lead explorers

[maajix]

Parent

#5

What to build

Before reporting an apparently converged full campaign, dispatch isolated Surface Archaeologist, Abuse-Case Adversary, and Boundary Breaker explorers; quality-gate their structured leads and reopen the campaign whenever a unique supported lead appears.

Acceptance criteria

• Apparent convergence schedules all three explorer lenses by default.
• Every explorer receives the same material campaign digest without peer reasoning or results.
• Explorer output requires a concrete subject, falsifiable hypothesis, supporting observation, next test, provenance, priority, and safety requirements.
• Duplicate, unsupported, already-tested, out-of-scope, and prohibited ideas are rejected and do not count as progress.
• One accepted unique lead invalidates the challenge and reopens normal campaign work.
• After reopened work becomes terminal, the challenge runs again against the updated material digest.
• A zero-lead challenge matching the current digest permits the reporting transition.
• Challenge bookkeeping does not alter the material digest it certifies.

Blocked by

• Guarantee fair recon coverage across assets #10 — Guarantee fair recon coverage across assets
• Escalate resistant hypotheses to a bypass specialist #11 — Escalate resistant hypotheses to a bypass specialist
• Re-evaluate kill chains after every material event #12 — Re-evaluate kill chains after every material event

[maajix]

Implemented in f951aa5 on branch agent/autonomous-campaign-coordinator. Full Python (159) + shell regression suites green.