News

Releases, publications and milestones from Intent Record AB.

A plain-language guide to the EU AI Act, free to read

Twenty-six chapters covering the EU AI Act in plain language: why the law exists, how to work out whether you are a provider or a deployer, what the risk tiers actually mean, and what each key article requires of you.

It is written for the people who have to act on the regulation rather than litigate it, and it is specific about what the law does not say as well as what it does. Free to read, no registration.

irp-capture 0.8.0 adds provenance lenses to the decision graph

A decision ledger tells you what was decided. It does not tell you which decisions everything else is resting on. Version 0.8.0 adds three lenses over the decision graph that answer that directly: foundations ranks what the recorded reasoning rests on, lineage shows why a particular decision exists, and impact shows what would be affected if it changed.

The lenses run over a derived layer that types each reference before walking it, which matters more than it sounds. Typing the edges removes cycles that would otherwise circulate through the graph and distort every score.

Everything here is MIT licensed and runs locally: pip install irp-capture, then irp export graph --view foundations. The analysis is written to a separate derived directory, pinned to a hash of the exact ledger it was computed from. It is never written back into the record itself.

IRP Evidence API: proving a record existed, without us holding your data

A record kept on your own machine has an honest limitation: you could change it and recompute its hashes, so it cannot prove on its own when it was written. That gap matters if the record is ever meant to serve as evidence.

The IRP Evidence API closes it with an external RFC 3161 timestamp, which proves a record existed by a given moment. The service receives only a cryptographic digest, never the underlying content, so we cannot see what is being recorded even in principle. An open browser SDK builds the package client side, and an independent Python verifier checks it offline, without needing us.

The verifier and SDK are MIT licensed, and it is deliberately honest about what it does not prove: existence by a point in time, not identity, delivery, or truth.