Solutions · Legal

Privilege doesn’t survive on trust. It survives on proof.

The moment a firm puts an AI assistant on top of its documents, the question stops being “is it accurate?” and becomes “can you prove it never crossed a wall?” Trace Continuity answers that in writing, per retrieval, per matter.

Matter-level privilege boundaries

Memory is bound to a matter, not to a firm. An associate with full system access still cannot retrieve a record from a matter they were never granted. Tenant membership is not enough — access is explicit, dated, and attributable.

Ethical walls that beat every grant

A conflict screen is checked inside the execution gate, ahead of retrieval. It overrides access grants, roles and inherited authority. Raising and lifting a screen both require a reason and both stay in the record permanently.

Legal hold that the database enforces

A matter under hold is preservation-locked. Deletion is refused by a database trigger, not by application code that somebody could route around. Hold provenance — reason, who placed it, when — cannot be quietly rewritten.

The record a GC actually asks for

Every block produces evidence: who attempted it, which matter, which rule stopped them, at what second. Not a log line you have to reconstruct — a governance receipt showing all seven verification stages.

What the wall check actually does

  1. 1. Matter resolves inside the firm. A matter reference never crosses a tenant line — an unknown matter is a deny, not an empty result.
  2. 2. Conflict screen is checked first. A screened attorney is refused before access is even consulted.
  3. 3. A live grant must exist. Revoked grants fail closed, and the revocation reason travels with the denial.
  4. 4. Closed matters are read-only. No new material enters a matter after it closes.
  5. 5. Hold state is recorded either way. Allow or deny, the receipt shows whether the material is preservation-locked.

This runs on the same mandatory path as everything else in the platform: authority, governance, matter boundary, tokenization, storage, retrieval, audit. There is no code path that skips it.