Obligation Delta

The core of an Obligation Delta is the transformation of a deontic operator. It identifies when a permission becomes a prohibition, a duty is narrowed, or a new obligation is created.

• SHALL → SHALL NOT: A mandatory duty is converted into a prohibition.
• MAY → SHALL: An optional permission is elevated to a mandatory obligation.
• Null → SHALL: A completely new affirmative duty is introduced.
• SHALL → MAY: A mandatory duty is relaxed to a discretionary permission.

The delta is always scoped to a specific regulated actor or class of entity. A single regulatory amendment can generate multiple, distinct Obligation Deltas for different stakeholders.

• Regulated Entity: The party directly bound by the new duty (e.g., 'financial institution').
• Supervisory Body: A new reporting duty imposed on a regulator.
• Third Party: A new right or protection granted to a consumer or counterparty.
• Mixed Impact: A single change that imposes a duty on one actor while creating a corresponding right for another.

An Obligation Delta captures the precise preconditions that activate the new duty. It models the logical 'if-then' structure of the rule, moving beyond simple text changes to semantic triggers.

• Threshold Triggers: A duty activates only if a quantitative metric exceeds a limit (e.g., 'if assets > $50B').
• Event Triggers: A duty is contingent on a specific event (e.g., 'upon a data breach').
• Temporal Triggers: A duty becomes effective on a specific date or after a defined period.
• Compound Triggers: Complex logic combining multiple conditions with AND/OR operators.

The delta defines the specific, actionable object of the obligation—what exactly must be done, prohibited, or permitted. This moves from legal text to a machine-readable compliance task.

• Reporting Action: 'File Form X-17A-5 within 60 days.'
• Prohibited Conduct: 'Shall not engage in proprietary trading.'
• Policy Mandate: 'Must establish a written cybersecurity policy.'
• Capital Requirement: 'Shall maintain a minimum Tier 1 capital ratio of 8%.'

Not all deltas are equal. A core characteristic is a severity score that quantifies the operational impact of the change, enabling triage and prioritization.

• Critical (New Duty): A brand-new, affirmative obligation requiring immediate process creation.
• High (Threshold Change): A modification to a numeric limit that alters compliance status.
• Medium (Procedural Shift): A change to a filing method or timeline.
• Low (Definitional Clarification): A non-substantive change that refines terminology without altering core duties.

Every Obligation Delta maintains a cryptographically verifiable provenance chain back to the specific source text. This ensures auditability and allows for precise legal citation.

• Source Document: The specific amending bill or final rule.
• Target Provision: The exact statutory section being modified (e.g., 15 U.S.C. § 78j).
• Effective Date: The extracted date when the delta becomes operative.
• Diff Evidence: The precise text span that constitutes the change, serving as the grounding for the semantic analysis.

The formal representation of obligations, permissions, and prohibitions using modal logic. An obligation delta is computationally derived by applying deontic operators to the pre- and post-amendment states. Standard Deontic Logic (SDL) uses the O operator for obligation and P for permission; a delta is the logical difference O(φ) → O(¬φ), representing a complete reversal of duty.

The specific, atomic difference between two versions of a regulatory text. While a regulatory delta identifies the textual insertion, deletion, or modification, the obligation delta interprets its normative consequence. For example, a regulatory delta might show a threshold changed from '$10M' to '$5M,' but the obligation delta captures the new class of entities now subject to reporting duties.

The systematic comparison of an organization's internal control framework against a new regulatory baseline. The obligation delta serves as the input to gap analysis, defining the precise scope of new or modified duties. Key steps include:

• Mapping each delta to existing internal policies
• Identifying control deficiencies for new prohibitions
• Calculating remediation effort for expanded obligations

A quantitative methodology that assigns a severity rank to each detected obligation delta based on its operational, financial, and legal consequences. Scoring models typically weigh factors such as entity scope (how many business units are affected), duty type (prohibition > obligation > permission), and remediation timeline. A delta introducing a new criminal liability provision would receive a maximum criticality score.

The algorithmic detection and reconciliation of contradictory legal rules. An obligation delta can introduce a direct conflict with an existing, unamended duty. Resolution strategies include applying the lex posterior (later law prevails) or lex specialis (specific law prevails) principles. Automated systems must flag, not silently resolve, such conflicts for human review.

A computational framework that traces how a single obligation delta in a foundational statute cascades through dependent regulations, cross-references, and interpretive guidance. A change to a definition in a parent act can silently modify the obligation delta of dozens of subordinate instruments. Propagation models use graph traversal algorithms on legal knowledge graphs to map the full blast radius.