Change history and release identity
Source and Versions
This section explains how capsule lineage, immutable artifact 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.