Change Log
One consolidated history across the three artifact libraries — entities, briefs, and skills — plus domains. Under History → Change Log on the Studio rail.
How it works
Every event is one row: when, which artifact, its library, what happened, the version, the comment, and who did it. Six events exist:
| Event | Meaning |
|---|---|
| Created | The artifact came into existence |
| Activated | A version was published — this is what changed what agents receive |
| Rolled back | The active pointer moved back to an earlier version |
| Deactivated | Withdrawn from service — the pointer cleared, versions kept |
| Updated | A domain changed. Domains aren’t versioned, so they never activate |
| Deleted | The artifact is gone — this row is the history that survives it |
The comment column is the point of the page. Activation requires a comment, so the log reads as a running account of why the configuration is the way it is, written by the people who changed it as they changed it.
An artifact drafted by the admin agent and activated by a person reads here like any other activation, under that person’s comment.
Filter by library, and search across artifact, comment, and author. Click an artifact to open it: an entity opens in its builder, a brief or skill on its page, a domain on the Domains page.
Domain events
A domain has no activation, so its comment column records what the save changed instead:
| Change | Reads as |
|---|---|
| Name, description, color, icon, or meaning | Changed: name, color |
| What the domain carries | Entities added: opportunity_360 · Entities removed: case_360 |
| Briefs or skills added to it | Briefs: pricing_policy, brand_voice |
| Write access through the domain | Writes through this domain enabled |
| Unattended writes | Unattended writes (no confirmation) ENABLED |
| Customer-facing flag | Customer-facing on |
| Who may read it | Access: granted to Dana Ruiz, 1 manual share revoked |
| Who may manage it | Managers: granted to Sam Okafor |
Access lines say granted and revoked, never who has access in total. The Domains page manages manual shares only, and an owner, a sharing rule, or the role hierarchy can grant access it never sees.
Saving a domain without changing anything writes no row.
Who sees what
Admins see everything. Domain managers see the artifacts homed in their domains — the same scope that governs what they can manage. A domain’s own events count as homed in it, so a manager sees the history of the domains they manage and no others.
Notes
The log is its own ledger. Each event writes one row at the moment it happens, and nothing rebuilds the history from version rows later. Deleting an artifact takes its versions with it, and a history rebuilt from those versions would go too. The ledger row stays, label and all.
Draft saves don’t appear: a draft changes nothing an agent receives. The log records only the events that did.
What’s next
- Versions — the contract the log is built from