optimize technical truth

src/Config/PromptBuilderConfig.php

@@ -438,6 +438,7 @@ final class PromptBuilderConfig
             '- 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.',
             '- Never place a shop URL, product number, price, or availability below a different heading taken from retrieved knowledge.',
             '- If technical RAG knowledge and shop records cannot be matched with high confidence, use separate sections: Fachliche Einordnung and Shop-Treffer.',
+            '- For uncertain technical suitability from shop hits, use a short section like "Shop-Treffer (technische Eignung nicht sicher belegt)" and list only exact shop fields. Do not add a technical explanation or recommendation.',
         ]);
     }
 
@@ -461,6 +462,7 @@ final class PromptBuilderConfig
             '- Prefer exact values, ranges, thresholds, compatibility notes, and application areas over general explanation.',
             '- For direct follow-up questions about an indicator, value, threshold, or device, answer the resolved mapping first before any table or explanation.',
             '- If the sources only support a negative finding, output only that negative finding and do not add speculative alternatives.',
+            '- For product-selection answers, keep the answer minimal: suitable product if explicitly supported, exact evidence, current shop fields if same product identity is clear. Do not add sections for Vorteile, Einsatzbereiche, Messprinzip, or Hinweise unless directly asked and explicitly sourced.',
         ]);
     }
 
@@ -532,6 +534,9 @@ final class PromptBuilderConfig
             '- 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.',
+            '- 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.',
             '- When shop results are present and relevant, include current price and the actual URL if available.',
             '- If the shop data does not provide a positive price for a result, do not output any price for that result.',
             '- Do not let accessories, bundles, or service items override a technically better product match unless the user explicitly asks for them.',
@@ -566,6 +571,8 @@ final class PromptBuilderConfig
     {
         return $this->getStringList('fact_grounding.technical_rules', [
             '- For technical product questions, answer primarily with explicitly stated facts.',
+            '- For measurement-parameter questions, do not treat similar or neighboring abbreviations as equivalent. In particular, p-Wert is not pH-Wert unless the source explicitly says pH or pH-Wert.',
+            '- Do not invent or infer measurement principles, methods, calibration functions, benefits, advantages, application areas, or alternative products from product family names, search rank, or shop query wording.',
             '- Behave like a technical documentation assistant, not like a sales advisor.',
             '- Keep interpretations minimal and do not generalize application areas beyond the provided sources.',
             '- Do not describe benefits, consequences, risks, or operational outcomes unless they are explicitly stated in the sources.',