Skip to content
Ophiolite

Surface Matrix

| Surface | Audience | Maturity | Production guidance | Notes | | --- | --- | --- | --- | --- | | CLI | automation and CI | Preview | Good for scripts and operational flows | Platform JSON command boundary | | Python automation | automation and CI | Preview | Good when scripts need structured calls over CLI JSON | No separate domain SDK | | Rust core | embedders and platform teams | Preview | Deepest exact surface | Canonical runtime truth and shared capability vocabulary | | Charts integrations | app teams | Experimental | Secondary to the runtime story | Useful in consumers, not the product headline | | Compatibility surfaces | advanced users and migration work | Internal | Use only when you need older names, adapter shims, or raw transport shapes | Not part of the durable public promise | | Reference apps | internal teams and evaluators | Internal | Do not treat as the platform contract | Ophiolite Workbench is a consumer, not the identity |

Reading the matrix

Section titled “Reading the matrix”

The platform story is the combination of canonical Rust behavior plus thin public control surfaces over that behavior.

The current split is:

  • platform surfaces: Rust core, CLI, Python automation, run bundles, review packets, shared contracts, capability vocabulary
  • compatibility surfaces: interop packages, migration shims, and raw transport-oriented namespaces
  • app-local surfaces: Ophiolite Workbench desktop commands, workflow orchestration, session UX, and import-provider activation

The important rule is that the Ophiolite Workbench desktop command boundary is internal to the app even when it transports canonical contracts.

See stability levels for the label definitions.