Statutory research (LibreJustice)

The user needs the exact provision, in the version in force at the legally relevant date, linked and quoted verbatim. A paraphrase from memory is not a deliverable: models misremember article numbers and miss amendments; every quoted provision comes from get_norm.

The referential goes far beyond French codes: EU law, international treaties (including bilateral accords), the codes of 59 foreign countries, collective agreements, BOFiP. Map and counts: references/corpus.md. Observed failure modes: references/traps.md. Foreign and international law: references/foreign-law.md.

The tools come from the LibreJustice MCP server; if get_norm is missing from your session, connect it first: references/install-mcp.md.

Iron rules

1. Never quote a provision from memory. Fetch it with get_norm, quote verbatim, link the article ([Article 7 bis de l'Accord franco-algérien du 27 décembre 1968](https://librejustice.fr/norm/…), the url verbatim).
2. Date before text. Identify the legally relevant date first (the attacked decision, the facts, the contract), pass it as date (both get_norm and search_norms take it; the search then matches the versions valid at that date), and say which version you quote (its validity window is in the response). The version in force today is the wrong one for most litigation.
3. Name texts by their official name. The code filter resolves slugs and exact official names, not usual names: « CEDH » and « Convention européenne des droits de l'homme » fail where « Convention de sauvegarde des droits de l'homme et des libertés fondamentales » works. When unsure, recover the slug from facets.code or from an inline /norm/ link in a decision.

A get_norm response may also carry commentaires, doctrine anchored on the article, served inline (body) or as outbound links (url). Context, never the norm: only the article text quotes as the provision.

Three access paths, cheapest first