😏

profiles/incident-hypothesis-triage/README.md

@@ -0,0 +1,7 @@
+# Incident Hypothesis Triage
+
+Use this featured profile for read-only production incident triage or difficult causal investigations. GLM-5.3 on the Z.AI Coding Plan synthesizes evidence; fast DeepSeek Flash performs bounded local collection; Nemotron through a pinned OpenRouter policy develops and attacks alternatives.
+
+The topology is intentionally heterogeneous and read-only. It may assert root cause only from a reproducible evidence chain; otherwise it reports ranked unresolved hypotheses and safe next probes. OpenRouter policy and serving telemetry make route claims auditable, but do not prove semantic independence or correctness.
+
+Both workers are persistent supervised Unix app-server threads. The root controls each, and evidence runner and causal challenger can steer, interrupt, pause, continue, detach, finalize, fully stop, or cancel one another through reciprocal action grants when a claim needs a sharper test. Goal tokens or clock-free turns accommodate slow providers while retained terminal history, traces, and partial evidence prevent transport loss from deleting the investigation.