Files
marcopan 292048f777 feat(harness): language workspace param + skill riscritta in inglese (semantica completa)
Due cambiamenti interconnessi da user review:

1. language come parametro workspace (spec decisione 9):
   - Config.language (default 'en') + workspaces PSD con 'language: it'
   - Generalizza Thoth oltre l'italiano: descrizioni tabelle/colonne ed evidence
     sono nel workspace language; le istruzioni della skill restano in inglese
     (piu' affidabili per modelli piccoli, meno ambigue)

2. Skill riscritta in INGLESE preservando la semantica COMPLETA dell'originale
   (autocritica: la mia riscrittura precedente aveva perso ~10 vincoli precisi):
   - 'promuovere' ambiguo (3 accezioni: phase advance / recommend / memory promote)
     -> 'never advance a phase or record a decision without confirmation'
   - recuperati vincoli persi: choice-is-confirmation (no reviewer_confirm dopo
     reviewer_decide), reviewer_select SOLO per iterazione no-decision, messaggi
     auto-contenuti obbligatori, artefatto = superficie di decisione (gate rilegge
     da disco per CTE/SQL), candidati con provenienza+score non verita', opzione
     'leave ambiguity open', F1 passa lista completa non solo ultima
   - language contract esplicito (istruzioni EN, output nel workspace language)

Sottomoduli cte/memoria/rewriting/sql-generation in inglese, semantica tecnica
intatta (regole AV-SQL, dim_time trick, max 5 memorie solo 3 tipi riusabili).

Verifica: 0 residui nsp/chirone, tutti i tht <cmd> citati registrati, 165 passed.
2026-06-27 14:50:30 +02:00

1.1 KiB

Question rewriting technique

Adapted from the "rephrase question" step of AV-SQL: decompose the question into explicit conditions, without losing information.

The rewritten question must:

  1. Make the population explicit (who/what is counted or selected) using the data model's terms (e.g. "distinct patients in dim_patient").
  2. Make every condition an explicit, numbered clause: time window, included/excluded events, thresholds, states.
  3. Replace ambiguous terms with the concepts clarified in Phase 1, citing the evidence that defines them when it exists (evidence id in parentheses).
  4. Make the expected output explicit: count, list, aggregate, trend.
  5. Stay in the workspace language, in a form a second reviewer would understand without having seen the conversation.

Format of the proposal to the reviewer:

Rewritten question: Conditions: 1) ... 2) ... 3) ... Assumptions used: Expected output:

Iterate based on corrections. Do not proceed to Phase 4 without confirmation.