graphs.sgit.aithe vaultsRegulation Graph

Regulation Graph, opened

The EU AI Act as a graph you can cite. Regulation (EU) 2024/1689 parsed from official Formex XML, hash-verified against the bytes it came from, and published as an evidence layer: in the vault's own words, "a risk in a register points at a named obligation in a real instrument instead of being asserted." This is the largest graph in the estate and the one this book already quotes most often — usually without saying what makes the numbers trustworthy, which is what these pages are for.

113articles
500paragraphs
417points
180recitals
13annexes
68definitions
1,523 · 1,944nodes · edges

The vault's own counts, resolving from the structure above. Quoted here, not recounted.

Built from Formex XML retrieved from CELLAR, hash-verified, parsed deterministically.
Built from Formex XML retrieved from CELLAR, hash-verified, parsed deterministically. · the vault's own published figure, sgit.ai/demos/vaults/regulation-graph/, fetched 22 August 2026, CC BY 4.0

The two deep readings

chain of custody

The provenance chain

Claim → graph node → vault file → commit → official source, with CELEX identifiers and the SHA-256 of retrieved bytes. Plus versioned properties, two instruments composed without consolidation, and the audit that stopped a publication.

the correction, verified

The query engines

SQLite over sql.js in memory, rdflib with Turtle export, Cytoscape over the citation graph — all client-side, all ephemeral, the vault never written by the app. This is what settles the "we don't use databases" correction.

The instrument itself, structure first

The Act is navigable by its own structure, with a provenance footer on every node and search across the parsed text. This is the view that makes the rest defensible: when a risk cites Article 9(2)(a), you can go and read Article 9(2)(a) — in the text that was parsed, not a paraphrase of it. The distinction sounds pedantic until you have watched a compliance discussion run for an hour on somebody's summary of a provision.

Per-node provenance footers, and search over the parsed text.
Per-node provenance footers, and search over the parsed text. · the vault's own published figure, sgit.ai/demos/vaults/regulation-graph/, fetched 22 August 2026, CC BY 4.0

The entry point is an experiment, deliberately

app.json sets entry to lab/index.html, so opening the vault lands in the Art 9 lab: paragraph universes, a web-component folder explorer, provision graphs with reach profiles, and a Graph REPL whose read-only tools drive the canvas. The lab is marked experimental and has no main navigation of its own; a back-link reaches the other ten views.

Landing a reader in the newest and least finished thing is an unusual choice, and an honest one. It is the same instinct as this site's comms board: showing the work in progress rather than only the parts that have settled.

Opening the vault lands here: the Art 9 lab, marked experimental.
Opening the vault lands here: the Art 9 lab, marked experimental. · the vault's own published figure, sgit.ai/demos/vaults/regulation-graph/, fetched 22 August 2026, CC BY 4.0

Eight hard rules, two worth quoting

"Evidence, not compliance. Never a claim that an organisation passes or fails. Not legal advice."
"Provenance chain end to end: claim → graph node → vault file → commit → official source (CELEX/ELI plus SHA-256 of retrieved bytes)."

The first is a scope discipline this book should copy rather than admire: the vault refuses to be the thing everybody wants it to be. The second is the one this site keeps arriving at from other directions — it is the same instinct as the build gate that refuses a release when the book lags its source. A claim is worth what its chain of custody is worth.

What it does not do

Open it yourself

sgit clone sgit_rk1_c004daae386e8d17fa648884acc527018bd4ea1116ad673fb2f1b068011695c9:73heuprz

A one-way read key, derived from a vault key that is not published and never will be. The vault's own page carries the live embeds and the full audit note.

What the book will cite from this