optimize technical truth

This commit is contained in:
team 1
2026-04-29 11:48:30 +02:00
parent d3d94d023e
commit 123d5d4020
3 changed files with 28 additions and 0 deletions

View File

@@ -0,0 +1,13 @@
# RetrieX answer grounding strictness fix
Patch scope:
- Strengthens prompt/grounding rules for technical product-selection answers.
- Keeps Retrieval, Shop Search, AgentRunner, SSE, and scoring untouched.
- Prevents confident suitability claims from weak shop hits or query wording.
- Explicitly prevents treating p-Wert/m-Wert/minus m-Wert as pH/pH-Wert unless the same source says pH or pH-Wert.
- Forces short, source-close answers when evidence is uncertain.
Expected effect for cases like:
"suche einen testomat der ph messen kann"
RetrieX should not confidently turn p-Wert into pH-Wert, should not invent measurement principles/benefits/alternatives, and should say when technical suitability is not securely proven by the provided RAG/shop records.