Reusing what already exists instead of starting from zero changes the starting point of a new presentation. That is what generation is being built for: the new document comes out of the body of knowledge your company has already produced, and every passage points to where it came from.
From your knowledge, not from nothing
The new comes from what already exists in your vault, and the page states where the capability stands
Ask for a deck, a section, a summary. The design is for SazAI Corpus to compose from your own body of knowledge, the presentations, analyses and translations that already live in your vault, and not from a generic model’s idea of your business. The content is yours, distilled: your numbers, your terminology, your voice, assembled into something new, every passage with its provenance.
This is the least mature operation in the set, and the page says so before you find out. That is why it carries no number and no verb of its own in the present tense for the capability: translate and compare sell as ready, create sells as maturing. Whatever ships appears in the platform roadmap on the day it appears, and not before.
The state, said in full and before you ask. Measured on 2026-09-02, in the development environment and not in production, which is the only boundary this sentence can claim: the write-run log is empty across all four formats, and the write step does not appear in the history of steps executed. The engine exists, the log is empty, and the two together are the state.
Co-creation with AI
The material is yours, the decision is yours, and what the machine brings is the assembly
The word co-creation names a division of labor, not a decoration. You bring the material and the judgment; the assembly arrives with the origin of every passage attached, and what is not in your body of knowledge does not appear.
Where the new document is assembled from, why the blank space where an answer would fit is honest information, and why the signature stays with whoever reviewed it, are in co-creation with AI.
Web editor
Fixing the slide on the screen where you read it, and the gap that still separates that
The screen that shows your slide and the engine that writes your file already exist, and connecting them is not a matter of wiring: what passes between the two today is a rendering of the page, and a rendering does not hold the identity of the elements the engine needs to write back in the right place.
Why element identity is what makes a change addressable, and exactly where the missing piece is, are in web editor.
Agentic editor
Asking for the change in words, without the model touching the file
The obvious way to edit by conversation is to let the model touch your document, and that is exactly the one this house refused. Your request, in your own words, becomes a specification, and a request the engine cannot resolve to a concrete element in your material fails instead of being guessed.
How the request becomes a specification, why editing inherits the refusal that translation already proves, and what asymmetry remains today between reading and changing, are in agentic editor.
What you have already produced keeps being what you see, ask and translate. And all of it, done or still to do, is recorded: it is the fifth, trust.