The agent layer
One agent per article, as an address
Every article in the register has its own rule tree with its own address, interface and hash. The tree runs deterministically: the same facts give the same outcome, today and in a year. No language model is involved, neither when the tree is built nor when it runs.
- agents
- 1 563
- acts
- 26
- operative trees in the GDPR
- 18
Engine: agent-engine-1 sha256:0a4bd50d21f8ec9bBuild: agent-engine-1+legal-2026-08-25
Acts with an agent layer
- GDPR99 articles
- AI Act113 articles
- NIS246 articles
- DSA93 articles
- DMA54 articles
- ePrivacy23 articles
- PSD2117 articles
- EUDPR101 articles
- DORA64 articles
- MiCA149 articles
- CSRD8 articles
- CSDDD39 articles
- Taxonomiförordningen27 articles
- Dataförordningen50 articles
- Cyberresiliensakten71 articles
- eIDAS 2.082 articles
- FSR54 articles
- WHISTLEBLOWING29 articles
- PAY-TRANSPARENCY37 articles
- PLATFORM-WORK32 articles
- PRODUCT-LIABILITY24 articles
- GPSR52 articles
- EUDR38 articles
- CBAM36 articles
- AMLR90 articles
- ACCESSIBILITY35 articles
How it works
- 1Pick an article. The address is the agent: /agent/gdpr/artikel-33.
- 2Read the script. The fields are the article's conditions, the outcomes are its obligations with paragraph references.
- 3Call the API. The answer carries the outcome, a trace per condition, missing fields and a run hash.
- 4Verify. The text, script and engine hashes travel with every answer.