LEGALIR / Infrastructure

A gateway with a duty to refuse.

Autonomous systems need explicit authority for every consequential operation.

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

Register the principal

An agent receives an identity tied to an accountable institutional owner. Its purpose, approved tools, model endpoints, data scope, usage budget and review requirements form a versioned grant. Personal account permissions must not silently become agent permissions.

02

Authorize at the data boundary

Evaluate the principal, tenant, client, matter, source rights, intended operation and current policy before retrieving text. Filtering only after a global search risks leaking restricted titles, snippets and counts. Deny by default and return a non-disclosing result.

03

Separate read from action

Reading a contract does not authorize sending it, editing it, signing it or contacting a counterparty. Consequential tools require a fresh explicit grant and human approval bound to the exact proposed action. Re-check policy after approval and before execution.

04

Contain untrusted instructions

Retrieved documents are data, not system instructions. Tool outputs and source text cannot widen an agent’s scope. Constrain tool schemas, validate destinations and test injection attempts that ask the agent to reveal other matters or bypass review.

Your knowledge remains yours.

Enter the reading room ↗