§ I · Thesis
A drafter writes the answer. A second model, with no view of the drafter’s reasoning, checks the answer’s citations against the source text. Every citation shows the result: “Verified”, “Check this one”, or “Not checked” when the check did not run. You can see which to rely on and which to read yourself.
§ II · Specimen
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
01
Your question and the matter context. A PII pre-pass strips identifiers before anything leaves the firm.
02
CourtListener and the firm’s own document index. Cached in the firm’s Supabase, never on a vendor server.
03
A first model writes the answer. Every factual claim is wrapped in a citation tag pointing to a retrieved source.
04
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.
05
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.
06
Every cite, every verification, every routing change writes a row to your firm’s audit log. Append-only, queryable, yours.
§ IV · Deployment
Platform
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
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
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 →