Pre-release. Ophiolite runs today for design partners; public source and server image publication are in preparation.

Ophiolite

Product / Data model

Data model

Wells and wellbores are real things with declared identities, and every version fixes its data, its context and its interpretation together.

For data managers who need one authoritative identity per well and one exact meaning per version.

  • Available Wells and wellbores as real things
  • Available One record of data, context and interpretation
  • Partial Explicit result versions
The wells and wellbores view: wellbore HON-GT-01, part of well HON-GT-01, with the log that belongs to it and the evidence stated.
A wellbore with its well and the evidence for what belongs to it. NLOG.NL, Dutch subsurface portal (TNO / Geological Survey of the Netherlands): HON-GT-01, HON-GT-01-S1 and HON-GT-02 composite logs, retrieved 10–11 September 2026; the despiked curve is a demonstration edit. Terms: NLOG disclaimer (LicenseRef-NLOG-Disclaimer-2016-08-09). Captured 2026-09-28 from release 2026.10.4.
The Data page listing three NLOG composite logs and a published result, each with its source, updates and version.
Each version keeps its source. NLOG.NL, Dutch subsurface portal (TNO / Geological Survey of the Netherlands): HON-GT-01, HON-GT-01-S1 and HON-GT-02 composite logs, retrieved 10–11 September 2026; the despiked curve is a demonstration edit. Terms: NLOG disclaimer (LicenseRef-NLOG-Disclaimer-2016-08-09). Captured 2026-09-28 from release 2026.10.4.

Key features

Typed wells and wellbores
Created with an external identity or as provisional — never guessed from names or coordinates.
Evidenced associations
A log belongs to a wellbore because a person asserted it, with the evidence they gave.
Exact versions
A version fixes the bytes, the declared context and the interpretation; it never changes.
Lineage
One hop each way from any version: what it came from and what was derived from it.
Identity history
Attaching an external identity to a provisional well is audited, never silent.
Audience rules
A well or wellbore is visible only to the people it is shared with.

How it works

  1. Create a well with its authority and key, or as provisional.
  2. Associate an exact version of a log, tops or a surface with its wellbore, stating the evidence.
  3. Navigate from the well to its exact versions in the Workspace or in Python.

Technical details

Entities and associations are rows in the one metadata and permission core that also holds versions and grants, so a read of a version and of its context is one consistent answer.

Use cases

One well, many names

Keep one well with its authority key while files arrive under local names.

Trace a result

Follow a published result back to the exact log version it used.

Hand over a field

Everything associated with a wellbore travels in a bundle with it.

Not yet, and not planned

  • Explicit result versions: Connector-owned inputs are not versioned this way

Not planned: suite-wide petrel or techlog replacement; a general application builder or marketplace; universal format conversion.

Read more