Obligation
A specific, citable requirement extracted from a statute, regulation, guidance, supervisory expectation or standard.
Overview
An obligation has an identifier, a source document and version, a scope (who and what it applies to) and the controls mapped to it. When the source changes, the obligation and its controls are re-tested.
Obligations are the unit that connects regulatory text to operational work.
It connects most directly to Requirement, Control, The five layers of obligation and Compliance obligation.
Example
GENIUS.Redemption, version 2026-08: redeem stablecoins at par on request within the required timeframe.
Check the official sources below for legal scope, applicable dates and exceptions. This entry is an explanatory reference, not legal advice.
Why it matters
Obligations are what you are actually accountable for; documents are just where they are written down.
Who it affects
All regulated organisations.
Where it sits
Ten linked steps connect where you operate to the proof that you complied.
- 01Jurisdiction
- 02Industry
- 03Activity
- 04Authority
- 05Regulation
- 06Requirement
- 07Guidance
- 08Control
- 09Evidence
- 10Enforcement
Connections
The terms most closely tied to Obligation. Select one to open it.
What to do about it
- 1Define the owner, frequency, data and pass condition.
- 2Automate the test on source data where you can.
- 3Capture evidence on every run, including exceptions.
- 4Review exceptions and failures and record the decision.
From requirement to evidence.
Regulation Layer’s library holds obligations across all five layers, each linked to its source, authority and controls.
Request early access →