Product · Claim drafting
Sentence by sentence, every factual statement cites its evidence. A separate verifier - a different examiner from the drafter - checks each citation against the source before your team sees it.
The drafter cannot emit a factual sentence without evidence attached - the schema rejects it. Chronology renders from your confirmed events; analysis prose is drafted in a claims register and flagged where judgment is required.
On 2 February 2006, the Architect instructed the Contractor to place the order for the Light Wall.1 The tender report had identified a 23-week lead time.2
Contradicted or uncited sentences block export - in code, not in a prompt. Weak support goes to your QA queue, where a named reviewer can stand behind a sentence; the audit log records who. Contradictions can never be approved away.
“The instruction was issued in good time.” contradicted
The gate is enforced in code. It cannot be talked out of refusing.
Export produces a .docx with real Word footnotes, each resolving to a document and page in the record. The claim reads like your best work, because your team reviewed every flagged line of it.
Real Word footnotes, every one resolving to a document and page in the record.
See it on your own matter. Pilots run on a real record, with your reviewers in command.
Request a pilot