Versions
Entities, briefs and skills all carry two states: a draft you edit, and an active version agents are served from. They work like Flow versions — edit the draft, then activate to publish a numbered, immutable version.
Draft and active
| State | Who reads it | How it changes |
|---|---|---|
| Draft | You, in the builder and Preview | Every Save |
| Active version | Every agent, tool and API call assembles from it | Only Activate |
Nothing you save reaches an agent until you activate. The bar under the builder header says where you stand: Unsaved Changes while edits are local, Edited Draft once saved but not published, nothing at all when the two agree.
An artifact that has never been activated is delivered to nobody. An inactive entity is refused at the agent boundary; an inactive brief or skill is skipped. Studio previews and edits the draft either way. Seeded entities and skills arrive active at v1; copies and new artifacts start inactive.
Activate
Click Activate in the header.
- Unsaved edits are saved first — activation publishes the saved draft.
- The dialog lists what differs from the active version.
- Write the required comment, saying why this version exists.
Versions are numbered per artifact, never reused or renumbered.
Roll back
Versions in the header lists the history — number, comment, who activated it and when — with the active row badged.
| Action | What it does |
|---|---|
| Activate this version | Agents receive it immediately. The pointer moves; no new version is created |
| Load into draft | Copies the version into the draft without activating |
| View payload | The stored configuration |
Rolling back also offers to load that version into the draft, checked by default.
WARNING
Uncheck it and the draft keeps the configuration that prompted the rollback, which the next Activate republishes.
Deactivate
Deactivate, at the bottom left of the Versions dialog, clears the active pointer. Nothing is deleted: every version stays, and Activate publishes again from the draft or from any version listed. Agents stop receiving the artifact immediately, which makes this a real emergency stop.
What a version covers
A version freezes the artifact’s own configuration — for an entity, its fields at every level, field properties, instructions, related lists, references, and which elements it uses.
It does not freeze the elements themselves: edit a shared metric and every entity using it changes at once. Domain membership is not versioned either, so those changes are live immediately.
Write access is deliberately not versioned. The writable fields and the Allow Writes switch live on the entity record, so narrowing takes effect immediately and a rollback can never re-grant permission to write.
Notes
| Action | Effect on versions |
|---|---|
| Save | Edits the draft. Agents unaffected |
| Copy | Copies the source’s draft. The copy starts inactive with no history, stamped with its origin |
| Delete | Deletes its versions with it |
| Preview (builder) | The draft, including unsaved edits |
| Preview (catalog) | The active version — what agents get right now |
Every load is stamped with the version that served it, so usage carries version as a dimension and the charts mark each activation. Every activation comment lands in the Change Log.
What’s next
- Domains — who receives what
- Your first entity — the model in practice