patch 17c

config/retriex/prompt.yaml

@@ -209,11 +209,6 @@ parameters:
         - ph-indikatoren
         - ph indikatoren
 
-      direct_main_device_request_patterns:
-        - '/\b(welcher|welches|welche)\s+[^?.!,;]{0,40}(testomat|messgerät|messgeraet|analysegerät|analysegeraet|gerät|geraet|analysator)\b/u'
-        - '/\b(suche|finde|empfiehl|empfehle)\s+[^?.!,;]{0,40}(testomat|messgerät|messgeraet|analysegerät|analysegeraet|gerät|geraet|analysator)\b/u'
-        - '/\b(testomat|messgerät|messgeraet|analysegerät|analysegeraet|gerät|geraet|analysator)\s+[^?.!,;]{0,40}(messen|misst|überwachen|ueberwachen|kann|für|fuer)\b/u'
-
     measurement_evidence_guard:
       intro_rules:
       - '- This block is generated from the current user question and is stricter than broad product-selection wording.'
@@ -434,8 +429,6 @@ parameters:
       - '- Only use shop price, URL, product number, or availability for the main product when the shop result clearly matches that same main product.'
       - '- If the matching shop item appears to be an accessory, reagent, consumable, set, or kit, keep it separate and do not present its commercial fields as the
         main device.'
-      - '- Use the Requested role, Inferred role, and Role compatibility fields independently for each SHOP PRODUCT RECORD; never transfer the role of an accessory, indicator, reagent, kit, or set to a different shop record.'
-      - '- If a SHOP PRODUCT RECORD has Inferred role: main_device, do not describe that same product as accessory_or_consumable merely because other shown records are accessories or consumables.'
       - '- If the commercial match is uncertain, say that commercial details for the main product are not clearly available in the provided shop results.'
       - '- If no price is shown for a shop item, omit the price instead of writing 0,00 €, free, kostenlos, or a guessed price.'
       - '- For every shop hit shown in the answer, copy the exact shop product name verbatim from the same SHOP PRODUCT RECORD as the item heading.'
@@ -486,6 +479,8 @@ parameters:
       - '- Use shop data as highest priority for current commercial fields: price, availability, URL, current shop-visible naming, and explicitly shop-visible product suitability for product-selection questions.'
       - '- Use retrieved knowledge as highest priority for technical matching, thresholds, measurement principles, and technical explanation when it contains a matching product or fact.'
       - '- If retrieved knowledge is silent or only contains unrelated products, but live shop results explicitly match the requested parameter/application, use the shop results and do not answer with a negative RAG-only conclusion.'
+      - '- If the user asks for Schwimmbad, Schwimmbecken, Pool, or typo-like pool wording, a product may only be recommended for that application when the same RAG or SHOP PRODUCT RECORD explicitly names that application. Chlor measurement alone is not proof of swimming-pool suitability.'
+      - '- If a product record proves Chlor measurement but not Schwimmbad, Schwimmbecken or Pool use, say exactly that distinction and avoid recommendation wording such as empfiehlt sich, geeignet für Schwimmbad, or Anwendung im Schwimmbad.'
       - '- For product-selection questions, a shop result proves technical suitability only when the same SHOP PRODUCT RECORD explicitly states the requested measurement parameter, application, or compatibility. Search ranking, generated query terms, generic category matches, and similar wording are not proof.'
       - '- If the requested parameter appears only in the generated shop query, metadata, unrelated highlights, or another product record, treat suitability as unverified and say that the shop hit requires technical verification.'
       - '- Do not convert p-Wert, m-Wert, minus m-Wert, alkalinity, acid capacity, or other water-treatment parameters into pH or pH-Wert unless the same source explicitly says pH or pH-Wert.'
@@ -547,6 +542,8 @@ parameters:
         entry explicitly connects them.'
       - '- If several devices or indicators are present, keep each device-indicator-range assignment separate and do not transfer an indicator from one product to
         another.'
+      - '- For Testomat CAL or Testomat 2000 CAL threshold/range questions, do not answer with Testomat 808 indicator ranges or the generic 0,02 °dH to 5 °dH range unless a CAL source record explicitly contains that exact assignment.'
+      - '- Do not use phrases such as typical monitoring range, typical range, or common range for a named product when the provided source only proves another product variant or does not explicitly state the named product range.'
       - '- If the source states only a threshold function, do not expand it into broader control logic.'
       - '- If a detail is not explicitly stated in the provided sources, say so plainly.'
       - '- Prefer short, source-close sentences over explanatory expansion.'