Asset branching

A launch video may need a founder’s perspective on LinkedIn and a shorter introduction on Instagram. Coconut keeps the original in a Master asset and gives each channel its own branch. You can adapt a post without changing the starting material or another channel’s version.

Structured atoms give edits a specific target

An asset contains typed blocks called atoms, including text, images, and video. Each atom has its own identity, so a person or agent can edit a caption, move a block, or replace media within a specific version of the asset. The publication system maps those atoms to the content required by the destination.

The original and its channel branches

The Master holds the original content. A channel branch holds the version prepared for one destination, along with its publication state. Editing that branch leaves the Master and other branches unchanged. Compare a branch with the Master to see how the version differs.

Changes to the Master do not automatically update existing channel branches. Automatic syncing from the Master is not currently available.

Each destination has its own publishing decision

A LinkedIn post can be ready while an Instagram post still needs attention. Coconut checks the selected account, required content, media compatibility, and publishing permissions for the destination. Approval follows the configured tool policy.

These checks establish whether the post meets the publication requirements. They do not provide an editorial review of its claims, tone, or suitability for your audience.

An edit has an author and a history

When a person or agent changes an asset, its journal records the actor, time, and changes. Inspect the history for the Master or a channel branch to understand how the work reached its current form.

The asset system validates the operations in a command and commits the resulting document as a complete version. Those accepted changes and their history belong to one transaction. This atomic commit prevents a failed asset command from leaving only part of that command applied. Publishing to external channels has separate outcomes for each destination.

Eligible edits support undo and redo. The Master also supports restoring a recorded version. Recovery changes the content in Coconut; it does not retract a post already published to a channel.

Reuse the material across brands

Use media you have access to in separate assets for your personal and company brands. Each brand’s asset has its own channel branches, so the same video can carry a founder’s story in one brand and a product announcement in another.

Why we built it this way

Agent work needs an identifiable target and a record of its effects. Channel branches give edits a specific destination. The journal makes those edits attributable, and supported recovery lets you revise the work without losing its history. You can inspect the changes and make a publishing decision with the relevant version in front of you.