Work product
Ask the file. Check the answer.
A question against a ten-thousand-page matter, answered in the time it takes to read the answer — with every claim linked to the document and page it came from, so you check it before you rely on it.
The rule that makes it usable
It will not cite what it was not given
Drafting works from this matter's own record. Where a legal citation is needed and the record does not supply one, the draft says [CITATION NEEDED] rather than producing something plausible.
What it does cite is checked. Every case citation is resolved against CourtListener's free opinion database, and one that does not resolve is shown in red as unciteable rather than left for you to catch. That check is existence and citation accuracy — not Westlaw, no treatment, no Shepard's signal. A citation that resolves can still be bad law, and saying so plainly is the point: a confident "verified" that meant more than it should is the worst thing a tool like this could hand a lawyer.
What comes back is a draft to edit, not a filing. It is also read back to you as the other side would read it, which is the part most people find useful.
What is here
Case chat with citations
You can ask the file a question at four in the afternoon and have a cited answer before you leave, instead of blocking out a morning to re-read a box. Every claim links to its page, so you check it before you rely on it.
The question is matched against the fact ledger, and the model answers using only the facts retrieved. Citations are parsed back into document and page links, so any claim can be checked in two clicks. It is told to say what is missing rather than infer.
- Answers are informational and never enter the review queue.
- Retrieval is full-text over facts; no embeddings until a checkpoint proves need.
- It is a CONVERSATION, not a series of questions: a thread keeps the exchange, so "what about the second one?" works. Threads are per person as well as per matter — two attorneys on the same file are having two different conversations, and stitching them into one would put one lawyer's half-formed thinking into the other's context.
- It knows about EVERY feature of this software, one line each. Ask how to do a particular thing by name and it is given that feature's full steps for the question you asked; ask about something it was not given steps for and it says so and points you at the guide rather than inventing them. It will never make up a screen that does not exist.
Drafting with cite-check and red team
A first draft that already cites this matter's own record, plus a read of the other side's best answer, before you have spent an afternoon on it. What comes back is a draft to edit — every legal citation in it is resolved against a public opinion database, and one that does not resolve is marked unciteable.
Drafts are written from the fact ledger with inline citations. The cite-check pass tests every factual assertion against that ledger — and reports EVERY legal citation, resolving each against CourtListener for existence and accuracy. That is not treatment: a citation that resolves can still be bad law, and the page says so. The red team argues the other side's best response and names what the record supports that the draft missed.
- The model is instructed to write [CITATION NEEDED] rather than cite anything it was not given; what it does cite is resolved against CourtListener for existence and accuracy only — not Westlaw, no treatment, no Shepard's.
- Editing an approved draft revokes the approval, by database trigger.
- The pre-filing checklist is ADVISORY and always will be. It reads the requirements of the court and the judge your matter sits in, measures what can be measured, and says plainly what it could not check rather than calling it clean. A failing line does not stop you approving, exporting or filing anything: signing off records that an attorney read it. A requirement from a rule set your firm has not confirmed still appears, marked unverified — never dropped, and never shown as verified.
- A template is lifted only from a filing your firm authored, never from a pleading served on you, and it is not offered to anyone until an attorney has read the proposed structure and confirmed it. Your templates are yours: there is no sharing surface between firms, and nothing you confirm is ever lifted back into ours. When our version of a form moves on you are shown what changed and choose — nothing is merged into your copy.
- The firm keeps a memory of how it writes and what it has decided — its voice, notes on a judge or an opposing counsel, arguments and objections it has used, and the findings it has told the platform to stop raising. That memory reaches drafts, engagement letters, the forensic pass, the morning briefing and answers about a matter, so the product sounds like your firm rather than like a model. It is added by us or learned from a dismissal you explained; there is no screen to edit it, so what is in it is a question to ask rather than a page to open.
- Pleadings — complaints and answers built from a section tree, with the allegation ledger beside them — are their own capability, "The pleading builder". This entry is the prose drafting beside it.
The pleading builder
The paragraph numbers, the Count re-allegation ranges and the caption stop being things a lawyer re-checks by hand every time a paragraph moves. Every allegation the firm makes is written down beside what the firm will stand behind it with, before the pleading leaves the building rather than after the other side asks. And the court-formatted document is filed to the matter the moment it is exported, so the copy that went out is the copy the file keeps.
A pleading starts from a template — the platform's Florida circuit civil complaint, its answer, or one the firm lifted from its own filing and confirmed — and from the matter: the court identity, the parties, the counts chosen from causes of action a lawyer has signed off for that jurisdiction, and, for an answer, the affirmative defenses. The template is a tree of sections: fixed text, values the matter supplies, choices, computed paragraphs and prose the lawyer writes. The engine numbers the paragraphs and computes every "realleges paragraphs 1 through N" range, and an empty slot renders as a visible bracketed placeholder rather than a sentence with a hole in it. No model is called to start, edit, mark or export a pleading. When the pleading is started, each numbered paragraph it asserts is written to the Allegations ledger as unreviewed; an attorney marks each one supported, will be supported (which requires naming the source), information and belief, or strike. For an answer, the served complaint's numbered paragraphs are imported deterministically and each is answered admit, deny or without knowledge — every one arrives as without knowledge, and the matter's own facts that bear on a paragraph are shown beside it as a reading aid. Exporting renders the .docx for the court: the page, the face, the caption shape, the signature block and the jury demand come from that court's encoded rules where they exist and from the firm's default where they do not, and the export dialog says which is which. The same bytes are filed to the matter as a document, and a PDF/A copy is queued for the worker to produce.
- Formatting follows this court's encoded rules only. Where a rule for a field is not encoded, the firm's default is used and the export dialog says so, field by field — nothing is borrowed from another court's rules.
- It produces the filing and does not file it. Nothing here logs into a court portal, files with the clerk or serves anyone: the export puts a copy in the matter on this platform, and the attorney files with the court.
- An allegation is never a fact. The ledger records what the firm says and what it will stand behind; nothing in it is written to the fact ledger or read back into a draft as a source, and a paragraph marked supported is an attorney's judgment, not a finding.
- Nothing marks a paragraph for you. Every allegation starts unreviewed, and only an attorney changes that.
- The ledger is re-derived on every section save: an unchanged paragraph keeps its disposition and takes its new number; a changed one starts again unreviewed; a removed one is closed out, and earlier judgments stay readable as history.
- Prose inside a repeated section — one Count, or one affirmative defense — is drafted in the text below the section tree, not in the section editor.
- Causes of action and affirmative defenses are offered only for jurisdictions where a lawyer has read and signed off their elements; a court with none signed off is offered none, and the page says so.
- The PDF/A copy is typeset from the filed document's text in the platform's standard faces, not from the court's encoded profile; the profile governs the .docx.
Chambers
The thinking you would do with a senior colleague on a Tuesday afternoon, with the whole fact ledger already in view: simulate opposing counsel, value the case, outline a deposition, argue a theory until it breaks — without any of it touching the file. Nothing said in Chambers becomes a fact, a deadline, a filing, a draft, or a time entry.
A thread runs over this matter's facts with citations back to the page each one came from. A hard question can be escalated to a more capable model for that turn only, at exactly two and a half times the rate — the multiple is the model's own price in the rate card, not a markup added in the interface, and the checkbox says so before you send. The verbs (simulate, value, outline a depo) are the trial notebook's existing one-shots said as sentences; their results are stored where they always were, as internal decision support. Ethical walls bind Chambers exactly as they bind the matter page: a screened matter cannot be discussed, because its facts never enter the prompt. Every case citation in an answer is resolved against CourtListener, and one that does not resolve is marked unciteable.
- Chambers writes NOTHING into the record — no fact, no deadline, no filing, no draft, no time entry. It recommends; the attorney acts through the product's own review paths.
- Threads persist as firm records — there is no delete, by design. The application database role holds no DELETE on either table.
- Never client-visible and excluded from the export bundle by rule.
- Turn content is not covered by the per-document crypto-shred story; it lives in the database and its encrypted backups.
- Staff can read a thread; posting a turn is attorney-only.
Getting a filing past the portal
Nobody is at a free conversion website at eleven at night with a client's filing in it, because the two mechanical reasons a portal rejects a document are handled before it goes near one. Neither of those reasons has anything to do with the law, and neither should cost anyone an evening.
The document is converted to PDF/A, which is the archival format portals insist on, and if it is over the ceiling that portal allows it is split into parts that each fit. A bookmark outline can be built two levels deep — the section of the file the document sits in, and the title its reading gave it — because a clerk opening a two-hundred-page exhibit set will look for one. The plaintext exists only inside a private working directory that is removed when the run ends, whatever the outcome.
- It is an operator command, not a button on a screen. Ask us and it happens; there is no way for a firm to run it itself.
- The outline is as deep as the record is: two levels, from the file section and the document's own title. There is no per-page heading extraction anywhere in this platform, so there is no honest way to emit a bookmark per exhibit — and inventing one from a model would put made-up structure into a court filing.
- It does not file anything and does not talk to any portal. It produces a package that will be accepted; a person still uploads it.
What this page does not show you
There is no screenshot above, on purpose. Our demonstration matter is seeded without any chat threads or drafts, because both require a real model call — so there is no genuine picture of an answer to show, and we would rather show nothing than a mock-up of output the product did not produce. Ask for a demonstration and you will see it run against a live file instead.