Obligations, surfaced against the systems they apply to.
The Obligation Engine continuously maps regulatory and framework requirements to live AI system records — so you always know which obligations apply, which are met, and what is outstanding.
Continuous mapping
When a system's risk class, data scope, or stage changes, applicable obligations are recomputed automatically.
Framework-aware
ISO 42001, EU AI Act, NIST AI RMF, and DSIT AIME requirements are decomposed into actionable obligations.
Owner-routed
Each obligation lands in a queue owned by the right team — engineering, risk, legal, or system owner.
Status & evidence
Each obligation links to the controls and evidence that satisfy it, with a clear status: met, in progress, outstanding, or not applicable.
See obligation engine operating against your AI systems in under 10 minutes.
ISO/IEC 42001, EU AI Act, NIST AI RMF, and DSIT AIME ship out of the box. Sector overlays are added on request.
Updates are released as framework deltas. Your live systems are re-evaluated and changed obligations surface with a clear before/after diff.
Yes. Internal obligations sit alongside regulatory ones and use the same status, ownership, and evidence model.
Scoping uses the system's registry attributes — risk class, data scope, deployment region, oversight model, and lifecycle stage.
Start building record for your AI Systems.
One connected structure for systems, risks, evidence, reviews, decisions, and accountability activity across the organisation.