Start here
Orchestrate.legal is for people moving legal AI from isolated tools into controlled legal work. Pick the entry point that matches your question; you do not need the whole mental model on day one.
Core contrast
Most tools still optimise for Document → Prompt → Answer. That pattern is useful for narrow tasks, but it hides intent, sequencing, review, permissions and matter history.
Coordinated legal work follows a different shape: Task → Plan → Route → Execute → Review → Monitor. Everything on this site, model, demos, playbooks and writing, is organised around that contrast.
Choose your path
Each link answers a different practical question.
If you are thinking about architecture, start with the Reference Model.
It defines the primary flow, terminology and how routing, gates, matter state and audit fit together.
If you are designing controls, start with Execution Gates.
See how destination and reliance change whether an output may proceed, with governance applied at the point of action.
If you are deciding where AI work should run, start with the Routing Simulator.
Task shape, sensitivity and budget drive path: model tier, governance band and review, not a generic “best model.”
If you are trying to explain the wider argument, start with the writing series.
Pieces are grouped by theme so the argument can be followed across orchestration, governance, evaluation, matter state and private inference.
Also useful
- Matter State Viewer: what the system should know about the live position of the matter, not only documents.
- Playbooks: methods you can take into a firm or product team.
- All demos: short demos using mock data and fixed rules.