Notebooks And Sharing

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

That same notebook analysis scope can now flow forward into the SQL editor.

So a saved notebook is not only a visual review artifact. It is also the carrier for the current lot, selection, and what-if context when you want to continue with scoped SQL work.

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

Use personal spaces for private work and shared spaces for team workflows.

Shared spaces have explicit access management and separate notebook 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

Saved notebooks can now move through document lifecycle states:

active
archived
controlled

Think of them as:

active: working analysis
archived: put away, not for active collaboration
controlled: frozen official artifact

Recommendation

Use controlled when a notebook becomes a decision artifact that should be shared but not edited in place.