Surfaces and Apps
Audience: anyone deciding where to do a piece of work Status: Current
Ophiolite exposes a small set of surfaces over one platform. The mental model is short: one Workbench shell, thin automation, durable proof artifacts.
The product shell
Section titled “The product shell”Ophiolite Workbench is where humans look and decide: browse typed assets, run operators, inspect views, compare runs, review evidence, approve or request changes, and export signed review packets.
Where agents enter
Section titled “Where agents enter”Agents and scripts do not drive the Workbench UI. They operate through the same backend semantics:
- CLI (
ophiolite) — JSON-first commands covering the full flow lifecycle (validate, plan, run, inspect, compare), attestation (sign, verify, packet export), project queries, and analyses such as the well tie. - Python (
ophiolite_automation) — thin wrappers over the same JSON surfaces; the draft → validate → run → inspect → compare → sign → packet loop closes from a script.
What travels
Section titled “What travels”- RunBundles are the internal/reopenable artifact that moves between machines and organizations: a self-contained, reopenable, signed record of a run — recipe, plan, report, artifacts, digests, and a hash-chained event log.
- Review Packets wrap run evidence with the deliverable’s review state into a signed, offline-verifiable artifact for a partner, regulator, or internal assurance reviewer.
Whatever surface produced a run, Workbench can inspect it: the record is the project’s, not the command’s.