Notebooks And Sharing
Notebook state
Section titled “Notebook state”A notebook captures more than text notes. In alpha it can persist:
- lot and snapshot context
- active test focus
- selection state
- scenario limits
- spatial analysis pushes
- chart and modal-driven what-if conclusions
Versions
Section titled “Versions”Notebook saves now track base_version.
That means version history can tell the difference between:
- a normal save from the previous head
- a valid save that was made from stale notebook state
This does not block saves. It makes lineage visible.
Spaces
Section titled “Spaces”Use personal spaces for private work and shared spaces for team workflows.
Shared spaces have explicit access management and separate notebook share links.
Share links
Section titled “Share links”Notebook share links are read-only.
That is true even if the underlying notebook is mutable for the owner.
Current behavior also caps active share links per notebook to keep the surface controlled.
Lifecycle states
Section titled “Lifecycle states”Saved notebooks can now move through document lifecycle states:
activearchivedcontrolled
Think of them as:
active: working analysisarchived: put away, not for active collaborationcontrolled: frozen official artifact
Recommendation
Section titled “Recommendation”Use controlled when a notebook becomes a decision artifact that should be shared but not edited in place.