Darwin Axiom plans

Axiom is the Darwin Suite's product for legal work: a workspace where a firm's documents are read, compared and drafted with the help of a language model. Documents are gathered into projects, questioned one at a time in the Assistant or many at once in a tabular review, and the answers point back to the passage they came from.

For teams who work through volumes of documents: law firms, in-house legal departments and anyone whose day involves reading contracts, filings or correspondence to answer the same question across many of them. No technical knowledge is assumed. Questions are written in ordinary language, and the answers come back the same way.

Axiom signs in through the same account as the other Darwin products, so one set of credentials reaches all of them. A person may belong to more than one organisation; everything in Axiom -- projects, documents, reviews and analysis templates -- belongs to the account chosen at sign-in, and switching account changes what is on screen. Nothing is ever visible from one account to another.

A credit is a token actually consumed by the model, counted after each answer rather than estimated before it, so a short question costs less than a long one. The monthly allowance comes with the subscription plan and is shared by everyone in the account. When the balance reaches zero, the actions that call a model stop until the allowance renews or more is added; nothing already produced is lost, and everything already on screen stays readable.

A project is a matter: a named place to keep the documents that belong together, with a client or matter reference and a practice area. Reviews and conversations can be started inside it, and a document drafted in one of them is filed there. Work does not have to sit in a project -- a document can also live on its own in Files -- but a project is what keeps one matter's material in one place.

In two places. Inside a project, alongside the matter they belong to; or in Files, the library for documents that belong to no particular matter. Models keeps a separate library of document models to draft from. Wherever a document sits, every version of it is kept -- uploaded or generated -- and any version can be downloaded later, not only the most recent one.

Yes. A project and a tabular review each carry a list of the colleagues who may open them, chosen from the active members of the same account -- somebody outside the account, or a member who is no longer active, cannot be added. Sharing a project shares the documents in it. If any of those is private, Axiom says so before sharing and asks whether to make them readable or to leave things as they were.

It keeps the document to the person who put it there. Nobody else in the account can open it, download it or see it quoted, and it drops out of the rows of any review a colleague looks at, taking the answers extracted from it with it. The restriction follows the document rather than a copy of it: every version, every proposed change and any document drafted out of it inherits the same restriction.

A grid. The rows are documents and the columns are questions, and Axiom fills every cell by reading that document for that question. It is the answer to "what does each of these fifty contracts say about termination", asked once instead of fifty times. Each cell holds a short answer, the reasoning behind it and a pointer to the passage it rests on, so a surprising result can be traced to its source.

A column is a question written in ordinary language, and Axiom can suggest the wording. Columns can be added, renamed and removed while the review is open, and Fill extracts the answers for whatever the grid holds at that moment. Adding a document adds a row and fills it; removing one takes its answers away with it, so a grid never shows results for a document that is no longer part of it.

Yes. Every tabular review has a conversation beside it that can be asked what the grid found -- the outliers, the pattern across the rows, a summary to send on -- and that can draft a document out of the answer. The conversation reads the review's findings rather than the documents themselves, and it cannot change a document under review: material being reviewed stays exactly as it was.

The Assistant is a conversation about the documents attached to it. It reads them, answers in ordinary language and cites the passages it relied on, so an answer can be checked rather than taken on trust. Documents can be attached as the conversation goes on, and each question is answered against what was attached when it was asked -- the transcript stays a truthful record of what each answer was about.

Yes, in the Assistant and in a review's conversation alike. Ask for a document and Axiom writes it, files it where the conversation belongs and offers it for download. Ask for a change and it proposes one as a tracked change instead of overwriting the file: the proposal is read change by change, each accepted or rejected, and every version remains available afterwards.

A saved starting point. A tabular template holds a set of columns; an assistant template holds the instructions a conversation should follow. Starting from one copies what it holds, so the thought that went into a good set of questions is spent once and reused on every matter after it. The copy is independent -- editing the template later leaves reviews already created from it untouched.

Three choices are made once for the account, under API Keys and Models: which model answers conversations, which fills review cells and which names things. A user can also enter their own provider key there. When a key is present Axiom calls that provider with it, and the models on offer are those there is a key for; with no key of your own it falls back to the installation's. Keys are stored encrypted and are never shown again in clear.