h-diagnose

name	h-diagnose
description	Diagnose a concrete failure with rival-hypothesis testing. Stabilize the symptom, generate distinct explanations, test discriminating observations read-only in parallel, and rank by evidence while retaining losing rivals.

h-diagnose — Test rival explanations

Retrieve current FPF source only when pattern choice is material to the diagnosis. Mechanical reproduction, logs, and direct implementation probes do not need a ritual query. Inspect a known SourceID/UnitID directly; otherwise use mode="concern" and treat the returned candidate_set as incomplete navigation, not a selected pattern. Before relying on one candidate, inspect its exact identifier and direct pattern body. Keep several candidates live or abstain when the returned basis is insufficient. Never run a query after the diagnosis merely to manufacture source support for an already-chosen story.

Keep symptom, hypothesis, probe, observation, and verdict distinct. Include a rival that challenges the initial framing. Prefer safe parallel probes; label design-time inference separately from runtime evidence. Keep losing hypotheses with return conditions. Persist only on explicit request or when a named receiving use needs replay.