About

Most tools give you a score.
Regulators ask for evidence.

IRP Compliance is built on IRP, an open source decision-record format. The difference between a score and a permanent record is exactly what matters when regulators come knocking.

Start free assessment How the technology works

The difference

Compliance tools give you a dashboard.
Regulators want a record.

A score tells you where you stand today. A permanent record shows what changed, who decided it, and why, over time. Those are not the same thing.

01 / Record

Not a snapshot. A record.

IRP Compliance saves your decisions as they happen, not just a single score from one day. Every change to where you stand is kept in order, with the reason it was made.

02 / Permanent

Permanent by design.

Nothing is overwritten. Every fix you make is added to your record, never replacing what came before. This is what auditors and regulators actually ask for: a history, not a snapshot.

03 / Open

Open infrastructure. No lock-in.

The underlying format is MIT-licensed and open source. Your compliance record is not trapped in our platform, it's a plain file you can read, export, and take with you on your terms.

Open source foundation

IRP: Intent Record Protocol.

IRP Compliance is powered by IRP: an open source specification for preserving decisions, their reasoning, and their lineage. MIT licensed. Vendor-neutral. Built to survive tool changes, team changes, and time.

Append-only JSONL ledger

Every decision is a new line, never an edit. The ledger grows forward. Nothing disappears. This is the format audit trails are built on.

Decision + reasoning + rejection

Each IRP entry answers three questions: what did we choose, what did we reject, and why. The three things regulators actually want to see documented.

Portable across tools and time

IRP is not a platform feature. It is a file format. Your decision ledger moves with your organisation, to new tools, new teams, and future audits.

View IRP on GitHub →

// .irp/ledger.jsonl, append-only { "id": "IRP-2026-08-01-001", "decision": "Activated human oversight for high-risk AI system", "why": "Art.26 obligation, deployer must ensure meaningful oversight", "rejected": "Full automation , Art.26 non-compliant", "approved_by": "DPO, CISO", "timestamp": "2026-08-01T09:14:00Z" } // next decision appended below, nothing overwrites

The IRP book

A field guide for architects who need decisions to survive.

Written by the creator of IRP. Covers the protocol, the ledger format, integration patterns, and the philosophy behind decision lineage as infrastructure.

Field guide · Work in progress

IRP: The Architecture of Durable Decisions

A companion guide for architects, CTOs, and compliance leads building systems where decisions need to survive change, time, and scrutiny.

Read the draft →

Most tools give you a score.Regulators ask for evidence.

Compliance tools give you a dashboard.Regulators want a record.