Skip to content
LedgerAI
Sign In
System

How LedgerAI Works

A deterministic chain from legal text to documented proof.

Core System

The Complete Traceability Chain

LedgerAI establishes a four-step chain from legal text to documented proof. Each step is explicit, traceable, and auditable.

01

Regulation

A law or standard that applies to you, decided by explicit rules on your organisation profile.

02

Obligation

A specific requirement within the regulation, with its article or section reference.

03

Control

Technical or procedural implementation that satisfies the obligation.

04

Evidence

Documented proof that the control exists and operates as intended.

Step 1: Regulation

A regulation is a law, standard or binding directive that may apply to your organisation. The EU AI Act, the GDPR, POPIA and the FIC Act are examples.

LedgerAI ships a researched library of regulations and obligations for the EU, the US and South Africa. The library is updated with LedgerAI releases. There is no live regulation change feed, so a change in the law reaches you when a release includes it.

Example: The EU AI Act applies because your profile says you operate in the EU and ship AI features.

Step 2: Obligation

An obligation is a specific requirement within a regulation that you must satisfy. Obligations carry an article or section reference, the condition under which they apply, and a severity.

LedgerAI decides which obligations apply from your organisation profile:

  • Where you operate (EU, US, South Africa)
  • Whether you process personal data
  • Whether you ship AI features or use automated decision-making
  • For South Africa, your entity type, financial-sector licences and filing status
Example: EU AI Act Article 13 requires transparency obligations for your chatbot. This becomes a tracked obligation in LedgerAI.

Step 3: Control

A control is the technical or procedural implementation that satisfies an obligation. Controls can be code, processes, documentation, or oversight mechanisms.

Each control in the library is linked to the obligations it satisfies. Your team sets its status and owner, and legal and engineering work from the same records.

Example: To satisfy the transparency obligation, you implement a control such as “Disclose AI system to users.” The control is linked directly to the Article 13 obligation.

Step 4: Evidence

Evidence is documented proof that a control exists and operates as intended. Each item is a file, a link or a note attached to a control: a policy document, a screenshot, a link to a code commit or a test run.

Every evidence record is timestamped and carries a verification status: pending, verified or expired. When auditors ask, “Prove this control works,” you have documented answers.

Example: Evidence for the transparency control includes: a screenshot of the UI notice, the relevant code commit, and QA test results confirming the notice displays correctly.

The Advantage

Why Traceability Matters

When a regulator asks, “How do you satisfy Article X?” you don’t search through spreadsheets. You follow the chain: Regulation → Obligation → Control → Evidence.

A score or a generic checklist cannot show which piece of work answers which legal requirement.

LedgerAI makes every connection explicit. Legal can see which controls satisfy which obligations. Engineering can see which evidence proves which controls. Auditors can review the whole chain in an Audit Mode export.

This is not compliance theater. This is systematic accountability.

See the system in action.

Create AccountView Pricing