Lexware

§ I  ·  Thesis

Legal research with every cite verified.

A drafter writes the answer. A second model, with no view of the drafter’s reasoning, checks every citation against the source text. Claims that fail support are stripped. What you read is what was verified.

Sign inSee a specimen ↓

§ II  ·  Specimen

One paragraph, three pills, three statuses.

Under the “reasonable expectation of privacy” framework, courts evaluate whether the claimant exhibited a subjective expectation of privacy and whether that expectation is one society recognizes as reasonable1. The doctrine has been adapted to digital surveillance, with the Court holding that long-term cell-site location data implicates the Fourth Amendment2. Lower courts have split on whether the framework reaches a seven-day window of aggregated geolocation3.

§ III  ·  Process

Two models. One question of trust.

  1. 01

    Intake

    Your question and the matter context. A PII pre-pass strips identifiers before anything leaves the firm.

  2. 02

    Retrieve

    CourtListener and the firm’s own document index. Cached in the firm’s Supabase, never on a vendor server.

  3. 03

    Draft

    A first model writes the answer. Every factual claim is wrapped in a citation tag pointing to a retrieved source.

  4. 04

    Verify

    A second model, with its own context, sees only the draft and the source passages. Cite by cite, it decides whether the source really says what the answer claims.

  5. 05

    Deliver

    Claims we cannot find a source for are removed before delivery. What remains is marked Verified or Check this one, with the caveat shown inline.

  6. 06

    Audit

    Every cite, every verification, every routing change writes a row to your firm’s audit log. Append-only, queryable, yours.

§ IV  ·  Deployment

Three modes. The firm’s keys, or no service.

Platform

Vendor-hosted

We run the backend. Your Supabase, your Anthropic key, your CourtListener key, set in your environment. We never see your data at rest.

Standard isolation

Cloud

Firm-hosted VPS

You run the backend on your own VPS, behind your TLS. Point the frontend at your URL. We have no production access.

Sovereign isolation

Self-host

Tailnet / on-prem

You run the backend on a tailnet or on-prem box. Frontend connects only through your private network. Air-gappable.

Maximum isolation

In Cloud and Self-host mode, no vendor key, JWT, or client document ever transits a Lexware-controlled server; in Platform mode we operate the backend under row-level isolation. Read the security model →