← all use cases
for legal teams ·one memory layer

Every commitment the company made, audit-ready.

Every 'we agreed to' needs a record. 3ngram keeps who promised what, when it is due, and the matter it belongs to in one queryable trail.

how it shows up ·memories your assistant keeps
  • commitment

    Promised to send the security packet within 30 days of signature.

    claude · −18d · halftide labs / msa
  • event

    Security packet draft assembled from the trust center; awaiting CEO sign-off.

    claude · −2d · halftide labs / msa
  • decision

    DPA review: added EU data residency clause; redlines accepted.

    claude · −12d · halftide labs / dpa
  • fact

    Renewal terms aligned with finance; 18% uplift confirmed for Y2.

    chatgpt · −3d · halftide labs / renewal
what changes ·with the loop closed
  • Every commitment keeps its who, when, and which matter on record
  • Deadlines stay attached to the matter they belong to
  • Clauses and renewal terms stay audit-ready
why it matters ·the shape of the problem

Halftide Labs has an MSA, a security packet deadline, a DPA clause, and renewal terms moving across different tools. 3ngram gives Legal one queryable trail of who promised what to whom, when it is due, and the matter it belongs to.

Legal work does not tolerate the kind of casual context loss that other disciplines have learned to live with. “We agreed to send that” is not useful unless you can show who agreed, when, where, and under which matter.

3ngram gives in-house practices a memory layer with an append-only audit trail. The Halftide Labs security packet, DPA clause, and renewal terms all stay tied to the matter they belong to, captured as your assistant works. Every commitment the company made stays queryable and audit-ready.

friction points ·what breaks, and what 3ngram does instead
01

Commitments hide in operational threads

Someone promised Halftide Labs the security packet within 30 days of signature. The deadline matters legally, but the promise lives in a Basecamp thread nobody rereads.

3ngram: The promise is captured as a typed commitment with its deadline and matter. It stays open on record and comes back whenever Halftide Labs comes up, instead of resurfacing as a compliance issue.

02

Clauses lose their approval trail

The DPA now includes an EU data residency clause and the redlines were accepted. Six weeks later, Legal needs to know where that position came from.

3ngram: The clause decision, the rationale, and the accepted redlines are captured against the matter, so the position and its history come back when anyone asks where it came from.

03

Commercial terms need legal continuity

Finance confirms an 18% uplift for Y2 renewal terms while Legal is still tracking the MSA obligations. The company made both commitments.

3ngram: 3ngram keeps commercial and legal commitments in the same queryable trail, scoped to the customer and matter they belong to.

faq ·the questions we hear most
How does matter-scoping work?
Each matter gets its own scope: a namespace for memory. Commitments and decisions captured under one matter never surface while you work in another, and recall respects the boundary in both directions.
Can the trail be audited?
Yes. Every memory carries an append-only audit trail: when it was captured, which actor wrote it, and what revised it. Corrections supersede instead of overwriting, so you can show how a recorded commitment reached its current state.
Is this compatible with our existing DMS?
Source sync for Google Docs and other document systems is on the roadmap. Today, the commitments and decisions your AI captures about those documents live alongside your existing DMS, not inside it.

Keep Every Company Commitment Audit-Ready

3ngram keeps promises, clauses, deadlines, and renewal terms on record under the matter they belong to, across every MCP client you work in.

get started free ↵