Illustrative reference architecture. Validate requirements for your organization.
Illustrative architecture: A legal team prepares a chronology for a commercial dispute using correspondence, contracts, invoices, and witness materials. Reviewers need consistent references and a clear account of conflicting evidence. Agents assist document organization and drafting; the architecture does not supply legal advice or autonomous litigation strategy.
Problem
Documents may be privileged, restricted to particular teams, duplicated with changed metadata, or subject to preservation obligations. A generated chronology can make unsupported factual assertions or expose one matter's confidential material through shared retrieval.
Why a multi-agent system?
Ingestion, chronology, citation, and review-coordination specialists operate within a matter-specific boundary. The evidence store preserves original files and extraction lineage; lawyers determine relevance, privilege, legal interpretation, and final work product.
Intended outcome
The intended result is a reviewable operational decision with source evidence and explicit ownership. Evaluate evidence preparation and citation quality while keeping legal outcomes outside the agent's claimed contribution. The useful deliverable is a reviewable record of what documents support, not an automated opinion about the merits of a matter.
Specialist agent team
Matter intake agent
Index authorized documents and preserve file hashes, custodians, and source metadata.
Tools
Matter repository
document parser
Authority boundary
Cannot delete preserved material or change original evidence.
Chronology analyst
Extract candidate events with dates, participants, and exact supporting passages.
Tools
Document search
date normalization service
Authority boundary
Cannot resolve disputed facts or infer missing events as established truth.
Citation verifier
Check draft references against source passages and document versions.
Tools
Citation lookup
page coordinate viewer
Authority boundary
Cannot fabricate authorities or treat a quotation as legal analysis.
Review coordinator
Route disputed facts, missing evidence, and confidentiality questions to assigned lawyers.
Tools
Review queue API
work-product draft tool
Authority boundary
Cannot determine privilege, contact parties, or file documents.
Enterprise systems
Matter management platform
Owns team membership, assignments, client scope, and approved work-product records.
Evidence repository
Retains original documents, preservation metadata, extraction versions, and controlled access.
Lawyer review workspace
Separates candidate findings from accepted facts and records reviewer decisions without exposing protected material to general search.
Architecture diagrams
Matter evidence and chronology workspace — logical architecture — Specialists produce bounded findings; the evidence ledger preserves source versions and human decisions before an authorized adapter changes a system of record.
Failure and decision sequence — A shared retrieval cache returns another matter's document. The workflow records unresolved work and resumes only after the source state and reviewer authority are checked.
sequenceDiagram
participant O as "Case orchestrator"
participant S as "Matter management platform"
participant H as "Accountable reviewer"
O->>S: Retrieve matter-scoped evidence
S-->>O: Candidate document with foreign matter ID
O->>H: Block result and report isolation fault
O->>S: Repeat retrieval with verified partition
O->>H: Present authorized source-bound chronology
Runtime flow
1
Establish matter scope
Bind every job to an authorized matter, reviewer, evidence collection, and permitted processing purpose.
2
Ingest preserved copies
Parse working copies while retaining original hashes and custody metadata; quarantine unsupported or corrupted files.
3
Extract candidate events
Normalize dates with timezone and uncertainty metadata and retain exact passages supporting each proposed event.
4
Check citations and conflicts
Verify document versions and expose contradictory accounts rather than choosing the most fluent narrative.
5
Route professional review
Present lawyers with evidence-linked chronology entries and separate queues for privilege, relevance, and factual disputes.
6
Publish accepted work product
Save the reviewed revision with source manifest and access policy; later evidence changes create a new review revision.
Failure recovery
A shared retrieval cache returns another matter's document.
Detect: Matter-bound authorization checks reject the cached document identifier before rendering.
Recover: Discard the result, investigate the cache partition failure, and rerun retrieval within the authorized matter boundary.
A draft event cites the wrong document revision.
Detect: Citation verification finds the passage missing or materially different in the referenced file.
Recover: Remove the unsupported assertion and require a fresh source-backed entry for lawyer review.
Security & decision boundaries
Enforce matter isolation in retrieval, caches, exports, prompts, and reviewer workspaces.
Preserve original evidence and custody metadata under the team's established retention process.
Keep privilege and legal interpretation decisions with qualified lawyers.
Treat document instructions as untrusted content incapable of authorizing tools or disclosure.
Require source passages for factual chronology entries and label unresolved contradictions explicitly.
Operational metrics
Measurement definitions, not promised improvements.
Citation validity
Audited citations resolving to the stated passage and version divided by audited citations.
Chronology correction rate
Candidate entries materially changed or rejected by lawyers divided by reviewed entries.
Matter isolation violations
Cross-matter access attempts that return protected content, monitored separately from correctly denied attempts.
Review preparation time
Elapsed time from authorized collection availability to lawyer-reviewable chronology and exception queues.
Architecture tradeoffs
Decision
Benefit
Cost
Matter-specific indexes
Reduce cross-client information exposure.
Increase storage and index-management overhead.
Source-bound chronology
Makes factual claims inspectable.
Ambiguous dates and contradictions require deliberate review.
Immutable evidence copies
Preserve reconstruction of the record.
Retention and storage obligations need separate operational management.