Run it in ten minutes
The quickstart goes from a clone to a verified release answering a question with citations — and proves the verification is real by feeding it a tampered artifact.
OpenRegs
Regulation as data an agent can cite. Every answer traces to an official source; every artifact verifies offline.
Regulation, not one sector’s regulation. A regime declares the instruments it mirrors and the jurisdiction they belong to — never an industry. What bounds coverage is whether a publisher’s format has a watcher adapter, not what the law is about. Financial regulation is where the first real corpora start, because obligations move fastest there and the cost of missing one is highest, and the same six planes read the rest. What OpenRegs is says it at length.
Point an agent at it
MCP setup wires an agent to five tools over one verified release, so its answers carry eIds, atom ids and a release tag — and explains why the quoted law arrives wrapped in a notice saying it is data, not instruction.
Understand the system
The overview walks the six planes — ingestion, consolidation, atomization, canon, release, serving — and the architecture enumerates every component and contract between them.
Look up a command
The CLI reference is generated from the engine’s own argument parser: every command, flag, default and choice, and never a transcription that could drift.
Operate it
Runbooks cover building, signing and publishing releases, reading a red CI gate, triaging quarantine, and disaster recovery.
Wire it into CI
Release bumps map your controls to obligation atoms and report what a new release does to them; the integrations run that report for you on GitHub Actions and GitLab CI.
Contribute
How to contribute takes one obligation atom from the text it is read out of to the release that ships it; governance says who reviews what, and why domain review is not optional.