01
Upload the opposing document
One pleading against this case only. The worker never loads other files for “office-wide” context.
Law-office AI
Analyse an opposing document against the whole case
The assistant reads a new pleading in case context, flags weaknesses, and proposes moves. The lawyer decides. Person data leaves the office only as stable codes.
Analyze the case. Find the issues. Examine the evidence. Research the law. Prepare the work.
You make the legal decisions.
The AI prepares the case. The lawyer decides the case.
Workflow
From filing to a lawyer-owned decision
01
02
Codebook before the model
Person, organisation and account strings become P-01, ORG-02, ACCT-03. The map stays in Symfony.
03
The lawyer records the move
Courses of action split fact, inference, issue and authority. Nothing files itself.
Product
Analysis that cites the page — in codes
A static sample of what work looks like after the codebook. No real names leave the office.
Control
Built for a single office, not a public docket
Codebook stays here
Models, Writing Assist and docsgen never receive the map. The UI may decode for view or work.
No grant is a 404
Owner and creator have work. Everyone else needs an explicit case grant. Missing access is not advertised.
The lawyer decides
Suggested courses of action are not filings. A work account records the decision on the brief.