Trust

Inspect the evidence and its limits.

Read the source, follow the finding and know the limits of the check.

Start with the evidence available to inspect today, then the handling terms that must be established before client work begins.

Synthetic reports and recorded checks

These checked-in examples use synthetic material. Each links its input or output to a recording that states what ran and what remained outside the check.

Sample Chambers Reports

Two sample Chambers Reports, built from synthetic briefs, show the finding index, per-finding cards and annotated source passages that a check returns.

Dated September 2026 builds. They show what a check returns; they do not measure performance on other drafts.

Verification record

Data source pending

Last verified: Pending publication

Evidence pending publication. No product-wide test count, blind-corpus result or false-accusation rate is claimed here.

Read the JSON source →

Published as a static snapshot at build time. The verification timestamp identifies its age; this is not a live monitor.

Internal test evidence: publication pending

Copy reviewed October 20, 2026. No dated, release-specific obstacle or adversarial result is published here. Each measured statement must identify the corpus version, tested commit, result and test date before publication.

A result on an internal test set applies to that set and release. It is not a guarantee for other drafts or sources. Capability descriptions explain what Aletheia is designed to detect; counsel must inspect the evidence and review the findings.

Document custody before onboarding

The hosted product is designed as a browser-based service hosted on our own dedicated infrastructure. This is design intent, not a current service guarantee. The handling below is a basis for the access conversation; agreed terms must identify the actual services and controls before onboarding.

Matter documents
The design goal is to keep matter storage and processing on our own dedicated infrastructure. Technical enforcement is not yet implemented and verified. The agreement must specify locations, authorised access, subprocessors and any exceptions.
Public-source lookups
The design goal is to send citation strings only to CourtListener, not documents or arguments. This boundary is not yet deployed and verified. The agreed workflow must identify any outside research services and the exact information sent with a lookup. A source-search request and a client document need different handling.
Model providers and training
The access terms must expressly address whether information reaches an outside model provider and whether it may be retained or used for training. Infrastructure ownership alone does not establish those protections.
This public website
The enquiry form sends the contact fields you enter to Formspree. Use a general description of the work and keep client documents, privileged information and matter details out of the form.

Put the safeguards in writing.

Access requires a documented account of firm and user isolation, access controls, encryption and key management, backup and restoration, incident response, retention and deletion. The recorded demonstrations above establish none of those controls.

Preserving the history of a working matter is different from handling an account closure or deletion request. The agreement must explain time periods, exceptions, backup treatment and who is responsible for each step.

A missing source is a limit, not an accusation.

The Chambers Report says what could not be checked and what counsel needs to supply. It does not turn an unsuccessful lookup into a claim that a case is invented.

Agree the terms before the work begins.

Approved documents will be linked here. Reserved slots show where a document is still pending; no legal text has been drafted for those.

Terms

Document link pending

Data Processing Agreement

Document link pending

Discuss access and handling terms →