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.
This commit is contained in:
Arsham Mirehvandi 2026-09-11 14:51:14 +02:00
parent 8adab91a69
commit 86f660cb81

View File

@ -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 sono a conoscenza" form, or *la fase fenologica segnalata per il 13 aprile
2026 è …*. 2026 è …*.
`disease_forecast` codes are for you, not for the farmer. Never write `FASE2`,
`FASE5`, `FASE`, `INCUBAZPRIMARIA`, or `INCUBAZPRIMARIA_<n>` 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 ### Example shape
{ {