Each agent does one job and hands back a proposal — a recommendation, a packet, a draft, a flag. Nothing is filed, sent or changed until a person says so, and every answer names the records it came from.
File, send or change anything without an attorney's approval.
See another firm's data. Every run is scoped to one firm.
Answer without citing the records they relied on.
Send client-facing work, or anything that reads as legal advice, without a person. Those artifact types are policy-gated before they can even be approved.
Each has a trigger it waits for, one thing it produces, and the person whose approval it needs.
Intake triage
Reads a new intake and recommends where it should go: practice area, urgency, and who should own it. Also runs on demand from the review queue.
Deadline detection
Scans intakes and every uploaded document for dates that matter and proposes calendar entries for them.
Matter setup
When a routing recommendation is approved, opens the matter with its niche checklist, folder structure and first tasks.
Lifecycle snapshots
Records where each matter stands every time an approval is granted or rejected, so the history is never reconstructed from memory.
Research head-start
Once the matter is set up, drafts a first research brief on the issues it raises, with the sources it drew on.
Client health
Checks every client relationship daily and on day zero: silence, missed payments, unanswered questions, and flags the ones drifting.
Email triage
Classifies every message that reaches the firm's connected inbox, links it to a matter, and hands official notices onward.
Official notices
Handles government notices the Email Agent flags, creates the record, and escalates when nobody has responded.
The morning brief
Writes the Daily Brief: what changed overnight, what is due, what is waiting on a decision.
The same five steps every time, whichever agent is working and whatever set it off.
Something happens in the firm: an intake is submitted, a document is uploaded, an email arrives, an approval is granted, the day starts.
The event bus routes it to the right agent with a priority. Watch Rules can filter before any model runs.
The agent assembles matter context within a token budget, does its one job, and logs cost and citations.
The result is an artifact in the Review Queue: a recommendation, a packet, a draft, a flag.
An attorney approves or rejects. Approval can itself be an event that wakes the next agent.
Approval can itself be an event. A routing recommendation that an attorney accepts is what wakes the agent that opens the matter — so the chain advances on human decisions rather than around them.
Thirty minutes, on a call, with your own matter rather than a demo account.