Editing Corpus/FTS (section)

== The two-text model ==

* <code>body</code>: clean displayable content. Always renderable to a user (HTML, links, formatted text). Immutable after ingestion. Never contains noisy OCR or raw PDF binary.
* <code>body_search</code>: FTS-optimized text used for indexing. Can be noisy (raw PDF extraction, OCR output) because users never see it directly. Nullable. When NULL, FTS uses body directly.

Why two columns:
# '''Display vs index separation.''' <code>get_document</code> returns <code>body</code>, so it must always be clean. FTS reads <code>coalesce(body_search, body)</code>, so <code>body_search</code> can hold a noisy-but-indexable representation (e.g., extracted PDF text) without polluting display.
# '''PDF-sourced documents.''' When a document is only available as PDF, <code>body</code> is a clean stub like <code>&lt;p&gt;Source: &lt;a href="..."&gt;PDF officiel&lt;/a&gt;&lt;/p&gt;</code> (the LLM follows the link or uses search snippets). <code>body_search</code> holds the pdfminer-extracted text so the document is findable via FTS.
# '''Legal reference normalization''' (e.g., "L442-1" to "L442.1") must be consistent between index and query. <code>body_search</code> holds the normalized text; the search plugin applies the same normalization to the query.
# <code>body</code> is the source of truth for display and annotation anchoring. It never changes.

See ADR-010 for the full rationale of this semantic.