Home / Vaults / Standards Atlas — GDPR
Standards Atlas — GDPR
"The standard is the graph." GDPR cannot be read at face value: its operative meaning lives in the rulings, the regulators' guidance, and the per-country variation the text never mentions. This vault makes those first-class nodes layered over the articles they bend — and it is one of the earliest experiments here in shipping a graph as a vault.
Read key:
sgit_rk1_439ca57ab9e53b4edfa67e99da1b70948c297d323376c890292dc2f0876aa15c:4zv4bvmuIn the official UI: open it read-only in a new tab · From the CLI:
sgit clone sgit_rk1_439ca57ab9e53b4edfa67e99da1b70948c297d323376c890292dc2f0876aa15c:4zv4bvmuPublished deliberately, and derived one-way from a vault key that is not published and never will be.
See it live, here
Both surfaces open automatically below. You can also open the app in its own window ↗.
What is in it
Read the text at face value and you miss most of it
The vault holds the whole workshop rather than a finished artefact: the raw Regulation (EU) 2016/679, a normalised form, the graph that connects it, the visualisations rendered from that graph, and the provenance that makes each claim auditable. Nine views run from The text through Structure, The graph, Beyond the text, Sources, Validate and Provenance.
Its sources are public record and named as such — CJEU proceedings including Meta Platforms Inc. v Bundeskartellamt, regulator material from the German federal DPA, and enforcement decisions. Nothing private is in it, by construction.
A banner across every page, and a seed that says it is a seed
Above every view sits SEED PASS — NOT LEGAL ADVICE, and the overview repeats it in full: "a structural and educational artefact, not legal advice. The rulings/guidance/per-country overlays are a web-verified seed (30 May 2026), illustrative and not exhaustive, and must be validated before they are relied upon."
That is why the Validate view matters. Corrections are written from inside the vault to /feedback/, gated on the fs.write: ["feedback/"] grant — so a read-only reader records changes in the page only, while the seed graph stays immutable and reviewers layer validated provenance on top.
Notes
The narrowest interesting grant on the site. Most vaults here request read and no write. This one requests fs.write and fs.mkdir on exactly one path — feedback/ — which is how it accepts corrections without ever letting a reviewer alter the graph they are reviewing.