Ophiolite component boundaries
Ophiolite separates data coordination, application adapters, scientific calculation and user interfaces. Existing ArrayBridge wire and package names remain compatible. The split does not move customer datasets or create another scientific authority.
| Component | Owns |
|---|---|
| Platform | Shared contracts, access checks, revisions, publication, notifications and backend adapters |
| Connectors | Mapping between application APIs and scientific asset contracts |
| Workspace | Browser data-management interface; the organization/OSDU workspace remains roadmap work |
| Workbench | Native scientific desktop interface |
| Execution | Calculation runtime and supervised workers |
| Science | Numerical algorithms independent of GUI/network code |
| View | Experimental server-side visual rendering |
OSDU service APIs remain the foundation in OSDU mode. The existing demonstration backend remains distinct from that integration. A repository split does not imply that all current clients now use OSDU.
Remote rendering pilot
Section titled “Remote rendering pilot”In a provisioned pilot, open the View browser page and enter the access credential provided by the operator. The server renders a synthetic scalar surface into an image. Changing the viewport requests another image; picking a cell returns its exact value and unit. The browser does not download the full numeric grid.
Requests carry the scene’s exact revision. A mismatched revision fails instead of silently switching to the latest data. Missing cells render transparent. This fixture uses local grid coordinates; it makes no geographic CRS claim.
If authorization fails, obtain a current credential. If the revision changes, reload the scene metadata. A failed request must not be interpreted as a new image. This is a private 2D CPU experiment, not a supported production 3D viewer, live asset subscription, or multi-user authentication service.
Developer contract and limits
Section titled “Developer contract and limits”View reads an immutable synthetic JSON scene containing asset identity, revision,
unit, width, height and finite numeric or null cell values. Its private experimental
API separates scene metadata (/scene), revision-qualified PNG frames (/frame)
and exact numeric inspection (/pick). It bounds viewport dimensions and dataset
size. Bearer authentication, loopback binding and an authenticated tunnel qualify
the current deployment; production OIDC, quotas and shared sessions remain work.
These routes are not a stable public SDK.
Platform owns revision/access semantics; View must eventually consume those contracts rather than invent a second data authority. Connectors own application adaptation. Science owns algorithms and Execution owns running them. The full current-backend server and worker still use a composed integration build.
See availability.