Review a shared document with an agent

In Processes, choose Create process → Agent document review. Enter guidance such as "Improve clarity without changing the facts.", then apply the draft in Code. Review and save the source, bind an editor AI profile, and select Start. The reviewer is the authenticated person who starts the process (HUMAN("owner")). Creating or saving the source does not run the editor or change the document.

Before Start, the host administrator must install a document resource named story with read and revise permissions for your identity and workbook. The document grant configuration describes this setup. Source cannot grant access. An installed profile also needs its normal model/provider configuration.

The starter uses READ(room.story) to get the base and REVISE(room.story, base, review.content) to attempt the edit. These are core process operations; no operation-package import is required. An existing workspace.READ / workspace.REVISE import uses the same contracts.

The process reads the current story, passes that exact content and your guidance to the editor, and requires a structured response containing the complete revised text. It privately shows the original and proposed text to you and waits for your explicit typed approval. Approval attempts to save against the revision that was read; it never overwrites a newer revision silently:

• If you decline, the proposed text is returned with status: "declined"; no revision is attempted. Its reference identifies the unchanged base.
• If you approve and the story is unchanged, the revision is saved and its content is returned.
• If another editor changed it, the newer story stays in place and the proposed text is retained for review and returned in the result.
• If the editor's response does not satisfy the declared response shape, no revision is attempted.
• If a write's outcome cannot be established, the process stops with an unknown outcome. It does not retry the edit automatically.

The result contains status, content, reference and message. For saved, the reference identifies the saved revision; for conflict, it identifies the retained proposal, which has not been applied to the story. Use Copy result to copy the complete result, including long content hidden by paging. Inspection and copying grant no permission to apply the proposal.

Inspect the conversation and operation records using the existing Process controls. This workflow makes one model call, waits for one human decision, and has no retry loop. Cancelling while awaiting your answer prevents the proposed revision. A correct response shape does not establish editorial accuracy; review the content. Restoration requires the selected native recovery store and matching document grants. The approval-and-revision sequence — approval across a host restart with an explicit Resume, decline and cancellation without a revision, and a stale approval returning a conflict — is recorded in the initial release product evidence. That is local evidence with a scripted provider, not packaged-candidate qualification.

Start also checks space for the workflow's bounded document results, including conflicts. Longer workflows reserve more space; a workflow that cannot fit is refused before any model call or edit. This can be conservative for branches and small documents. Reduce the operation bound or split the workflow if it exceeds the installed ceiling. It does not make several edits one atomic transaction.

The complete source and generated starter include the explicit human approval step. Focused native tests exercise approval and decline with a scripted editor and in-memory journals; the product walkthrough is in the initial release evidence. An earlier automatic-revision product walkthrough using the explicit package spelling covers authoring, Save, Start, inspection, competing edits, invalid responses and cancellation through real disk journals with a scripted provider. See the retained product evidence. The shorter core spelling has also been exercised through Create process, Save, Start and inspection: a saved edit, a competing edit, a retained conflict and a subsequent read confirming the current revision. See the core-language product evidence. These walkthroughs do not establish model quality or document restoration.

You can use Create process again in a workbook that already contains these workflows. It chooses unused process, team, room and operation-import names; review and Save each draft before Start. This includes multiple document-review starters in one workbook. Other source constructs whose names cannot be fully inspected may still require adding the process in Code. See the repeated-creation product evidence.