Regulators covered
Which frameworks the legal pack maps to today.
Adapter coverage
Upstream services Vortalis adapts for this vertical.
- ClioShipping
Matters, documents, contacts, notes, activities, communications. Privilege detection on note bodies and communication bodies.
- iManageShipping
Document management API. Privilege detection on document text fields; per-tenant pattern set extensible via Tenant.config.
- NetDocumentsShipping
Document workspace and folder API. Tokenisation of client and matter identifiers; privilege detection on document content.
- RelativityShipping
E-discovery workspace API. Privilege detection on extracted text and email subjects; production manifest captured in the audit trail.
Action vocabulary
The policy template for this vertical.
Actions allowed
13
Each action gated by policy at the hot path.
Anticipated require_human actions
- contract.signed_off
- ediscovery.produced
- document.shared
Rate-limit posture
Per-day caps on the highest-risk action types: 50 external shares per 24-hour window, 10 e-discovery productions per 24-hour window, 20 contract sign-offs per 24-hour window. The firm raises any of these after agreeing the volume with the matter partner.
Template path: policies/sectors/legal/document-review-template.yaml
Integration brief
The implementation guide your engineers read first.
Available
docs/governance/integration-briefs/legal-document-review.md
Honest limits
What this sector pack does not do.
Vortalis does not provide legal advice; it governs AI-agent actions that draft, review, or produce legal documents.
The policy template gates thirteen actions including document.drafted, contract.redlined, and ediscovery.produced. It does not advise on the merits of a matter, choose the legal strategy, or substitute for the supervising solicitor. The legal judgement remains with the firm. Vortalis records what the agent did, when, and under whose authority; it does not adjudicate whether the agent should have been delegated the work.
Privilege detection is a Vortalis primitive; the legal determination of what constitutes privileged content in a given jurisdiction is the operator's responsibility to encode in policy and tenant configuration.
The DMS adapter base applies a marker-based detector and records the classification result on each audit row. The default pattern set covers the common UK and US privilege markers; a firm with jurisdiction-specific markers extends the set via Tenant.config["dms_privilege_markers"]. The detector is conservative by design (it flags candidates rather than missing them) and is not a substitute for the firm's privilege-review workflow.
Counterparty certification with Clio, iManage, NetDocuments, and Relativity is the operator's responsibility.
Per the public limitations page, Vortalis ships adapters as code, not as counterparty-certified production integrations. The four DMS adapters listed above are shipping code in the platform; the operator's contract with each upstream vendor governs the conformance and rate-limit conventions of the upstream service. The audit-chain evidence the firm presents to the SRA or the NY state bar is the Vortalis chain; the upstream's own audit trail remains a separate artefact.
State bar rules differ between jurisdictions; the New York rules are the first published state-bar mapping. Mappings for other states land as customers in those jurisdictions onboard.
A matter in California, Texas, Illinois, or Massachusetts requires a state-specific evidence-pack builder. The NY mapping is shipping; the package structure under vortalis_proxy/compliance/us_state_bars/ anticipates the other states. A matter run through the platform in a state without a published builder is governed but the regulator-facing evidence pack will not name that state's specific rule numbers. The honest framing is that the platform's runtime evidence is jurisdictionally consistent; the regulator-facing mapping is state by state.
The general-purpose honest limits sit at /security/limitations; this list is specific to the legal pack.
Bring Vortalis to your legal agents.
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.