auto-decorrelation — Cross-Family Verifier Recruitment

The lever for catching a model's blind spots is decorrelation, not repetition — a model cannot find its own family's flaws by repeating itself. FH's adversarial verification (Axis-2 challenger) dispatches in-session at the session tier, same family as the governor. When frontier CLIs are installed and a local GPU box is live, leaving them idle wastes the one thing that actually raises the verification ceiling. This skill recruits a cross-family verifier for load-bearing changes — and degrades honestly when none is available.

It is a thin recruitment-and-degrade policy that REUSES existing machinery: agent-composer does the actual dispatch, cross-ecosystem-synergy-detection inventories tools, token-budget-gate gates spend, the headless CLI patterns and the floor-tier canary already exist. Net-new = the discovery + the family-diversity recruitment + the degrade ladder only. (A composing policy skill — it fans out to several callees, so its token floor is higher than a leaf skill by design; this is composition, not reinvention, and the chain is return-path-closed — Step 5 gates acceptance on the callee's back-trace.)

Triggers