LEGALIR / Infrastructure

Build the institution’s own legal graph.

An agentic workbench for graph-based record management, built around permissioned retrieval units.

Sign in to learn more ↗
The permissioned thin filmInstitutional records remain in a lower plane. A thin policy boundary lets only permitted retrieval units reach approved agents above. Restricted information stays below.APPROVED AGENTSSCOPED RETRIEVAL ↑POLICY BOUNDARYPRIVATE RECORDSFIG. 03 / PREPARE ONCE. RETRIEVE UNDER AUTHORITY.
PROPOSED INFRASTRUCTURE / IN DEVELOPMENT
01

Begin with the record

Connect an approved collection, inventory its versions and establish its access boundaries. The proposed workbench helps knowledge teams classify records, identify legal entities and propose relationships. Original documents remain the source of record.

02

Agents propose. Institutions approve.

Extraction agents may suggest that a clause belongs to a contract, an opinion interprets a provision or an amendment changes an obligation. Proposed edges carry evidence anchors and confidence signals. Reviewed publication into the institutional graph is a separate permission, with human approval for consequential changes.

03

A taxonomy the firm can govern

A shared legal vocabulary can coexist with practice-specific and institution-specific classifications. Version the taxonomy and its mappings. Tax, governance and other purpose-trained language models can assist classification without making their labels authoritative by default.

04

Records and units remain connected

A record may contain many retrieval units; a unit may link to several legal entities and reviewed graph edges. Stable IDs, source checksums and version histories prevent a graph update from silently severing the relationship to the original evidence.

05

Private by construction

The proposed graph builder writes only within the institution’s authorized scope. Graph traversal enforces the same tenant, client and matter policy as document retrieval. A private edge is not published into the shared legal graph simply because it refers to a public statute.

06

A controlled change cycle

Import → propose → inspect → approve → publish → monitor. Rollback and correction should preserve the historical record, invalidate affected retrieval artifacts and make changes visible to downstream workflows.

Your knowledge remains yours.

Enter the reading room ↗