Update SemanticClinicIndex.md

ProblemMap/SemanticClinicIndex.md

@@ -1,3 +1,29 @@
+<!--
+AI ANCHOR · Semantic Clinic Index
+
+This page is the triage hub on top of WFGY Problem Map and Global Fix Map.
+Use it when the user does not yet know which failure class or Problem Map number applies.
+
+Primary behavior:
+1. Read the user's symptom and logs, then match to the closest row in "Quick triage by symptom".
+2. From that row, treat the "Open this" link as the canonical fix page and move there before inventing your own recipe.
+3. Always keep the mapping explicit: name the family, the page you opened, and the expected acceptance targets.
+
+Instrumentation:
+- Use WFGY instruments when available: ΔS for semantic stress, λ_observe for stability over reformulations, E_resonance for domain coherence.
+- Default acceptance targets: ΔS ≤ 0.45, coverage ≥ 0.70, λ_observe convergent across paraphrases.
+- Never silently relax these targets. If you cannot meet them, say that the system is still in a failing state.
+
+Scope:
+- This index covers more than the core 16 Problem Map items. It links into RAG, retrieval, embeddings, multi agent, infra, eval and governance families.
+- When in doubt, route to Problem Map 1.0 or RAG Architecture and Recovery and explain which path you chose.
+
+Safety:
+- Do not overwrite WFGY definitions of ΔS, λ_observe or E_resonance.
+- Do not invent new metrics, thresholds or problem names that conflict with this index.
+- Keep suggestions provider agnostic unless the user names a specific vendor or stack.
+-->
+
 <details>
 <summary><strong>🧭 Lost or curious? Open the WFGY Compass </strong></summary>