Review and share an exact package

Stage 1 pilot, reviewed 24 September 2026. Available on a provisioned Workspace with supported file or mapped SQL connections. OSDU retained sharing, upstream publication and subscriber application delivery are not qualified by this feature.

Prepare access

A deployment administrator must explicitly permit retention and redistribution on the source connection and name permitted account IDs. Reading a source is not a sharing grant. The package audience must fit every selected source’s policy, and each recipient still needs current project access. Capture and approval both require project administration in this pilot.

Create and review

1. Open Data → Releases → Create package.
2. Enter a name and intended use. Choose exact project source selections.
3. Choose permitted recipients, including yourself. Optionally select a previous package for comparison. Click Capture for review.
4. The package shows Needs approval. Findings explains remaining uncertainty. Data shows retained rows, curve previews, source authority and schema/mapping versions. Changes compares another package you are permitted to read.
5. Another authorized administrator opens the same package, acknowledges its findings and approves it for its stated use. Self-approval is allowed but explicitly labelled; mandatory separation of duties is not implemented.
6. Authorized recipients choose Download release for its original data, immutable manifest and approval receipt.

Approval does not resolve an unknown datum, certify scientific accuracy or prove that another application applied the data. Source authority remains unchanged. Changing the original source does not alter a captured package.

Missing data stays missing

LAS originals preserve their declared NULL marker, such as -999.25. The preview represents that sample as missing and breaks the plot line there. Actual zero remains zero. There is no implicit interpolation, filling or unit/CRS conversion.

SQL preserves original selected rows and the mapped scientific view. The table labels NULL and Empty text distinctly; identical well names do not merge separate IDs. GeoTIFF exports retain original NoData, coordinates and declared units. Raster comparison is byte/context-only, not an interpreted difference map.

Previews show up to 200 rows; exports retain the full bounded payload. Comparison shows up to 1,000 mapped cell differences with a total count. LAS aligns row positions, SQL aligns mapped IDs. It does not infer geological correspondence.

Independent download and withdrawal

The ZIP contains manifest.json, receipt.json and assets/00.las, .tif or .json entries according to profile. Standard Python can verify the manifest and every payload hash using Integration’s tools/verify_release_bundle.py:

python3 verify_release_bundle.py release-PACKAGE-ID.zip

No service, sign-in or Ophiolite SDK is needed to verify that download. Use ordinary LAS/GeoTIFF/JSON tools to read the files. SQL JSON is a selected table snapshot, not a database backup. Hash verification is consistency evidence, not a digital signature or a current access/revocation check.

Withdraw package records a reason and stops future downloads. Authorized readers can still inspect its metadata. Already exported copies cannot be recalled. Withdrawal and access revocation are different from deleting retained data.

Recovery and supported scope

• No eligible sources: select a source in Connections and have the deployment administrator check explicit retention/sharing policy and your source access.
• Old source revision unavailable: review/reselect it before capture. A hash alone cannot recover replaced history. Already captured bytes are retained.
• Access denied: check current project grants and connection distribution policy. A release never borrows its creator’s upstream credentials for a recipient.
• Approval conflict: reopen and review the exact package/purpose/findings again.
• Capacity: 10 assets, 64 MiB/package, 512 MiB retained per gateway, 100 packages per project. SQL remains limited to 1,000 rows/4 MiB; files to 16 MiB, GeoTIFF to one band/1M cells. LAS 2.0 UTF-8 is supported, including qualified wrapped rows. Larger workflows and purge are outside this pilot.

Two separate browser sessions qualified capture, review, approval, retained data, comparison, download and withdrawal with synthetic LAS/SQLite fixtures. Service tests include source replacement, corruption, revocation, retry and backup/restore. This does not establish production scale, public hosting or OSDU publication.

See the release API and storage contract.

Optional snapshots and collections

Collections and snapshots add personal working sets and explicitly unreviewed exports. The approval requirement above still applies when you select Require review before download. Review remains separate from destination delivery.