Docs / Document Studio
Documents from the schedule
Ask for the steering-committee deck and get a real .pptx built from a slice of plan you define — on a data path that differs from the rest of the product, deliberately and visibly.
What it produces
A conversation, like the scheduling agent — but a different one, with a different toolset. You tell it what the document is for, define the slice of schedule it may use, and it builds a .pptx, .docx or .pdf and hands you the file. Typical asks: a monthly steering deck, a gate-review pack, a one-page status brief for someone who will never open a Gantt.
It cannot change anything
The Studio has no mutation tools at all. There is no path from a document conversation back into your plan — not a task, not a date, not a comment. It reads a bounded slice and writes a file. If you want the plan changed, that is the scheduling agent, on the other surface, with its own review step.
Scope is yours to set, and it is enforced
You declare the slice — which projects, which parts of the schedule, which window. Only that slice is sent. Out-of-scope tasks are absent, and so is cost data. The model cannot widen its own scope mid-conversation; the boundary is enforced on our side, not requested politely. If the slice you chose turns out to be empty, you are told it is empty rather than handed a plausible-looking document about nothing.
The part you should read before enabling it
Document generation runs on the model provider's document-authoring skills and code-execution sandbox. That path is not zero-retention, unlike the scheduling agent's. Nor can we tokenise names on the way, the way we do everywhere else — a redacted name would land in the finished slide and the document would be worthless.
So the control is consent and scope rather than redaction, and it is layered. Five things must all be true before a build starts: the platform switch is on, your organization's admin has accepted a recorded disclosure of exactly this trade-off, the project has it enabled, your account is granted, and you hold a write role on that project. Revoke any one of them and the next build stops. Bump the disclosure and existing consent goes stale until someone re-accepts it.
Two more things worth knowing: the provider-side copy of the finished file is deleted the moment we have retrieved it, and none of this touches the scheduling agent — its path remains zero-retention and redacted. Full detail on the security page.
Cost
Document builds are metered separately from agent conversations, with their own quota. An over-quota build is refused with a clear message rather than silently truncated, and usage is reported per organization.