GuideCreate2 min read
Revisions, freezes & preservation
Keep earlier work identifiable while adding a storage copy or making an allowed update.
Select an underlined word to see what it means.
In this guide
- 01Original work
Keep its collection, token, files, and Parts identifiable
- 02Preserve bytes
Add a verified location for the same content
- 03Revise deliberately
New scripts or presentation need a new version
- 04Retain the trail
Follow the original permissions and history
A file and its location are different things.
The MarkA file's computed fingerprint, also called a digest or hash. A reader recomputes it to check the bytes.For exampleChanging the sketch's background color changes its Mark. A filename alone would not reveal that change.Full glossary entry → identifies the exact file bytes. A carrier is the place and method used to recover them. The same file can have a checked copy in more than one location.
Moving unchanged bytes preserves their content identity. Changing the sketch changes the file and its MarkA file's computed fingerprint, also called a digest or hash. A reader recomputes it to check the bytes.For exampleChanging the sketch's background color changes its Mark. A filename alone would not reveal that change.Full glossary entry →.
Make an update a visible event.
An update should continue the work’s history. For an existing published graph, the shared planner can prepare a graph revision and reuse unchanged selected-chain objects. Only the changed pieces need new storage.
Each work either stays on one exact version of a shared Part (pinned) or moves to newer approved versions (follow latest). Updating a shared Part never changes pinned works.
Preserve more without losing the original.
A larger work might use a practical external carrier today and gain a native onchain copy later. Retain the original token reference, files, and dependencies so people can inspect that relationship.
A new location still needs successful retrieval and matching MarkA file's computed fingerprint, also called a digest or hash. A reader recomputes it to check the bytes.For exampleChanging the sketch's background color changes its Mark. A filename alone would not reveal that change.Full glossary entry →. Recording a hash alone does not put the file there.
A freeze applies to a specific thing.
An artifact freeze, a shell freeze, and a closed sale affect different records. Read exactly what becomes fixed. A closed sale may still have already-reserved allocations to fulfill.
A ShellThe opening program and interface around creator content. The canonical KEEL verification shell owns the protected checks and K controls.For exampleOpen the K control to inspect the files and checks behind the displayed work.Full glossary entry → cannot bypass an immutable contract’s rules. If the original token cannot be updated, a separate preservation record or wrapper must explain its relationship to the original.
Technical detail: stored bytes, revisions, and freezes
HoldKEEL's native onchain storage for the file bytes and the instructions for joining them back together.For exampleYour sketch and its shared drawing library are stored as separate objects in the Hold.Full glossary entry → content objects are immutable. Artifact and harness registries can support append-only revisions under their policies. Freezing a registry binding seals the specified selection. Creator shell revisions and per-token harness composition are distinct records. Verify the exact implementation and state; do not infer a complete frozen graph from a UI label.