Contracts Playbook

/ Overview

A contracts playbook is the firm’s positions written down: what to ask for, what to accept instead, and what to refuse. This demo drafts that from an agreement the user pastes, uploads, or loads as a sample. The model uses the agreement’s own party names. A person reviews each position, edits it, and confirms before the draft is finished.

The output is a draft for review, not a substitute for reading the contract. A confirmed playbook is stored in the val’s SQLite database. The public library opens a sample playbook stored there and does not list other records. Do not paste a confidential agreement into it.

/ What it does

• Starts from the job at hand: a full playbook, a format pass, a single clause, counterparty paper, or “not sure yet”.
• Drafts preferred positions, ordered fallbacks, positions to avoid, a risk label, and a quotation back to the source clause.
• Exports Markdown or Word from the confirmed draft. SQLite keeps each confirmed version. The public library shows the sample playbook, and a saved playbook can redline another party’s paper.

/ How it is built

File text is read in the browser. .docx and text-based PDFs are parsed locally; the extracted text is what the model sees. An optional redaction pass masks recognized patterns before that text is sent, then restores them for display. It is best effort and can miss things.

Model output is checked against a strict schema and against the source quotations before it is shown. Confirmation is a gate, not a default. The confirmed record is a row in val-scoped SQLite: the playbook, its version family, and a source excerpt. The file itself stays in the browser.