Enron
The FERC public-record email release, with custodian metadata intact — the same shape eDiscovery teams already work with. Tested with real custodian folders, not synthetic samples.
For legal teams
Legal AI your firm controls — and your carrier can audit.
Runs inside your firm's network. Every answer traces to a specific page in a specific source. The model and the data stay where you keep them. The audit log is tamper-evident — the kind of record you want in hand the day a deal blows up.
What KAOS does for legal work
Research with verified citations. Drafting with traceable sources. Deal-room review with a spend cap.
Verified-citation legal research
Every citation in a draft is pulled out, looked up against the actual published source, and checked to see whether the source really supports the sentence it sits next to. Anything the system cannot verify is flagged for the lawyer to read, not smoothed over. No invented cases.
Drafting from a corpus you can audit
Every sentence the system produces carries the source location it came from — the document, the page, the exact passage. Privileged material is fenced off by matter, so a draft for one client never reaches into another client's files.
Deal-room review with a hard spend cap
Run a research agent across a thousand-document deal room with a hard spend cap per session, per day, and per matter. The agent stops when it hits the cap. No surprise bills, no runaway agents, no "we left it running over the weekend" stories.
The compliance horizon
AI in legal work — the dates that matter.
EU AI Act enforcement is staggered through 2027; US state guidance arrives in waves. KAOS was built around the obligations these regimes converge on: trace every claim to its source, refuse when uncertain, and keep an audit log a regulator can read end to end.
Where the obligations meet
Control, audit, and open code in the same toolkit.
A hosted vendor can give you one or two of these three. KAOS sits where all three meet — the same property that makes the platform inspectable also makes it self-hostable, and the same audit trail that proves the work was done correctly proves it was done inside your network.
How KAOS meets the obligations you already have
Competence, privilege, redaction, cost — the pieces a partner has to defend.
ABA Model Rule 1.1 — competence
A supervising lawyer can check what the system claims, sentence by sentence. Every citation traces back to its source; the system refuses when it isn't sure rather than guessing. The Comment 8 obligation to keep abreast of changes in technology is far harder to meet with a black-box vendor than with a system you can inspect.
Privilege and confidentiality
Privileged data stays segregated by matter and never crosses clients. The audit log is tamper-evident — required reading the day a deal blows up. KAOS runs inside your firm's network; nothing has to leave for the system to work.
Redaction
The system tracks redactions as first-class annotations on the document. PDFs can be re-rendered with the redactions actually burned into the file, not just hidden in a viewer where the underlying text survives copy-paste. The audit trail shows exactly what was redacted, by whom, and why.
Cost ceilings
Set a hard cap per session, per day, per matter, per user. The system stops cleanly when the cap is reached and tells you why. No surprise bills, no runaway agents, no awkward conversations with the finance committee.
Tested against real public records
The same documents your firm already works with.
The integration tests run end to end against the corpora attorneys actually live in: a custodial email release for eDiscovery, SEC filings for diligence, a regulatory ontology for clause classification, the LEI registry for counterparty lookups, the Federal Register for comment-period work, the eCFR for the version of a regulation in force on a date that matters. Not synthetic prompts written by engineers.
See the legal & financial use cases on learn-kaos, or run the first example yourself.
EDGAR
SEC filings pulled directly from the source: 8-K, 10-K, DEF 14A, S-1. The same filings you go to when a counterparty's most recent disclosures matter — pre-deal diligence, securities-litigation discovery, an executive-comp benchmarking memo. No third-party broker between the filing and your draft.
FOLIO
The shared ontology that lets a system answer "find every governing-law clause that points at a Delaware court" or "label every non-disclosure provision in this NDA." A working vocabulary for finance and capital-markets work, not a thesaurus.
GLEIF
Roughly 2.5 million legal entities indexed by LEI. Public API, no key. The lookup you reach for when a counterparty diligence list lands on your desk and you need to confirm the actual contracting entity behind a brand name.
Federal Register
Direct connector for tracking proposed rules, final rules, and notices through the comment period — the day-to-day work of a regulatory or government-affairs practice. No vendor-of-record, no rate-limit surprises during a comment-period sprint.
eCFR
Pull the version of a Title, Part, or section that was in force on the date the conduct happened — not whichever version the search engine returned today. The version a litigator or compliance officer needs to cite cleanly.
For your security and procurement teams
The diligence answers are already public.
Before code touches privileged data, your security and procurement teams will ask who maintains it, whether it is license-clean, and whether the build can be tampered with. KAOS answers those on a public compliance dashboard — every package carries a signed build attestation and a software bill of materials, the dependency tree has zero GPL/AGPL, and every claim links to evidence you can re-check yourself. No NDA, no questionnaire round-trip.
For the motivated practitioner
Read the book. Run the scenarios. Build something for your practice.
Vibe Coding with KAOS is the lawyer-facing on-ramp. No formal software background required — a few weeks of working with Claude Code is enough. Each chapter ends with a real command you run against a real document and get a real answer back. Companion to the conceptual minibooks at ai4lf.com.
Built at 273 Ventures.