Obligation tracking
Commitments, deliverables, and covenants extracted from executed agreements and kept as structured obligations with owners and dates — not as highlights buried in a PDF.
Platform
Enterprise Search One search bar for everything you know Knowledge Graph Every fact carries a receipt Agent Studio AI teammates that follow policy App Builder New One prompt to a live applicationApplications · LACE Legal
Contract intelligence with the receipts attached.
LACE Legal tracks obligations, renewal and notice-period deadlines, and conflicts across document versions — with every extracted term linked to the clause it came from. Point-in-time queries answer what the organization knew, and when, for investigations and litigation holds.
Renewal and notice-period surveillance
Auto-renewal dates and notice windows are computed from the governing language and surfaced before the window closes, so evergreen terms do not renew by inattention.
Version conflict detection
When an amendment, side letter, or superseding master agreement contradicts an earlier term, the conflict is flagged with both sources side by side rather than silently overwritten.
Clause-level citations
Every extracted term links back to the specific clause, document version, and page it came from. Review means checking a citation, not re-reading the contract to see whether the model was right.
Point-in-time queries
Ask what a given obligation looked like on a specific date. The bitemporal graph separates when a fact was true from when the organization recorded it — the distinction discovery and investigations turn on.
Review workflows
Extractions route to counsel for confirmation before they become relied-upon facts. Approvals, rejections, and edits are all part of the record.
In practice
A vendor asserts a renewal took effect. LACE Legal returns the governing clause, the amendment that changed the notice period, the date each version was executed, and what the contract record showed on the day notice was due — every element citing the document and page it came from.
Under the hood
Built so the extraction is defensible.
Evidence-locked, not summarized
An extracted term is stored with a pointer to its source span. If the source document is superseded or corrected, dependent facts are flagged rather than left standing on a citation that no longer says what it did.
Bitemporal by default
Facts carry both valid time and transaction time. That is what makes 'what did we know and when' answerable years later, and what keeps a retroactive correction from quietly rewriting history.
Permissions that respect the matter
Retrieval is permissions-aware at query time, so matter-level walls and litigation holds are enforced when a document is reached — including for agents drafting on a lawyer's behalf.
FAQ
What enterprise teams ask.
How does LACE Legal avoid hallucinated contract terms?+
Extractions are evidence-locked: each term stores a pointer to the exact clause, document version, and location it came from, and the citation is shown with the answer. Terms route through review before they are treated as relied-upon facts, and if the source document is superseded, dependent facts are flagged.
What is a point-in-time contract query?+
It is a query that answers what the contract record showed on a specific past date, rather than what it shows today. LACE stores facts bitemporally — separating when something was true from when it was recorded — so retroactive corrections do not erase what the organization actually knew at the time.
Can LACE Legal detect conflicts between contract versions?+
Yes. Amendments, side letters, and superseding agreements are resolved against the base agreement, and contradictory terms are surfaced as explicit conflicts with both sources shown, instead of the later document silently overwriting the earlier one.
How are matter-level confidentiality walls and litigation holds enforced?+
Access is evaluated at retrieval time against the requesting identity, so a document outside a person's permissions is never reached, summarized, or cited. The same enforcement applies to agents acting on a user's behalf, and every access is logged.
MCP Server
Works where you work.
The whole platform is an MCP server. Connect it once, and the AI tools your team already lives in can search your knowledge, ask the graph, and put governed agents to work — same permissions, same citations, same audit trail, wherever the question is asked.
- Claude Cowork Delegate the busywork
- Claude Code In your terminal
- ChatGPT Ask in chat
- Codex Ships the code
- Microsoft Copilot Across Microsoft 365
- Cursor In your editor
One endpoint — every MCP client
Next step
Put the contract record on the record.
We set up a pilot on your documents and one workflow your team actually runs. You judge the working output — in weeks, not a quarter-long project.