> ## Documentation Index
> Fetch the complete documentation index at: https://docs.protodesk.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Review workflow

> Understand what a proposal changes and what requires human approval.

## Update an existing article

1. Confirm the workspace with `authoring_context`.
2. Find and read the article, including its current revision.
3. Agree on the intended edit with the person requesting it.
4. Submit an update proposal with that revision and a stable idempotency key.
5. Open the returned review link in the Protodesk dashboard.
6. A person reviews and approves or rejects the proposal.

Submission does not modify the article. Approval applies the content change. If the article is published, that approval updates its live content; if it is a draft, it remains unpublished.

## Create new articles

The assistant submits candidates together as an article set. A reviewer checks each candidate's content, collection, locale, slug, tags, and featured state. Approval creates unpublished drafts, which can then follow the team's normal publishing process.

## Resolve conflicts

If the article changed after the assistant read it, do not force the old proposal through. Read the latest revision, compare the intended change, and create a new proposal after review.

## Keep the boundary clear

The assistant can prepare content and submit proposals. The adapter has no approval or publication tool. It also does not clone repositories itself: any repository context used to draft content must already be authorized in the assistant's environment.

Keep customer-facing articles free of credentials, private implementation details, and unverified feature claims. Use a review note to identify anything that still needs confirmation.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.