Skip to main content
Compliance teams need to know what changed before anything becomes tenant work. The Regulatory Pack API exposes source-traced change intelligence at the canonical pack layer:
  • pack version history
  • deterministic fact diffs between versions
  • change events with impacted fact IDs, materiality, confidence, and citation basis
  • source-watch currentness, source-change events, and binding recompile candidates
Pack diff endpoints do not create tenant tasks. Customer applicability endpoints can persist workspace-scoped obligation instances and change impacts after a profile-specific review.

List Versions

Select a pack explicitly. This example uses the UK Data Use and Access pack:
curl
Expected response shape:

Diff Versions

Set two versions from the version list:
Then call the diff endpoint:
curl
Diff rows can include:
  • change_type
  • fact_type
  • fact_id
  • impacted_fact_ids
  • source_citation_basis
  • materiality
  • confidence
  • before/after hashes

List Change Events

curl
Use change events to power a downstream change monitor:
CLI and MCP wrappers are available for monitoring currentness, source checks, change events, graph coverage, customer applicability runs, obligation instances, and customer change impacts.

Monitor Source Currentness

Create source watches for validated public HTTP(S) or deployment-approved S3 sources, then run a bounded source check. These state-changing calls require monitoring:write; pack version, diff, event, and currentness reads use regulatory:read:
curl
Only binding source changes create recompile candidates. Guidance and watchlist changes are currentness signals and do not become binding obligations without binding source support.
CLI