Skip to content
Reg Change agents
Risk, Trust & ResilienceReg ChangeObligation Engineering

Obligation Change & Diff Agent

Explains exactly which duties, thresholds, populations, dates and evidentiary expectations changed.

Compares obligation semantics rather than page layout, classifying additions, removals, scope changes, deadline shifts and clarifications while preserving both source versions.

Authority

Inform

Team role

Provides specialist analysis

Handoffs

Named collaborators

The role

What it owns and where its authority ends

Desk

Obligation Engineering

Desk workflow

Segment text, classify normative force, atomize requirements, compare versions and independently validate citations.

Collaboration

Passes a defined work product to the next owner

Decision boundary

Provides evidence or analysis without committing the decision.

Systems and capabilities involved

  • Versioned obligation graph

  • Semantic and structural diff engine

  • Source relationship graph

  • Change adjudication workspace

Handoffs

What this role gives and receives

Capabilities offered

The handoffs name the next owner or specialist and the work that moves between them.

Context

What the role needs to do the work

Current work
Current source version, applicability questions, obligations, impacts, owners, deadlines and evidence gaps
Prior interactions
Prior interpretations, implementation decisions, filings, exams, commitments and challenge outcomes
Policies and reference
Firm jurisdiction, entity, product, obligation, policy, risk, control and filing taxonomies
Working method
Approved legal-review, change-governance, implementation, attestation and submission playbooks

Illustrative workflow

How the work moves

Starting point

A regulator issues a technical correction and delayed compliance date

  1. 01

    Bind prior and current source families

  2. 02

    Re-extract affected obligations

  3. 03

    Classify semantic deltas

  4. 04

    Notify impacted mappings and plans

Result

Obligation delta set with severity, dependencies and downstream impact graph

Checks and boundaries

What must be tested or reviewed

  1. 01Detects seeded threshold, exception, definition and date changes
  2. 02Does not label formatting-only edits as substantive obligation changes
  3. 03Every delta resolves to old and new pinpoint source

Human authority

  • Obligation owner confirms material semantic changes before implementation scope is reduced

Keep exploring