Change history and release identity
Source and Versions
This section explains how editable source, immutable release cuts, live Drop updates, and publish state work together so teams can evolve an app without fragmenting discoverability.
Canonical guidance for source lineage, cuts, and publish history.
Implementation focus
Use this model whenever you need rollback confidence, reproducible outputs, or clear version ownership.
Expected outcomes
- Track source and publish changes without losing canonical app continuity.
- Understand cut behavior for rollback, pinned embeds, and live Drop movement.
- Preserve reproducibility when shipping frequent updates.
Source, releases, and lineage
Editable source lives in the capsule. Published releases become immutable artifacts. The public post and live Drop connect those releases to the social and discovery surface.
This separation lets a creator keep iterating without erasing what viewers already opened, embedded, remixed, or referenced.
- Capsules hold editable project source.
- Artifacts hold runnable release output.
- Drops select which artifact is live for the canonical app.
- Remixes and version history depend on preserving lineage instead of overwriting history.
Reproducibility expectations
A published artifact should be reproducible enough for the platform to serve it consistently and for users to understand what changed between cuts. Build output, dependency resolution, and runtime entry selection are part of that contract.
Do not treat generated runtime output as the same thing as editable authored source. They are related, but they serve different trust and delivery roles.
- Keep source edits in the source plane.
- Keep runtime bundles and manifests in the artifact plane.
- Use release history when explaining why a public app changed.
Example and read next
Example: a teammate asks why the live app changed while an old tutorial embed still behaves the same. Explain that the Drop points at the current artifact while exact-cut references keep their recorded release output.
Use these related pages when you need the next layer of guidance. They point to the most likely follow-up tasks, not every page that happens to touch the same system.
- Read next: BUMP IT (/docs/bump-it)
- Read next: Studio (/docs/studio)
- Read next: Runtime Presentation (/docs/runtime-presentation)
- Read next: Embeds (/docs/embeds)