optimize technical truth

config/retriex/prompt.yaml

@@ -27,6 +27,20 @@ parameters:
         kit, consumable, or service item.
       - If a shop result has no price field, do not state a price for it.
       - Never interpret a missing price or a zero price as free, kostenlos, gratis, or available for 0.00 EUR.
+      - Treat every SHOP PRODUCT RECORD as atomic: exact product name, product number, price, availability, URL, image, description, and metadata must stay together.
+      - When outputting a shop item, use the exact shop product name from that same SHOP PRODUCT RECORD as the heading. Never use a retrieved-knowledge device name as the heading for a different shop URL or product number.
+      - If a technical device from retrieved knowledge and a shop record are not clearly the same exact product identity, separate Fachliche Einordnung from Shop-Treffer instead of merging them.
+      - Use the product role fields in each SHOP PRODUCT RECORD. If the user asks for a main device/system, a record classified as accessory_or_consumable is not a primary product candidate.
+      - For main-device/system requests, do not let a single accessory, reagent, indicator, kit, set, or consumable shop hit dominate the answer. Mention it only as a separate non-primary shop hit if useful.
+      - If a shop record says Role compatibility with request is not compatible, do not use its description, price, URL, or product number as evidence for the requested main device/system.
+      record_header_template: '[%d] SHOP PRODUCT RECORD'
+      exact_product_name_label: Exact shop product name
+      requested_role_label: Requested product role
+      inferred_role_label: Inferred shop product role
+      role_compatibility_label: Role compatibility with request
+      role_mismatch_notice: 'Role mismatch: this record is kept only as a separate shop hit; do not use its description, price, URL, or product number as the main device/system answer.'
+      atomic_record_note_lines:
+      - 'Record boundary: all fields below belong only to this exact shop product record.'
       overflow_notice_template: Only the top %d ranked shop results are shown here out of %d total results.
       fields:
         product_number_label: Product number
@@ -68,6 +82,8 @@ parameters:
       - '- For product-selection questions such as which device can measure or monitor a parameter, use relevant live shop results as a fallback when retrieved knowledge does not identify a matching product.'
       - '- If shop results are present, use them afterwards to add current price, availability, and the actual URL.'
       - '- Do not let bundles, accessories, or service items override a better technical match unless the user explicitly asks for them.'
+      - '- For requests asking for a main device, measuring device, measuring installation, analyzer, system, or plant, never make an accessory/consumable shop record the headline recommendation.'
+      - '- If all shop hits are accessory/consumable records while the user asked for a main device/system, answer from retrieved technical knowledge first and say that the shop hits do not clearly contain a matching main device.'
       technical_rules:
       - '- For technical questions, answer the exact requested fact first and keep it as the main answer.'
       - '- If one source chunk contains both the best matching value and nearby comparison values, use the nearby values only as context and do not include them unless the user asks for comparison or alternatives.'
@@ -80,6 +96,7 @@ parameters:
       - '- Never present missing or weak evidence as proof that a product, value, accessory, or suitability does not exist.'
       - '- A negative answer is allowed only when the provided sources explicitly support that negative finding for the asked scope.'
       - '- If several products, parameters, or accessories could match, ask one focused clarification question instead of guessing.'
+      - '- If the retrieved technical answer identifies devices but shop data only contains accessory/consumable hits, do not present those shop hits as the answer to a device/system request.'
       - '- For risky or binding product selection, state that sales or support should verify the application before a final selection.'
       without_shop_check_rules:
       - '- If the question is product-related and no live shop check was performed in this run, do not make a portfolio-wide negative statement such as "there is no product".'
@@ -120,10 +137,12 @@ parameters:
         facts.'
       - '- Keep price, availability, and URL on separate lines when they are present.'
       - '- 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.'
+      - '- If a SHOP PRODUCT RECORD is classified as accessory_or_consumable while the requested product role is main_device_or_system, do not use that record as a product recommendation headline.'
       - '- 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.'
+      - '- 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.'
       without_shop_rules:
       - '- If no shop results are present, do not compensate by inventing external products or external manufacturers.'
       technical_rules:
@@ -168,6 +187,7 @@ parameters:
       - '- 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.'
+      - '- If the user asks for a main device/system and the only shop hit is an accessory, reagent, indicator, kit, set, or consumable, state that the shop data does not clearly provide a matching main device/system.'
       - '- Do not call accessories, indicators, reagents, kits, sets, or consumables a device, measuring device, or main product unless the source explicitly says
         so.'
       - '- Do not claim that an accessory is required, necessary, used for calibration, or sets the measurement range unless this is explicitly stated in the provided
@@ -176,6 +196,8 @@ parameters:
         retrieved knowledge.'
       - '- Only use commercial fields for the main product when the shop item and the technically identified product clearly refer to the same product identity.'
       - '- If the shop match is ambiguous, keep the technical identification and commercial details separate.'
+      - '- Shop product names are authoritative for their own shop URL, product number, price, availability, image, description, and metadata.'
+      - '- Do not rewrite a shop record heading with a similar device name from retrieved knowledge. If identities differ or are uncertain, separate the RAG device from the shop hit.'
       - '- If the user asks for the price or availability of a referenced accessory, indicator, reagent, kit, set, or consumable, use commercial fields only from a shop result that clearly matches that accessory identity and code.'
       - '- For such accessory price follow-ups, do not answer with the price, URL, product number, or availability of the main device or of unrelated reagents; if no matching accessory shop item is present, say that the price is not available in the provided shop data.'
       without_shop_rules:
@@ -216,6 +238,66 @@ parameters:
       - '- If a detail is not explicitly stated in the provided sources, say so plainly.'
       - '- Prefer short, source-close sentences over explanatory expansion.'
       - '- If the sources only support that a product family is not suitable, output only that unsuitability and stop there.'
+    product_roles:
+      main_device_request_keywords:
+      - anlage
+      - messanlage
+      - gerät
+      - geraet
+      - messgerät
+      - messgeraet
+      - analysegerät
+      - analysegeraet
+      - analysator
+      - analyzer
+      - system
+      - monitor
+      - controller
+      - testomat
+      - pockettester
+      main_device_product_keywords:
+      - messgerät
+      - messgeraet
+      - analysegerät
+      - analysegeraet
+      - analysator
+      - analyzer
+      - messanlage
+      - controller
+      - testomat 2000
+      - testomat 808
+      - testomat evo
+      - pockettester
+      accessory_product_keywords:
+      - indikator
+      - indicator
+      - indikatortyp
+      - reagenz
+      - reagent
+      - reagenzsatz
+      - kalibrierlösung
+      - kalibrierloesung
+      - pufferlösung
+      - pufferloesung
+      - reinigungslösung
+      - reinigungsloesung
+      - kalibrier
+      - puffer
+      - buffer
+      - zubehör
+      - zubehor
+      - accessory
+      - ersatzteil
+      - verbrauch
+      - consumable
+      - kit
+      - set
+      - flasche
+      - bottle
+      - 100 ml
+      - 500 ml
+      - 100ml
+      - 500ml
     retrieved_knowledge:
       source_line: 'Source: Documents'
     url_content: