From 86f660cb81ef524ebb4a418f7736cd9720cfe0a2 Mon Sep 17 00:00:00 2001 From: Arsham Mirehvandi <130353205+arshammi@users.noreply.github.com> Date: Fri, 11 Sep 2026 14:51:14 +0200 Subject: [PATCH] Clarify internal code usage in advisory text - Updated _output_format.md to specify that `disease_forecast` codes are for internal use only and should not be included in `full_advice` or `advice_summary`. - Provided Italian translations for specific codes and emphasized the importance of using farmer-friendly language when referring to these phases. --- prompts/_output_format.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/prompts/_output_format.md b/prompts/_output_format.md index fcb0e93..7e2ea91 100644 --- a/prompts/_output_format.md +++ b/prompts/_output_format.md @@ -43,6 +43,15 @@ or in `full_advice` *la fase fenologica segnalata per oggi è …*. In sono a conoscenza" form, or *la fase fenologica segnalata per il 13 aprile 2026 è …*. +`disease_forecast` codes are for you, not for the farmer. Never write `FASE2`, +`FASE5`, `FASE`, `INCUBAZPRIMARIA`, or `INCUBAZPRIMARIA_` in `full_advice` or +`advice_summary`. Keep using those codes internally when reading the JSON. +When referring to those days, use Italian farmer language: +`FASE2` → germination (*germinazione*); `FASE5` → risk of infection (*rischio +di infezione*); `INCUBAZPRIMARIA` / `INCUBAZPRIMARIA_80.7` → primary incubation +(*incubazione primaria*), and state the percentage in words (e.g. *all'80,7%*), +never the JSON key. + ### Example shape {