Edit and subscribe to well updates

Bounded Workspace pilot · 24 September 2026. Save a SQL-well edit, retain its original input, then offer the result to colleagues. A recipient can subscribe once and choose when updates reach their private Workspace working copy.

Before you start

A deployment administrator must configure a supported SQLite/PostgreSQL connection with explicit retention, redistribution and recipient policy. The author needs project administration and their own source access. The recipient needs project membership and permission to read the retained snapshot; no borrowed SQL credentials are used.

Create and offer a result

1. In Data → Catalogue → Wells, edit a well, create a draft and save changes.
2. In Snapshots & releases → Capture snapshot, select the saved edit, identified by its short draft ID and generation. Its exact original input is included automatically.
3. Supply a name, intended use and permitted recipients. Review is optional. If requested, approval must happen before the snapshot can be offered.
4. In Data → Updates → New update stream, choose the snapshot and a meaningful name.
5. To publish a later version to that stream, save/capture another edit of the same source. Choose Offer another snapshot, review audience exclusions and confirm.

A stream contains explicit frozen versions. Choosing “Collection package” does not share live personal collection membership. Original inputs and other selected package assets remain inspectable in Snapshots & releases. Each consumer version supports one edited SQL-well result, with at most 200 wells. Larger results remain exportable.

Receive and work with updates

Open a stream and Subscribe to updates. The default is Review before applying. Inspect the incoming table, then apply it. Pin keeps your current version until you explicitly apply another. Follow checks every 15 seconds while the inspector is open and the browser tab is visible; it applies only to a clean working copy.

The status rows have different meanings:

Status	Meaning
Available	The publisher offered this snapshot version.
Approved	Someone approved that exact snapshot for its stated purpose.
Delivered	The browser acknowledged receiving a verified preview.
Applied	Your durable Workspace working-copy version advanced.

Applying does not write upstream or prove that another application used the data. Select Approved releases only when unreviewed snapshots are unsuitable for your work. Requesting review pauses a snapshot until approval; withdrawal blocks future delivery.

Edit values in My working copy and save them privately. Both unsaved and saved edits block automatic replacement. Discard working edits explicitly removes them before an update can be applied. These private edits cannot yet be published onward.

Scientific meaning and recovery

Zero is a value; NULL is missing; empty text is a separate SQL value. Text inputs can be empty; use Set missing for NULL. Blank numeric input means missing. No gap is filled with zero and no interpolation or CRS/unit conversion happens. IDs, units, CRS and depth context stay protected. Original SQL scalar encodings and unmapped columns remain in the retained input; the derived result declares its projection losses.

Saved edits and applied versions survive gateway restart. Unsaved edits survive a session-expiry/sign-in cycle in the same loaded tab and account, but not a browser reload after ignoring the warning. Save before leaving. A conflicting edit from another tab requires reload/review or explicit discard, never silent rebasing.

If access is revoked, retained content is hidden. Restore permission or explicitly discard and unsubscribe. Previously exported copies cannot be recalled. If a source changes before capture, start a draft from its new verified revision. Retrying the same snapshot offer never creates a duplicate version.

Tested example and limits

Qualification used two synthetic wells with distinct IDs but the same name. The first had depth 0 and a NULL operator; the second had NULL depth and empty operator text. The author changed the first depth to 12.25, then 20 and 30. A second browser account without a source principal tested review, pin, follow, dirty protection, session recovery and approval. Server tests additionally cover non-admin recipients, revocation, corruption, concurrent offers, stale generations, rollback and backup/restart.

No offline push, generic SQL console, external application delivery or OSDU writeback is claimed. See the API contract and current availability.