The compliance matrix should not be a weekend of copy-paste.

What breaks on a live capture

Volume wins and past performance write-ups scatter across drives. A new RFP arrives, and the team rebuilds answers that already existed — with numbers that drifted between revisions.

Colour-team review finds the unsupported claims late. Cross-reference matrices go stale the hour after they are finished.

The matrix as a deliverable

Requirements become response sections. The compliance matrix exports as a spreadsheet you can hand to capture leadership — not a screenshot of a board.

An automated red-team pass

After drafting, every claim carries a verdict:supported,partially supported,unsupported, orcontradicted. Review starts from the fourteen sentences nothing in past performance carries — not from a green confidence bar.

Ask the corpus before you draft

Grounded chat is scoped to the collections you choose. Answers cite passages you can open inline — useful for researching past performance before the matrix is built, and for checking claims after.

Administrative language stays human

Page limits, certifications, and boilerplate that nothing in the corpus answers are left as placeholders on purpose. Generating them would invent compliance language. A human fills those in.

Limits

Tokamak indexes digital documents you upload. It does not OCR scans. Entailment checking is model-assisted and imperfect; the hard gates are the numeric check and the export block on contradicted claims.