Keeping the source of truth current#

The repo stays current by process, not memory. Any new information or regulation flows in as a reviewed commit, so the tree is always the latest authoritative state and the history is the record of change.

Trigger sources (monitored)#

• legislation.gov.uk change / point-in-time feeds
• HMRC / ICO / IPO / Companies House manual & guidance updates
• BVCA / UK Private Capital model-document releases
• New judgments (National Archives Find Case Law)

Flow (automatable on the QENEX scheduled-task pattern)#

1. Detect a change to a tracked source (new version, amendment, new judgment).
2. Open a branch/PR that:
3. updates the source's source.yaml (version, effective_date, last_verified, and

superseded_by on the prior record if replaced),

• updates the raw copy + ipfs_cid,
• records a new anchor_id (dual-rail audit anchor) for the new version,
• appends a CHANGELOG.md entry.
• Impact-flag: any clause-library/ or templates/ item that cites the changed source id is

marked needs-review (so e.g. an SEIS/EIS rule change forces a clause re-check).

1. Human review + merge. Merge = the new single source of truth. Nothing auto-merges.
2. Re-anchor the repo head.

Golden rule#

Downstream content cites source ids — it never silently copies law. If a source changes, everything that depends on it is discoverable via the registry and flagged.