optimize technical truth
This commit is contained in:
13
RETRIEX_ANSWER_GROUNDING_STRICTNESS_FIX_README.md
Normal file
13
RETRIEX_ANSWER_GROUNDING_STRICTNESS_FIX_README.md
Normal 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.
|
||||
Reference in New Issue
Block a user