PRIMARY REFERENCE IMPLEMENTATION

Evidence-aware memory
in a legal workflow.

MESA Law demonstrates how matters, documents, review, and sourced question answering can meet MESA through a versioned HTTP contract. It is a reference implementation, not a customer deployment.

THE USER PROBLEM

Legal context needs
its source and review state.

A legal workflow cannot safely treat an answer as detached text. The repository models source-aware document workspaces, evidence and citation cards, review state, and sourced QA that can abstain.

  1. 01Official legal sourceReviewed or configured acquisition
  2. 02MESA DataTraceable legal release
  3. 03MESA CoreAuthorized memory and evidence
  4. 04Versioned HTTPExplicit integration boundary
  5. 05MESA LawMatter, document, review, sourced QA

VERIFIED REPOSITORY SCOPE

Cases, documents,
review, and evidence.

Current code includes a Next.js web app, FastAPI and Java API work, workers, PostgreSQL migrations, document parsing, matter-level access controls, deadlines, review state, drafting controls, and provenance-aware QA.

Matter workspace

Tenant-scoped matters, parties, members, timelines, claims, evidence, and document revisions.

Human review

Review queues, immutable audit records, citation verification, and approval gates before external draft use.

MESA binding

Catalog onboarding and V4 mutation state are tracked over HTTP. A 202 admission is not presented as publication; only COMMITTED is success.

MVP limits

External legal research and AI draft generation are disabled in the documented MVP contract.

CURRENT STATUS

Historical Law-side gates passed.
Overall integration: NO-GO.

The 2026-08-01 report records isolated Law-side gates against Core 0.7.1. Full-stack and live Core integration were not run. The pinned Law report records failing CI; this is not Core 0.9.3 integration proof.

Read verification report

NEXT STEP

Where to go from here