Current Scope and Maturity

Audience: evaluators and adopters
Status: Preview

Ophiolite’s direction is clear, but not every public surface is equally mature.

The platform identity is the local-first runtime for typed assets, execution, derived outputs, provenance/evidence, and persistence. Logs/LAS and seismic are current implementation slices with different maturity levels.

Current shape

• The Rust core is the canonical runtime and deepest implementation surface.
• The Python SDK is the preferred builder entry path, but still reuses CLI-backed operations underneath.
• The CLI is useful for automation, inspection, package creation, and project admin-style tasks.
• Operator packages are the main extensibility story and now support project-local Python runtime isolation.

Practical maturity

Area	Maturity	Notes
Canonical runtime semantics	Preview	Direction is stable even where APIs are still widening.
Python SDK	Preview	Best starting point for builders, but not yet the widest workflow surface.
CLI	Preview	Useful for scripting and inspection today.
Install doctor	Preview	Implemented as JSON output for local support and CI checks.
Rust embedding	Preview	Deepest and most exact surface.
Operator packages	Preview	First external Python runtime path is implemented.
Logs/LAS slice	Preview	Deepest source-file maturity today; not the product boundary.
Seismic runtime slices	Preview	Useful post-stack and gather paths exist, with family-specific scope limits.
Charts/app integrations	Experimental	Useful for app composition, but secondary to the runtime story.
Workbench installer	Planned	First target is a signed Windows installer with a sample project path.

Recommended production posture

Use Ophiolite today when:

• you want a local-first infrastructure layer
• you can tolerate preview-stage API evolution
• you value one canonical runtime more than polished breadth in every wrapper

See System Requirements for the first support targets.

Next: Build Workflows