Versioning & Publishing

Every content-bearing resource (Context, Instruction, Skill, Prompt Template, Checklist) has two related but separate ideas: status and version history.

Draft vs. Published

A resource is either a draft (still being worked on, not visible to any AI tool) or published (approved and eligible to be served). Toggling this status doesn't touch the content itself.

Version history — a "Main" pointer, not a linear stack

Every time you save an edit to a resource's content, a new version snapshot is created — but that edit does not automatically become "live." Nothing about the resource's current content changes just because you saved a draft edit.

Instead, each resource has one version flagged as Main — think of it like moving a git branch pointer rather than always reverting to the latest commit. To make an edit live:

1. Open the resource's version history.
2. Pick the version you want from the dropdown and preview it.
3. Click Set as main version.

Only then does that version's content become what the resource actually serves — both in the app and to any connected AI tool.

Deleting old versions

You can delete old versions you no longer need, with two guardrails: you can never delete the current Main version (set a different one as Main first), and a resource must always keep at least one version.

Why it works this way

This separates "I'm iterating on a draft" from "this is now the official version," so a half-finished edit can never accidentally become what your team or an AI tool relies on.