Document work

Generate documents

Ask the assistant to produce a document and it generates a downloadable artefact – DOCX, PDF, XLSX, HTML, or Markdown. The contract is generate-then-download: a revision is a follow-up prompt that regenerates, rather than in-place editing. HTML artefacts get a sandboxed Preview/Code toggle.

Every non-Markdown artefact passes a validator before it's returned (DOCX is also schema-checked), so a corrupt file is never handed back. Output branding (the DOCX reference template, PDF CSS, HTML theme) is configurable with neutral defaults. Artefacts live with their chat and are deleted when the chat is.

Tracked changes (accept / reject)

In the legal workspace, documents are first-class with version history and provenance. When the assistant proposes edits, Fosnie rewrites the DOCX as real tracked changes under a Fosnie author, and you review them inline:

• Accept or reject one change, all at once, or by author (e.g. accept the assistant's edits, keep your own).
• Accepting or rejecting creates a new version. A citation made against version 1 still resolves against version 1 after version 2 exists.

Anyone with edit access (via the sharing model) can do this – it's not a special role.

Tabular review

Extract structured answers across many documents at once. A review is a matrix – rows are documents, columns are extraction prompts – producing a grid of answers, each with reasoning and citations. It iterates the known set of documents (rather than searching a pool), so it never silently skips one, and runs under bounded concurrency. Cell types include yes/no, date, currency, number, percentage, tag, list, and free text, and the whole review exports to Excel.

Groundedness

Groundedness checks each factual claim in an output against the sources Fosnie actually holds and flags unsupported claims – it's about faithfulness to your sources, deliberately not a "no hallucinations" promise. It's off by default (features.groundedness) and fail-open: if the verifier isn't running, answers are unaffected.

• Live – after a retrieved answer streams, a background check scores it and shows a groundedness pill; it never delays the first token.
• Verify draft – a button on a generated artefact or document runs a deeper check: decompose into atomic claims, bind each to evidence, mark it supported / contradicted / not-mentioned, and produce a downloadable report with inline highlights (contradicted in red, not-mentioned in amber).

Optional ground-or-cut repair surfaces as tracked-change proposals you accept or reject – it regenerates a flagged span constrained to cite a real source, and cuts anything that can't be. It never auto-applies. Verification only ever reads sources you're allowed to see.