Ownership and exact versions

Every artifact has an owner and a stable identity. Saving creates revisions; publishing exposes an exact immutable revision. A private edit after publication does not change the public source or public metadata.

Dependencies pin exact published revisions. A new version of a dependency never silently changes your project. A fork gets a new private identity and retains attribution to the source revision.

Simulation-owned elements

Publishing a simulation exposes its local models, properties, presets, behaviors and visuals as reusable parts. Their detail view links to Open source simulation. Edit their definition there, then save/publish the appropriate revision; editing an extracted part directly would create competing definitions.

An author has one artifact identity per kind and source name. Publishing another Thermal property under the same author, even from another simulation, creates a new revision of that property. Already published @author/Thermal#2 imports stay on revision 2. A property and a model may share a name because their kinds differ. See source imports for exact-version syntax.

Standalone parts retain their own author and revisions. A community preset can target someone else’s published property without modifying it. Compatibility is with the exact property revision, not just a matching name.

Recorded media

Published simulation previews are immutable. Studio’s timeline can be downloaded as a local .hylebake and reopened read-only. To edit a recorded state, fork the visible frame into a private project; the original file remains unchanged. Studio does not currently expose a bake-upload feed or take-management panel.

A visual preview stores appearance for playback, while a bake stores simulation state for inspection and forking. Neither is an independently certified physics result.

See saving and publishing and bakes.