Current availability

Status reviewed 26 September 2026.

Workspace separates plain data/source/update words from exact IDs and JSON in Technical details. Bounded qualification includes gateway tests, browser checks and a live frozen Python reader. These guides describe pilot behavior, not general availability or production support. See the display contract.

Area	Evidence	Limit
Independent Python curve application	Workspace LAS binding, exact original/normalized reads, local Python interval correction, portable LAS receipt, synthetic and NLOG readback	Browser-authorized local execution; live-source admin route and explicit retained-input member route; no hosted execution, OSDU writer or native-host qualification
Connection administration	Browser setup, real PostgreSQL password rotation, disable/re-enable and recovery	Operator-approved read-only PostgreSQL well headers; no generic network/file picker or SQL curves
Retained Python results	Own-identity member publication, explicit recipient sharing, preview, portable download; synthetic and 32,401-sample NLOG readback	Deployment distribution audience remains required; unreviewed derived LAS, not native-host synchronization
Team sharing and review (E7)	Contributor upload without administration or compute, conditional sharing that a delayed retry cannot undo, owner-changed audience with descendant revocation, private inbox, one review-stage vocabulary with separate endorsements and withdrawal enforcement; gateway, SDK and mounted browser checks plus a live native-service rig with the actual Workspace	Pilot; LAS originals only; no custom stages, email or release-audience changes; exported copies cannot be recalled
Result versions, groups and comparison (E8)	Author-only new versions with expected parent (409), exact old revisions, per-version history; project result groups filtered by access (no hidden counts), one recommended version per group with reason and history, comparisons of settings, input and directional sample changes; gateway, SDK gateway, mounted browser and live native-service checks	Pilot; managed LAS results only; groups and recommendations are not yet in portable bundles; no automatic recalculation
Retained payload store (E9)	Content-addressed store beside the journal or on an S3-compatible bucket (qualified with MinIO: identical exact reads, backup to files and resumable restore into an empty bucket, portable export through the live gateway); verified reads, offline migration/rollback/sweep; configured upload limit and waiting read admission (16×32 reads without refusals by default); single byte ranges on exact reads	Pilot; MinIO only (Hetzner/AWS by configuration, not yet qualified); representations up to 32 MiB; no Parquet columns or multipart uploads
Pilot operations (E10 checkpoint)	Operator tool installs on a clean Ubuntu 24.04 container with pinned components, signs in with operator-created identities, upgrades from the previous pinned release keeping every exact revision, grant, revocation, withdrawal and history, backs up (database + journal + payload store with a manifest), refuses a tampered archive, restores onto a fresh database and verifies, then exports a bundle and calculates offline with the server stopped; hosted CI job and local run	Pilot; no container images/compose, systemd activation, Keycloak/browser sign-in in CI, ARM64, managed mode or server-to-server migration; downgrade unsupported; private components (E17 gates)
Connections and updates (E12 checkpoint)	Validated capability document per connector route (data, direction, change detection, earlier versions, losses, checked status) rendered on Workspace cards and the capability reference; locked PostgreSQL well headers: gateway worker finds a changed row, the lock stays, explicit update to the exact new version, stale choice refused, old version truthfully unavailable upstream while shared copies stay exact; unit, mounted browser and live native-service checks	Pilot; PostgreSQL by regular checks (no change data capture); QGIS host journey and plugin packaging on the Mac not re-qualified; horizon grids in QGIS not verified; no inbox signal for source updates yet
Well tops, trajectories, horizon grids, triangulated surfaces and point sets (E11)	CSV tops and deviation surveys and ESRI ASCII horizon grids upload with declared context and an explicit well-log link; exact reads in Workspace (tables, tops on associated log tracks, labelled minimum-curvature calculation, grid map) and SDK; bundle 2.0 offline; unit, gateway, mounted browser, mutation and live native-service checks	Pilot; one representation per type; no shapefiles or OpendTect files, CRS transformation, attribute units, TVD tracks or calculations on these types; synthetic fixtures only (NLOG rights not established)
Fault sticks and seismic volumes (E16)	OpendTect fault-stick text and SEG-Y (revision 1/2, IBM or IEEE samples, fixed traces, full grid) upload with every header decision recorded; volumes stored as the exact original plus verified per-inline chunks; inline, crossline and time/depth slices read one chunk at a time under the scientific-read limit; Workspace plan view and seismic sections with exact picks; SDK read_slice/export_slices; bundle 2.3; unit, gateway, mounted browser, mutation and live checks (local and S3-compatible store) with measured gateway memory	Pilot; synthetic volumes only (no NLOG or owner volume with established rights); OpendTect application round trip and Evo mappings not checked; little-endian, variable-length traces, other sample formats, irregular grids and full-volume export not supported; no interpretation tools
Agents with approved plans (E5 checkpoint)	Agent principals registered in Settings with narrower scopes, daily limits and expiry; every change runs only against the person’s (or the agent’s setup/run policy) approval of the exact request; provenance on the run; recovery by command id after a lost answer or sign-out; gateway tests incl. crash windows, SDK AgentClient, live rig with the native service ; remote MCP endpoint (streamable HTTP, agent key) with the agent’s reach as tools and exact bounded reads, capability discovery; official MCP client live rig and a required conformance task ; assistants acting through a person’s own sign-in (consent in Workspace, agent rules, header-less MCP use with protected-resource metadata), gateway, browser and conformance checks with fixture identity	Assistant sign-in is qualified with fixture identity only, not yet against the deployment identity provider; MCP clients needing dynamic client registration are not accepted; no automatic approvals for assistants; agents cannot upload or use linked sources
Sandboxed runner jobs (E13)	One rootless Podman container per job (no network, no registry, read-only root and input, no capabilities, unprivileged user, memory/time/CPU/process/output/log limits); agent jobs only after approval; receipt names runner, image and plan; restart re-attach/collect, cancellation, fair queue; gateway tests incl. real Podman in CI and a live rig	Operator-installed Python image only; no GPU, distributed scheduling or hosted execution; Workspace shows jobs only through agent approvals
AI readiness (E14)	Per-purpose AI-use permission (find similar data, train, test) granted by owners to readers and revoked with read access; whole-selection corpus authorization recorded as activity; SDK corpus export = portable bundle + manifest + samples (JSONL/Parquet) with well-grouped reproducible splits and a checker; search by words or a local operator model started without network; gateway, SDK and mounted tests and a live rig	No MCP search tool yet; no training, hosted models or vector database; curves only in corpora
Portable exit (E18)	Versioned bundles (ophiolite.portable-bundle/1 for curves, /2 up to 2.3 for tops, trajectories, grids, meshes, points, fault sticks and seismic slices) with exact originals, descriptors and data; authorised all-or-nothing export; result groups as export-time observations; offline reader and checker with frozen older readers; deterministic zip archives checked before extraction; import of a bundle’s originals into another deployment as the importer’s own private uploads with the bundle named as origin; measured sizes with local and S3 stores	Pilot; copies cannot be recalled; an import brings originals only (no history, groups, grants or lineage) and cannot import seismic slices; tar archives and imports over the upload limit are not supported
Reviewed releases	Two-user synthetic LAS/SQL browser review, exact retained ZIP, revoke/retry/backup tests; retained GeoTIFF unit qualification	Bounded file/SQL pilot; explicit sharing policy; no OSDU sharing or application delivery
Workspace dashboard	Persisted organizations/project associations, routed scientific pages, Mac Chrome navigation and real-service access tests	Private native backend; no organization-wide scientific grant inheritance
Browser well-log inspection	Native and retained curve tracks, exact keyboard picks, shared-scale original/result comparison and signed change summary	Bounded pilot; incompatible or inaccessible parents refuse comparison; no resampling or scientific certification
Component separation	Six version-pinned component repositories; composed and independent package tests	Private development repositories; full service/worker still composed together
Remote surface rendering	Server-generated PNG, revision-qualified numerical picks, browser and Mac transport checks	Synthetic 2D CPU pilot; no production 3D streaming or OSDU view adapter
Offline LAS and explicit publication	Archived internal Qt tooling: local view/export, shared open, reviewed selected-curve publication with durable retries	LAS 2.0 unwrapped; existing project backend; no file watching or native OSDU workbench publication
Independent numerical package	CMake build/install and separate consumer	Experimental C++ package; public stable SDK and ABI not released
Native client, shared curves, operators	Implemented in current worktree/pilot	Not a production-readiness claim
ResInsight → Excel	Existing backend pilot, owner reports working	OSDU Office.js integration pending
ResInsight → QGIS	Actual Mac QGIS 4.2.2 follow/pin, reconnect and access checks	Synthetic PORO, local coordinates, current backend
OSDU well logs	Bounded DDMS Parquet fidelity and historical reads	Not broad OSDU release qualification
Independent reading	Local portable-data experiments	General source/sink UI and customer bucket experience pending
Horizontal raster CRS conversion	USGS EPSG:4326 → EPSG:3857; actual Mac QGIS display/follow/pin	Same geodetic CRS only; bounded small rasters; no vertical or datum shifts
Native scalar-map notifications	Commit-driven gRPC stream to bridge; QGIS HTTP long polling	Bounded pilot; broad multiplexing and large-workspace load unqualified
Scientific assets and composition	Exact public reads, private catalogue publication, separate read/reuse grants, non-admin Python A→B→C; synthetic and NLOG	Bounded LAS; supported 0.x SDK over preview contracts, PyPI publication pending distribution qualification; no hosted execution or native synchronization

Before trying the native pilot

The pilot requires an operator-provisioned environment, scoped credentials, supported application versions and a qualified dataset. The existing demonstration launchers are specific to the owner’s environment; this public documentation does not present them as a general installation process.

Start with the self-contained browser demonstration and independent-reading exercise. A public installation guide will accompany a reproducible supported release.

View the roadmap.

CRS guide · Public-data exercise · API reference.

Workspace guide · Workspace control API.

Workspace foundation status

Private HTTPS/OIDC, verified invitation enrollment and real email delivery are qualified with one configured provider. TOTP and virtual passkeys were tested; physical passkeys, Safari and full customer production acceptance remain open.

The native pilot includes organization-scoped project creation, effective direct/team access, explicit project blocking, atomic organization offboarding, reviewed bounded LAS/GeoTIFF imports and exact scientific descriptions with curve/map profile checks. See access and assets and exchange contracts.

Experimental API/CLI credentials remain short-lived and browser-session-bound; unattended service accounts are not implemented. Application binding inventory is not host telemetry. General OSDU backend parity, durable multi-file ingestion, scientific approval workflow and full production operations remain separate gates. See Workspace foundations.

QGIS account-based browsing

The private QGIS pilot now supports independent browser-approved sign-in, authorized project/asset browsing, follow/pin/local-copy selection and encrypted credential storage. See QGIS Workspace guide and connector identity API.

Operations and customer observability

The scalar-offset pilot now records durable operation events with exact references, lineage and runtime evidence. OAuth QGIS 0.3.0 reports applied revisions and explicit coverage gaps. Real Mac QGIS, browser history/export, customer SQL outage/replay and a linked gateway/worker Jaeger trace were exercised. This does not claim arbitrary host action capture, unattended workload export or production fleet qualification.

Operation history · Activity API.

The observability follow-through adds grouped operations, correct Jaeger links, QGIS 0.4.0 phase timings, independently linked delivery traces, renewable read-only OIDC workload exports and configurable delivery retention/sampling. Actual Mac QGIS, browser and real-provider renewal/revocation checks passed. A 100-subscriber loopback test used one identity and asset; multi-user fleet scale remains unqualified.

The QGIS 0.5 pilot adds scientific context review and native result publication, qualified on QGIS 4.2.2. It creates separate derived assets and verifies exact no-op returns; it does not claim universal edit tracking or automatic vertical-datum conversion.

QGIS connector 0.6 pilot: native Processing observations and version-qualified QGIS 4.2 Raster-menu acceptance-to-output reporting; linked optional diagnostic traces; reviewed new assets or conditional source revisions with retained history. See scientific context and native publication for timing limitations, conflict recovery and no-operation round-trip evidence.

Reversible Workspace raster lifecycle

Connector 0.7 and the current native backend qualify administrator archive/restore, retained historical revisions, QGIS terminal connection states, explicit resume and network backoff. Guide · API. Permanent purge, general OSDU lifecycle and remote-copy erasure are not supported.

Managed source selections

Deployment-enabled experimental managed sources provide file/OSDU discovery, reviewed follow/pin selections and exact exports. QGIS 0.8.0 can consume reviewed GeoTIFF sources and publish explicitly derived native assets with upstream lineage. Actual Mac QGIS native-calculator publication was checked. OSDU application consumption, OSDU map profiles and writeback are not included. See the API contract for bounds.

SQL well-source pilot

The managed-source browser supports administrator-approved SQLite and PostgreSQL well tables, detected column types, reviewed/versioned scientific mappings, bounded full-snapshot following and portable JSON exports. Four synthetic SQLite wells and a real PostgreSQL fixture were checked. This does not provide SQL Server, CDC, general SQL writers or automatic coordinate/depth conversion. See the source workflow and mapping contract.

Workspace editing pilot — 23 September 2026

Individual SQL well records, persistent account-scoped drafts, old/new review, explicit SQLite/PostgreSQL base-table updates and portable LAS curve results were tested. Original data remains independently exportable. SQL write grants are opt-in; OSDU stays read-only. See editing steps and contracts. This is bounded pilot evidence, not general native-format write support.

Source qualification foundation — 23 September 2026

Managed source mapping/fidelity/history reports and the inspector are tested with synthetic source/SQL/LAS fixtures and a live authorized source read. Try the independent demo. Reports do not implement retained-package sharing, multi-asset approval or general OSDU writing.

The Stage 0 follow-up adds a guided deployment-admin registry wizard for files, SQLite, PostgreSQL and OSDU, explicit missing-value preservation and type-specific source descriptions. Project selection stays in Workspace; browser connection creation, a credential vault and SQL Server remain unsupported.

See reviewed releases for the Stage 1 workflow (24 September 2026).

Personal collections and optional file/SQL snapshots: bounded pilot, 24 September 2026. Workflow and limits. Team collection membership and external destination delivery remain deferred. Workspace subscriptions are described below.

Edited snapshots and Workspace subscribers — 24 September 2026

A bounded SQL-well workflow now connects saved drafts to retained input/result packages, explicit update streams and recipient review/pin/follow working copies. Local two-user browser evidence includes dirty protection, session recovery and timer application; API tests cover non-admin recipients and failure/recovery. This is not external-app delivery or OSDU writing. Steps and limits.

Independent Python applications · Application HTTP contract.

OpendTect — 24 September 2026

Bounded Linux 7.0.10 GR native import, GUI edit/save/reopen and separate LAS return were checked with synthetic zero/null data and NLOG HON-GT-01. Native Float32 and missing-edge losses are explicit; the returned LAS retains untouched source precision and missing edges. No automatic sync, general SDK, Windows/macOS, Petrel or Techlog qualification is implied. Workflow and recovery.

Scientific assets and composition

The offline descriptor and Python correction demo is available with synthetic fixtures and downloaded NLOG conformance evidence. It requires no login and publishes nothing. M2 adds exact common reads and authorized result reuse, including a two-user local Python chain. Coordinated deployed restoration and an external participant trial remain separate gates. The supported 0.x SDK covers the documented curve workflow over preview contracts; PyPI publication remains a distribution gate. No AI dataset builder is qualified.

M3 recovery qualification (24 September 2026): the bounded scientific composition pilot now has coordinated cold-recovery tooling, restored-account review, rejected old credentials, exact retained-chain recovery and retryable admission limits. Measured single-gateway fixture behavior is not a production capacity guarantee. See scientific service recovery. Independent external-user validation remains required before expansion.

Owner-directed derived-curve rehearsal — 24 September 2026

A retained LAS may receive explicitly published new curves on its unchanged depth axis, through las-derived-curves/1. The NLOG Alice/Bob exercise has real Mac Python, browser authorization, private publication, explicit sharing and reuse evidence. Workflow, byte limits and recovery. This is an internal rehearsal, not an external M4 trial, hosted execution or general rock-physics certification.

Self-service LAS handoff (M5 pilot)

Browser upload of exact authorized LAS originals, declared attribution/well notes, private catalogue visibility, explicit read/reuse grants and local Python kit. Administrator/compute upload; ordinary authorized members configure and calculate. Scope, limits and recovery. External M4 is deferred; no hosted computation, new domain or native-host claim is added.

Read-first Python and file inspection

The supported 0.x SDK and CLI expose permitted LAS discovery and exact reads without creating an application binding or run. Read access does not require compute/reuse rights. Connect offers a credential-free project or exact-asset configuration; local plots remain local. LAS inspection explains recognized curves, units and missingness before the existing upload, with no repair. Repeated curve names are kept as stated; each repeated curve is addressed by its column, for example GR (column 4). Advanced composition remains available. Existing upload permissions and account-owned SQL-source limits remain. Read-first guide.

Supported developer client — 26 September 2026

Python 3.10/3.12 installed-package checks, native gateway cases, TypeScript checks, four starter commands and clean transitional-kit installation are qualified at reviewed source revisions. The SDK reference records exact scope: curves, separate derived publication, SDK-owned credentials, original-folder recovery and explicit sharing. Six workflow guides ship in the wheel. Contracts remain preview contracts; PyPI/npm publication, stable 1.0, the complete open-source release and general production support are not claimed. Templates use synthetic fixtures; fixture URLs are not live Workspace or customer connector qualification.