Generating a document with AI is easy to demonstrate and hard to sign, and the whole difference sits in knowing where the text came from. Here the design is different: the new document is assembled from the body of knowledge your company has already produced, every passage points to its own origin, and the final decision stays with whoever knows the material.
From your material, not from nothing
What already lives in your vault is the raw material, not an example the model consulted
Ask for a deck, a section, a summary. The design is for the assembly to start from what is already in your vault, the presentations, analyses and translations your company has produced, and not from a generic model’s idea of your business. The content is yours, distilled: your numbers, your terminology, your voice.
The word co-creation is not decoration, and it names a division of labor. You bring the material and the judgment. The machine brings the assembly and the provenance, which is the address of where each passage came from. Remove either half and the product changes: without your material, it is generic generation; without the origin of each passage, it is plausible text you have no way to check before you put your name on it.
What your vault keeps for each document, and why it can be raw material instead of a folder of files, is in your documents.
What is not there does not appear
The blank space where an answer would fit is honest information too
What is not in your body of knowledge does not go in: no invented number, no confident fiction. The blank space where an answer should be is information, and it is what makes every passage auditable before you take ownership of the document. You see where each statement came from, or you see that it came from nowhere and was left out for that reason.
This is the same property that makes the agent refuse a question whose answer is not in your material, and it is not a behavior instruction asked of the model. The assembly starts from what the engine recorded, and the record either holds the information or it does not. Why the arrangement works this way, and not as a promise of good behavior, is in the conversation is with the AI.
Whoever signs is whoever decided
Review is the design, not a caveat pasted at the bottom of the page
The assembly starts from a model that already exists and fills the editable fields with what you supplied or with what was written from what you asked for. Whoever knows the material reviews it before the document goes out to a client.
It is worth being direct about why this is not a caveat. A caveat is what gets added when the guarantee falls short; here the person in the loop is the guarantee. The document carries the signature of whoever reviewed it, not the model’s, and that is why the page does not promise a finished document: it promises a draft whose origin you can check passage by passage. Material that arrives finished and without origin costs more to check than to redo, and that is the arithmetic most demonstrations do not show.
Where this stands today
Direction declared, measured, and with no verb in the present tense
This is the least mature operation in the set, and the page says so before you find out. The step that writes a new document exists in the engine and is the only creative step in the design, but no execution of it is recorded in this environment’s history. That is why the page carries no performance number and no verb of its own in the present tense for the capability.
The house rule is the same one that governs the roadmap: translate and compare sell as ready, create sells as maturing. The day there is a measured execution, it enters here with the date, and not before. The two surfaces through which co-creation should reach you, when it does, are the screen in web editor and the conversation in agentic editor.
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-execution log is empty across all four formats, and the write step does not appear in the history of steps executed in this environment. The engine exists, the log is empty, and the two together are the state.
And why the page carries no number. Publishing a measurement here that does not exist would contradict the one argument that holds up every other page, which is that our measurements reproduce. A capability enters this house when it has a written decision, a measurement, and someone outside able to repeat the measurement. This one has the first of the three.
What co-creation assembles returns to being material in your vault, and everything done or still to do stays on record: it is the fifth, trust.