Product & category
What is Sanctum Lex?
In brief
Sanctum Lex is a governed legal intelligence environment built around matters. Workspace, the Console and Enterprise Command connect legal professionals, source material, analysis and institutional work. Core, One and Optimus provide distinct intelligence modes for reasoning, objective-led work and strategy. Persistent matter context, Stances, Authority Check, governed agents and work products carry understanding into action, with permissions, provenance and professional review throughout.
Product facts
- Product
- Sanctum Lex
- Category
- Governed legal intelligence environment
- Environments
- Workspace · Console · Enterprise Command
- Intelligence
- Core · One · Optimus
- Audience
- Law firms · In-house legal teams · Financial institutions · Professional services
- Work
- Matter analysis · research · professional challenge · agents · work products
- Deployment
- Enterprise and private deployment options; controls depend on the agreed configuration
What problem does Sanctum Lex address?
A legal question often depends on more than one document or conversation. Sanctum Lex is designed to connect sources, chronology, issues, positions and prior findings around the work rather than treat each prompt as an isolated file.
The environment brings matter understanding, analysis, professional challenge and delivery together. Teams can build on the work already done, with a source record they can inspect.
What do Matter Brain and Stances mean?
Matter Brain is the persistent evidence and structured intelligence associated with a matter. Context carries forward across the matter, and source references support primary-evidence inspection.
Internal Strategy, Opposing Counsel and Judicial Review examine the same authorized record with different analytical objectives. They support professional challenge and preparation; they do not represent an actual opponent or a court.
How are research and work products connected?
Authority Check supports a separate reviewable research path for legal propositions. A matter source citation and verified public-law authority are different forms of support. Unchecked law should not be described as verified.
Governed agents and drafting workflows can prepare work against the permitted matter context. Consequential advice, filings and decisions remain subject to professional review.
Workspace, Console and Enterprise Command
Sanctum Workspace connects colleagues, sources, work products and ongoing work. The Console is the environment for substantive matter analysis, research, professional challenge and drafting. Enterprise Command provides the firm operations environment.
These are connected environments within Sanctum Lex, not separate brands or disconnected document tools. Deployment and enterprise controls support the organization around the professionals doing the work.
Core, One and Optimus
Core provides universal intelligence for reasoning, analysis, creation and execution. One keeps the objective in view as knowledge, people and work evolve. Optimus examines competing approaches and challenges assumptions for strategic work.
The intelligence modes offer different ways to approach the work within the Sanctum environment. Internal Strategy, Opposing Counsel and Judicial Review are distinct review perspectives, not alternative names for these modes.
A global legal environment
Sanctum Lex supports jurisdiction-aware and multilingual legal work, including cross-border matters. The relevant jurisdiction, source language and professional context belong with the question being answered.
Global work still requires local judgment. Applicable law, research availability, data location and deployment requirements should be assessed for the institution and jurisdictions involved.
Enterprise deployment and control
Sanctum Lex describes private deployment options, identity controls and approved processing routes. The agreed architecture determines tenancy, residency, retention and model egress. A private deployment must not be assumed to have zero external egress.
Zero external model egress is a configuration-specific description: inference must remain within the defined private boundary and outbound model routes must actually be denied. Review the current control boundary with the deployment team.