Sub-verticals
Four calling-side shapes; one shared platform.
Matter management and case work
Matter opening, conflict checking, and case-timeline drafting. The agent prepares; the solicitor approves anything that reaches the client. Conflicts surface as flagged actions on the audit chain rather than silent decisions.
Action classes
Human-approval gating
Client-facing communication is gated behind solicitor approval; matter.opened and conflict.flagged are recorded for supervisory review.
Primary regulators (maps to)
- SRA Standards and Regulations (Code of Conduct)
- Legal professional privilege
- GDPR (case data)
Contract drafting and review
Clause drafting and deviation flagging against the firm's standards. Sensitive client data is tokenised before the agent reasons over it, and redlines are audited so a reviewer can detect prompt injection in the returned text.
Action classes
Human-approval gating
Sensitive client data is tokenised; redlines are audited for prompt injection, and the supervising solicitor approves any client-facing draft.
Primary regulators (maps to)
- SRA Standards and Regulations
- Legal professional privilege
- Jurisdictional contract-law disclosures
E-discovery and document review
Document classification and privilege flagging across a review set. The audit chain integrates with predictive-coding and computer-assisted-review workflows so a production manifest is reconstructable.
Action classes
Human-approval gating
privilege.flagged candidates are conservative by design; the firm's privilege-review workflow confirms each one. Predictive coding and CAR decisions are recorded on the chain.
Primary regulators (maps to)
- SRA Standards and Regulations
- US FRCP (cross-border discovery)
- Sedona Conference principles
Court filings and case management
Filing drafting and deadline recording. The agent drafts and tracks; the solicitor signs off on any actual filing. Recorded deadlines surface on the audit chain so a supervising partner can reconstruct the matter timeline.
Action classes
Human-approval gating
filing.drafted is gated behind solicitor sign-off for any actual filing; deadline.recorded is captured for supervisory review.
Primary regulators (maps to)
- Court rules of procedure (CPR for England and Wales)
- SRA Standards and Regulations
- Professional indemnity insurance requirements
Adapter coverage
Upstream services Vortalis adapts for this sector.
- iManage WorkShipping
vortalis_proxy/services/imanage.py
Document management API. Privilege detection on document text fields; per-tenant pattern set extensible via Tenant.config.
- NetDocumentsShipping
vortalis_proxy/services/netdocuments.py
Document workspace and folder API. Tokenisation of client and matter identifiers; privilege detection on document content.
- ClioShipping
vortalis_proxy/services/clio.py
Matters, documents, contacts, notes, activities, and communications. Privilege detection on note and communication bodies.
- RelativityShipping
vortalis_proxy/services/relativity.py
E-discovery workspace API. Privilege detection on extracted text and email subjects; production manifest captured in the audit trail.
Honest limits
What this sector pack does not do.
Vortalis does not file with a court; it governs the AI agent's action.
The platform records what the agent drafted, what the policy decided, and what the solicitor signed off. The actual filing happens in the operator's existing systems, behind a solicitor's sign-off. Vortalis records the decision and the upstream outcome; it does not file.
Counterparty certification with each document-management platform is the operator's responsibility.
Vortalis ships the iManage Work, NetDocuments, Clio, and Relativity adapters as code, not as counterparty-certified production integrations. The operator's contract with each upstream vendor governs the conformance and rate-limit conventions of the upstream service.
Privilege determination remains the solicitor's professional judgement, not an AI agent's autonomous decision.
The DMS adapter base applies a marker-based detector and records the classification on each audit row. The detector is conservative (it flags candidates rather than missing them) and is not a substitute for the firm's privilege-review workflow. The legal determination of what is privileged in a given jurisdiction is the solicitor's, encoded in policy and tenant configuration.
Cross-border discovery under FRCP versus CPR remains the firm's track.
A matter that spans US discovery under the Federal Rules of Civil Procedure and disclosure under the Civil Procedure Rules for England and Wales requires the firm to determine which track governs each step. Vortalis records the agent's actions consistently across jurisdictions; the regulator-facing determination of which procedural rule applies is the firm's.
The general-purpose honest limits sit at /product/security-architecture; this list is specific to the legal pack.
Sample scenarios for illustration
How operators put the pack to work.
These are illustrative deployments, not customer references. No named customer testimonials appear here, because the first external engagements are still landing. Each scenario describes a plausible shape of a Vortalis deployment in this sector.
Illustration 1
A UK law firm deploying a contract-review agent on an iManage Work repository, governing SRA Code of Conduct obligations and legal professional privilege through Vortalis. The agent reasons over a tokenised view of client data, and the supervising solicitor approves every client-facing redline before it leaves the firm.
Illustration 2
A litigation team running an e-discovery agent against a Relativity workspace, governing US FRCP cross-border discovery and the Sedona Conference principles through Vortalis. Privilege-flagged candidates route to the firm's review workflow, and the production manifest is captured on a signed audit trail.
Illustration 3
A disputes practice deploying a court-filing agent on a NetDocuments matter, governing the Civil Procedure Rules and SRA supervision obligations through Vortalis. Every filing.drafted action stays behind the solicitor's sign-off, and recorded deadlines surface on the chain for the supervising partner.
Evidence-pack preview
Signed. Offline-verifiable.
A sample SRA and privilege evidence pack, showing the structure of a signed, offline-verifiable pack. Signed. Offline-verifiable.
Download the sample legal evidence pack (PDF)Sample artefact. This is a placeholder evidence pack for layout and review; a real signed, offline-verifiable pack replaces it before launch.
Bring Vortalis to your legal agents.
Pick the sub-vertical above. Read the integration brief if you would rather start with the engineering detail. Talk to us first if you would rather start with a conversation about your threat model.