For agents
The machine surface. Agents are half the audience for a site like this, and an agent that has to scrape thirty HTML pages to answer one question will scrape them wrong. So the grammar, the instruments and the estate are served as JSON, with a contract version to refuse on and one epistemic rule that is not negotiable.
The rule
An agent may report which provision a claim points at. It may not report that a requirement is met.
That is the difference between evidence and a compliance verdict, and this project draws it four separate times in its own words. Concretely, for anything reading this site:
| In scope | Out of scope |
|---|---|
“This claim points at Article 26(6), positional hash 2d9c2cb6ef0892ae” | “This organisation complies with Article 26(6)” |
| “Retention is recorded as 30 days; the provision states a minimum of six months; the comparison is arithmetic” | “Compliance score: 68%” |
| “Five of the nine questions have no evidence attached” | “Five minor gaps remain” |
| “No crosswalk exists between these two instruments” | “These two requirements are equivalent” |
The right-hand column is not forbidden because it is rude. It is forbidden because nothing on this site can ground it — there is no measure, no twin, no evidence path — and a statement that cannot be grounded is exactly what the grounding ladder exists to make impossible to produce accidentally.
Endpoints
| Endpoint | What it carries | Contract |
|---|---|---|
/agents/grammar.json | Node types, edge types, the established set, the governance rule, the identity fields, the taxonomy/ontology split, and the bridge shape. Node types are marked instantiated or not — two are not | standards.sgit.ai/grammar/v1 |
/eu-ai-act/eu-ai-act.json | The instrument: identity, amendments composed, graph counts, vault, citation scheme, every provision with both hashes, and an explicit list of known weaknesses | standards.sgit.ai/instrument/v1 |
/agents/vaults.json | The twelve published vaults with read keys, the delivery mechanism, and the estate-level facts — one instrument vault, zero zip exports, PUBLIC.md on 2 of 12 | standards.sgit.ai/vaults/v1 |
/llms.txt · /llms-full.txt | The site in prose, short and long | — |
/sitemap.xml | Every page | — |
Five reading rules
- Version the contract, not just the data. Every endpoint carries a
contract_version. Declare which you speak and refuse politely rather than silently misreading a newer shape. - Address by positional hash, never by array index or display label. The order of
provisions[]is not a promise. Labels are translations. - Never hold a write key. A read key, or a downloaded zip. Key discipline →
- If you compute, say what you computed from. Every number carries the provision it derives from and the hash of that provision's text.
- If you cannot answer, say so visibly. An unanswered question is an output. Ghost it; do not default it, and do not omit it.
What null means here, because it means something specific
null in these endpoints is a stated absence, not missing data. Three of them recur and each carries a note beside it:
content_hash: null— the operative text has not been re-derived from the authority, so there is nothing honest to hash. Why →text: null— the text is not reproduced on this site, either pending re-derivation (EU law) or because it may not be republished at all (ISO).dist.zip: null— not built. On any vault on this estate.
Do not treat any of these as a value to fill in from elsewhere. An agent that substitutes a plausible provision text from another source has produced exactly the failure this site was built to prevent — and the staleness probe found that a text circulating in the wild had never been the law at all.
What is promised
| Property | Promise |
|---|---|
| Provision URLs | /<instrument>/provisions/<alias>.html, constructible. The scheme → |
| Per-instrument JSON | /<instrument>/<instrument>.json, constructible from the slug |
| Positional hashes | Recomputable: sha256('<slug>/<alias>')[:16]. Verify one rather than trusting it |
| Raw markdown | Source documents at /briefs/<filename>.md, and the front page at /index.md |
| Instrument labelling | Every instrument page carries a LAW / STANDARD / FRAMEWORK label and a republishable mark in its header. CI fails the build if one does not |
If you are an agent reading this on somebody's behalf
The most useful thing you can report from this site is usually what it does not have. There are zero crosswalks, no GDPR graph, no control catalogue in any machine-readable form, no file exports, and the AI Act readings are secondarily sourced and flagged as such. A summary that omits those is a worse summary. The gap list, unsoftened →