Skip to main content

Agent corpus

Corpus changelog

Regulators keep acting, so the evidence behind the agent tools keeps moving. Every change to the statutory corpus gets a public change note here. Agents pin the corpus version in their answers; when the version changes, they re-read the affected records instead of answering from memory.

How the version works

One corpus, one version

The corpus is versioned on its own, apart from the API and the MCP server. v2026.12.0 is the first versioned release. The rule is one line: when a CAI or OPC decision lands, or a Law 25 checklist row changes, the corpus version changes with it.

The scheme (vYYYY.MM.N)
Year, two-digit month, and a release counter within the month. v2026.12.0, issued 2026-11-04, is the first versioned release; its version month and its issue month differ. From here on, the version month matches the issue month. Every change note below records its own issued date.
Minor (v2026.13.0)
New records, reclassifications, or new guidance attached to an existing row.
Patch (v2026.12.1)
Corrections, link fixes, and wording that leaves the legal substance untouched.
The one-line rule
A changed CAI/OPC decision or Law 25 checklist row bumps at least the minor segment. Nothing is edited silently; retired records stay in the corpus.
Breaking renames
Ship as a new major train (v2027.01.0), never as an in-place edit of an existing record.

Change-note format

What every note carries

Every corpus change ships exactly one note with these ten fields. The same notes are a read-only MCP resource atmovahedi://corpus/v2026.12.0/changelog.

FieldMeaning
change_idCN-YYYY-MM-NNN, unique per note.
corpus_versionThe corpus version the change ships in.
dateISO date the change was published.
change_typeadded, amended, retired, or corrected.
affected_recordsRecord IDs touched: CA-01 to CA-12, enforcement case IDs, Law 25 checklist row IDs, glossary slugs, or resource names.
summary_en / summary_frWhat changed, in plain language, in both languages.
statutory_referenceThe statute or provision behind the change, or “Corpus infrastructure” when no statute changed.
primary_source_urlRegulator decision, guidance, or page; the changelog page itself for infrastructure changes.
supersedesThe change_id this note replaces, or null.
client_actionWhat LLM clients must do: re-fetch, re-pin the version.

Change notes

v2026.12.0, issued 2026-11-04

Worked example, and the first real note: the change that introduced semantic corpus versioning itself. Every field below is live data.

CN-2026-12-001: initial semantic corpus versioning

change_id
CN-2026-12-001
corpus_version
v2026.12.0
date
2026-11-04
change_type
added
affected_records
CA-01 through CA-12, movahedi://corpus/v2026.12.0/changelog
summary_en
Initial semantic corpus versioning. The 12-row consequential-action index, the Law 25 checklist, the CAI/OPC enforcement case summaries, and this change log are now read-only MCP resources under movahedi://corpus/v2026.12.0/, and every MCP tool answer carries corpus_version in its output. When a CAI/OPC decision or a Law 25 checklist row changes, the corpus version changes with it.
statutory_reference
Corpus infrastructure; no statute changed.
supersedes
null (first note)
client_action
Pin corpus_version v2026.12.0 when citing statutory material. Re-read the affected resources when the version changes; never define Law 25 or Bill C-36 from pre-training memory.

For agents

Read the corpus, don't remember it

The versioned corpus lives as read-only MCP resources:movahedi://corpus/v2026.12.0/meta,movahedi://corpus/v2026.12.0/consequential-actions,movahedi://corpus/v2026.12.0/law25-checklist,movahedi://corpus/v2026.12.0/enforcement-cases, andmovahedi://corpus/v2026.12.0/changelog. Every tool answer carries corpus_version. Pin it when you cite statutory material, and re-read the affected resources when it changes.