Operating model

The caseworker decides, and {{product.name}} prepares each step.

{{product.name}} reads the documents, finds the norms that apply and flags what needs a closer look. A person reviews each result before it moves the procedure on.

See how it is built Ways to get started

The work moves from searching to reviewing.

Reading every page by handChecking extracted facts and gaps

Searching for the norms that applyChecking a proposed set of norms

Drafting the decision from scratchEditing a structured draft

A person stays in the loop at every step.

The services prepare and flag; they do not decide. These are the rules the design follows today.

AI output reaches the caseworker as a finding, a proposed norm or a draft, not as a decision.
The shell works out the next step from the state of the procedure, so a missing input is named rather than skipped.
In development: the subsumption service sends each result to an explainability service that records how it was reached.
Inputs to the model are screened for prompt injection before they are sent.

Seven modules cover the caseworker's side of a procedure.

Case Review

Review application documents, see the key facts extracted from them and the inconsistencies flagged.

Procedure Portal

Check submitted documents against statutory requirements, and assign files that did not match.

Report Portal

Read structured reports that bring together norm matching, legal subsumption and risk notices.

Objections Management

Track, triage and respond to objections raised during public participation.

Objection Submission

Record an objection on behalf of a stakeholder or a member of the public.

Comment Portal

Read, annotate and respond to comments extracted from documents.

Admin Decision

Compose, review and issue the administrative decision. The drafting service behind it is in development.

In each phase, people and services work on the same procedure.

Caseworker

Owns the procedure and every decision in it, and sees what the services found and what is still missing.

Intake

Documents are parsed, read with OCR where needed, split by structure and indexed. Completeness and coherence checks run on the result.

Participation and assessment

Objections and comments have their own services. Norm matching proposes the applicable law, and subsumption and risk notices test the facts against it.

Decision

A drafting service composes the decision and renders it to PDF for the caseworker to edit and issue. It is in development.

Each role keeps its job and loses the searching.

Caseworkers

Reads every page for missing itemsChecks a completeness report

Procedure Portal and Case Review match files to statutory requirements and flag gaps and inconsistencies. The caseworker confirms or corrects each finding.

Searches for the norms that applyReviews a proposed set of norms

Norm matching proposes the applicable law from the citations in the application and from the knowledge graph. The Report Portal shows it for review.

Drafts the decision from a blank pageEdits a structured draft

Admin Decision composes the decision from the reviewed results. The drafting service behind it is in development.

Participation

Sorts objections by handTriages objections in one place

Objections Management tracks, triages and helps answer objections. Objection Submission records one on behalf of a stakeholder or member of the public.

Copies comments out of documentsAnswers comments in context

Comment Portal shows comments extracted from documents, so the team can read, annotate and respond.

Technical and governance

Builds each integration from scratchCalls only the services it needs

Integration engineers use the REST APIs without the bundled UI. An XÖV adapter converts XPlanung, XTrasse and XBeteiligung messages to and from JSON.

Cannot see how an output was reachedTraces each result

Explainability, feedback and test-result services record how outputs were produced and how users rated them. They are in development.

Is tied to one modelSwaps the model at the gateway

Operators run the stack with Helm and point every service at a LiteLLM gateway by alias, so a model change is a gateway change.

How to start

Start with one part of the procedure and add services as they prove useful.

Step 1 Explore the code
Read the open-source repository and its documentation, and run a service locally.
Step 2 See a walkthrough
Go through the caseworker modules and the services behind them with the team, on sample documents.
Step 3 Pilot on your law
Ingest your jurisdiction's legislation and run one procedure type through intake and norm matching. [Replace: pilot terms and who runs the environment.]

Some parts are still being built, and we say which.

Roadmap: German and French UI, with English as the default. The UI is English only today.
In development: French law through every extraction stage, and a French jurisdiction configuration.
Roadmap: token verification on every backend. Today only a few services check the login token.
In development: durable storage for the audit trail, and staging and production environments.

Choose how to try it on your own procedures.

Explore the open-source code, book a walkthrough, or talk to us about a pilot on your jurisdiction.

Ways to get started