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

---
title: Revisions and conflicts
description: Which records keep saved revisions, how a post change affects an approval, and what to do on a conflict.
section: contracts
order: 40
status: implemented
mode: both
reviewed: 2026-10-02
sources: [db/publishing.sql, db/instagram.sql, db/x.sql, db/tiktok.sql, src/lib/server/marketing/service.ts, src/lib/server/marketing/marketing-agent-tools.ts, src/lib/mcp/agent-tools.ts, src/lib/server/mcp/AgentMcp.ts, src/lib/mcp/project-tools.ts, src/lib/server/media/project-agent-tools.ts, src/lib/server/media/MotionDocuments.ts, db/media.sql, src/lib/server/tiktok/TikTokPublication.ts]
tools: [get_post, inspect_post, edit_post, get_workspace, update_workspace, ads_save_plan, ads_get_plan, ads_get_operation, ads_execute_plan, get_project, edit_project, export_project, convert_project, prepare_seedance_reference]
next: [/docs/contracts/connections]
---
A post has one current version. `edit_post` changes it in place and keeps no earlier copy, so a post edit sends no revision ID. Business details have one current version too: `update_workspace` changes only the fields you send, and the last completed save wins.

An approval keeps its own copy of the exact content that the owner approved. If the post changes after approval, the approval no longer matches, and the server refuses to publish. Approval history locks a post against draft edits (`DRAFT_LOCKED`). Create a new draft when that lock applies.

A TikTok video review binds its video checksum, saved asset, account connection and permission version, caption, settings and UTC schedule. An edit before approval makes the earlier review unusable. Prepare it again. An approved post stays locked; use a duplicate for new content or timing.

TikTok Ads plans and approval requests bind an exact saved revision. Send the expected revision with each plan write.

## On conflict

Read the current record. Compare it with the intent and owner decision. Only then create a new write with a new request ID. Do not silently rebase a caption, media attachment, account choice, or spend instruction. A replay of the original request ID returns the saved result and does not recheck later changes.

## Studio projects

A project keeps its format. `edit_project` rejects a change of `format` or `storyMedia` with `INVALID_INPUT`. `convert_project` makes a new project in another format from a saved revision and leaves the source unchanged.

`edit_project` sends the complete composition, not a patch. A stale `expectedRevisionId` returns `MOTION_CHANGED` with `currentRevisionId`, and nothing is saved. Read `get_project`, apply your change to that revision, and send it again. Every save is an immutable revision with the agent or the owner as its author. The newest 100 revisions of a project stay, and so does every revision that a Seedance loop link names. The owner can restore an earlier revision; the restore saves a new revision. A render job keeps a copy of the exact revision it renders, so a later edit does not change a queued render.
