European LegalTech infrastructure that leads a legal answer back to its source, its context and its provenance.
Repertorium · legal knowledge infrastructure | PATRON · local-first legal workspace
Boutique · connectors and skills | MateMatic · architecture, audit and deployment
Four layers. Each works on its own; none requires the others.
| Layer | What it is | How you reach it | Code | Runs on your machine |
|---|---|---|---|---|
| Repertorium | Legal knowledge infrastructure: a corpus of Polish and EU law with a citation graph and PL-EU links | web console, remote MCP, REST | hosted service; interface and response contract documented in the open | as a local data pack, by agreement |
| PATRON | Local-first legal workspace: case files, chat, tracked-changes drafting, audit trail | Windows desktop app, 9 language editions | AGPL-3.0 | yes; the model is local or a cloud one you choose |
| Boutique | Catalogue of MCP connectors and agent skills | uvx / npx / npx skills add, catalog.json |
MIT / Apache-2.0 | yes; connectors query public sources from your machine |
| MateMatic | Architecture, reliability audit and deployment inside a firm | contact | governance documents are open | - |
people ─────────► PATRON (desktop) ───► connectors ───► official sources
(live query)
AI agents ──────► any MCP client ─────► connectors
└───► Repertorium (corpus snapshot)
applications ───► REST / MCP ─────────► Repertorium
people ─────────► web console ────────► Repertorium
PATRON reaches Polish and EU sources through its own bundled connectors today; wiring it to Repertorium is planned.
The two words mean different things here.
- Corpus (Repertorium, and the offline connectors
mcp-eu-compliance,mcp-fr-legal,pk-eli-mcp): a snapshot of the law with a known state date. Fast, joinable, citable - and as current as its last build. - Live query (most connectors): the request goes to the official source at the moment you ask. As current as the source itself - and only as available and as structured as that source is.
Claims are cheap; these are the parts you can inspect.
- Citation contract - MCS v0.1: the
source_id / url / exact_quote / locator / confidenceshape PATRON verifies citations against, with a conformance test a connector can run. - Response contract - Repertorium answers are
ok,partial(with the shards that failed named) orsearch_unavailable. An empty list is never passed off as an honest zero. Details. - Audit trail - PATRON hash-chains every model interaction and exports a ZIP with its own verifier, and the documentation says what the trail does not prove (ADR-0142, audit trail).
- Decisions - Architecture Decision Records and the AI Constitution a firm reads before deployment.