andon-verifylisted

# andon-verify Never write to the ledger. Return a structured verdict plus evidence content; `andon-loop` persists it. Never default to strategy a (tribunal) as a starting guess -- route through the classifier below first, every time. ## Step 1: route the wire (never skip, never default) ``` python3 ${CLAUDE_PLUGIN_ROOT}/scripts/andon_core.py route-wire '<signals_json>' '<availability_json>' ``` `signals` are booleans you determine by reading the wire's contract: `is_structural_claim`, `is_numerical`, `is_property_invariant`, `is_verifier_of_verifier`, `is_autonomous_reliability`, `is_epistemic_claim`. `availability` are booleans you determine from the environment: `available_lsp_or_index`, `available_property_lib`, `available_confab`. The script checks triggers in a fixed order (e -> b -> f -> g -> d -> c -> a) and only reaches `a` when nothing else matches -- this *is* `references/wire-classifier.md`'s decision procedure, already executed, not merely described. If it reports `degraded_from`, that strategy's prerequisite was missing; it already re-routed to the next applicable one. **Never hard-fail this run because a strategy is unavailable** -- tribunal (`a`) has no external prerequisite and is the guaranteed floor. Full classifier rationale (why this order, what each trigger means in practice): `references/wire-classifier.md`. ## Step 2: run exactly the routed strategy's reference doc Do not duplicate strategy logic inline in this file or in your own reasoning --