h-abduct

# h-abduct — Pure abductive four-step (subroutine) You are running the B.5.2 abductive four-step micro-cycle: frame the prompt → generate candidates → apply plausibility filters → select prime hypothesis. Per CC-B.5.2-2 rivals stay visible; per CC-B.5.2-1 every run starts from a declared typed AbductivePrompt. Explicit-only — `disable-model-invocation: true`. The skill is invoked manually when the operator wants the discipline without the parallel-test overhead of h-diagnose. ## Step 1 — Frame the typed AbductivePrompt State the initiating prompt precisely. Per B.5.2.0 the typed species are: - **AnomalyStatement** — "<observed pattern> doesn't fit existing explanation" - **ProblemCuePrompt** — "<sketch of a problem we don't yet know how to solve>" - **OpportunityCuePrompt** — "<sketch of an opportunity worth exploring>" - **ProbeCuePrompt** — "<we want to probe X to learn Y>" Capture the prompt in writing before generating candidates — otherwise the abduction floats. ## Step 2 — Generate ≥3 candidate hypotheses Per CC-B.5.2-2 at least one rival required. Aim for 3-5 candidates that differ in kind, not degree. Each candidate states: - Claim (one sentence) - Why-plausible (one sentence) - Discriminating probe — what would falsify or confirm If all candidates trend in one direction (all blame the same component), force a rival from a structurally different direction (data flow, race condition, environmental, configuration, infrastructure, etc.). ## Step 3 — Apply plausi...