Editing Corpus/Schema (section)

=== Static vs dynamic columns ===

* '''Static''' (written by <code>sync_source_registry()</code> at init from <code>SOURCE_REGISTRY</code>): <code>source_key</code>, <code>parent_source_key</code>, <code>jurisdiction</code>, <code>name</code>, <code>description</code>, <code>kind</code>, <code>publisher</code>, <code>publisher_url</code>, <code>license</code>, <code>license_url</code>, <code>language</code>.
* '''Dynamic''' (written by <code>refresh_corpus_stats()</code> at the end of each ingest cycle, including the dedup steps inside <code>run_post_ingest()</code>): <code>coverage_start_year</code> (= <code>MIN(date)</code> per source), <code>document_count</code> (= <code>COUNT(*)</code> per source), <code>freshest_document_date</code> (= <code>MAX(date)</code> per source). Top-level parent rows that have sub-sources are populated by a SUM/MIN/MAX rollup over their children.
* '''Operational''' (written by <code>state.set_ingest_state()</code> per ingest run): <code>last_file</code>, <code>source_updated</code>, <code>ingested_at</code>. These track pipeline state, not content state, and are not displayed in MCP responses.

<code>sync_source_registry()</code> MUST NOT touch dynamic columns — they would be reset to NULL on every init. The INSERT and <code>ON CONFLICT DO UPDATE SET</code> clauses only list static columns.

----