The site lifecycle

A Studio MCP edit starts with a private draft. Publication is a separate operation with separate permission. Keep that distinction in your task instructions.

1. Read before editing

Ask the client to read the current site context, the relevant authoring rules and a brief for the task. Context is bounded: an omitted file or rule must be requested explicitly if the edit depends on it.

For example:

Add an FAQ page using the existing design. Read the relevant rules and navigation first. Prepare the change and show me the complete diff. Do not apply or publish it yet.

2. Review the proposed result

Preparing a change retains a review without applying it to the draft or live website. Review all returned before-and-after content, including compiled CSS, navigation, page metadata and dependent files. Follow continuation ranges until the diff is complete.

The review identifies the source version and its exact contents. If another edit makes it stale, prepare a new review. A client must not silently substitute different source under an old approval.

3. Apply and finish the operation

Applying the reviewed change writes to the private draft. Larger operations may stop at a checkpoint and require an explicit continuation. Status reads report progress; they do not finish the work themselves.

Keep the same operation identity when retrying the same request. A lost response does not prove nothing changed. Inspect the retained result before retrying, and do not invent a new identity to get around an unfinished operation.

4. Preview

Inspect the draft in Studio. The MCP preview can return rendered content or a short-lived browser preview, but rendered HTML is not a visual acceptance test. Check the actual page, navigation and relevant screen sizes before publication. Treat a browser preview link as a secret.

Draft PHP may execute during rendering. Grant editing access only where that server-level trust is appropriate.

5. Publish separately

Ask for a publication review, inspect the live changes and then approve publication if intended. Edit drafts cannot publish; Edit and publish can. Publication checks for stale reviews and unexpected changes to managed live files.

Restore or recover

Snapshot restoration can target the draft, the published website or both, according to access. Restoring the draft does not publish it. Live restoration requires its separate owner-account grant. Website snapshots do not roll back every business record, account or credential.

If an operation reports recovery is required, use its retained recovery controls. Do not delete its files, receipts or safety snapshots to clear the message. See Troubleshooting.