The Problem
Reports, policies, proposals, and long notes often need to be reduced into a useful decision brief. The risky part is not shortening the text; it is preserving what the source actually says, separating action proposals from facts, and making ambiguity visible to the reviewer.
A trustworthy document workflow should let a person inspect the source used for a run and know exactly which draft was approved.
What You Can Use Today
The current Document Brief workflow accepts text that you paste into the Workbench. It does not open a PDF or Word file, scan an image, watch a folder, edit the original, or publish a result.
1. Set the briefing objective
Name the document, describe what the brief should help a reader decide, paste the source text, and add optional context. You can also opt into selected knowledge notes from the chosen Ant.
2. Build the structured draft
Use the manual editor or explicitly confirm optional AI drafting. The brief separates the summary, key points, action items, uncertainties, and evidence notes so a reviewer can correct each part.
3. Inspect and approve the exact version
Every run freezes its document text, context, selected knowledge, Ant settings, and execution details. Approval stores an immutable revision. Copying or marking it handled records a local handoff only; it does not change a file or complete an action elsewhere.
What Remains on the Roadmap
Future connected document work could add permissioned file import, format parsing, OCR, document-library access, and approved exports. Those capabilities need file-type validation, malware controls, access scopes, retention rules, and clear write permissions before they can be offered responsibly.