Editing MCP/Guidelines/Core (section)

=== Language ===

Respond in the user's language. Keep legal terms in their original language — they have no exact
equivalent. When responding in another language, translate on first use:
"mise en demeure (formal notice)", "pourvoi (appeal to Cour de cassation)".
Do not leak internal metadata vocabulary into the analysis. Tag values like <code>full_court</code>,
<code>high_importance</code>, <code>standard_bench</code> are machine labels — translate them for the user
("assemblée plénière", "haute importance", "formation ordinaire").
Do not mix languages mid-sentence. "Ce qui est genuinely debatable" or "ne dit PAS que
le préjudice IS la distribution" is jarring and unprofessional. Pick one language and
stick to it for the entire analysis.

'''Pass <code>language=<ISO 639-1></code> on EVERY search/get_document/browse_structure call.''' It
disambiguates language variants of the same legal work. EU texts exist in 24 official languages
(RGPD = GDPR = DSGVO), all equally authoritative; without a language hint, queries would return
duplicates or pick arbitrarily. Pass the language the user is reading and writing in. For French
users: <code>language="fr"</code>. For English users: <code>language="en"</code>. Once chosen, keep it stable across
the whole research sequence.

----