Local-first subsurface infrastructure
Build workflows and applications on a canonical runtime for typed assets, operators, derived outputs, provenance, and local persistence.
Ophiolite is a local-first infrastructure layer for subsurface developers. It gives you a canonical runtime, typed asset model, operator/procedure execution, provenance, project/package persistence, and SDK surfaces for workflows, automation, and application embedding.
What It Is
Section titled “What It Is”Use Ophiolite when you want one local runtime to handle:
- project structure for related subsurface work
- typed subsurface assets across implemented and planned families
- operator/procedure execution and derived outputs
- provenance, evidence, and reproducibility
- app-facing access through Python, CLI, Rust, and focused integration layers
How You Use It
Section titled “How You Use It”- Python for the default builder path and local workflow composition.
- CLI for automation, CI, and repeatable operational tasks.
- Rust for direct embedding, deeper integrations, and the canonical core.
Core Workflow
Section titled “Core Workflow”- Create a project.
- Import or discover typed assets.
- Inspect the operator catalog for a chosen asset.
- Run an operator.
- Persist and reuse the derived output.
Why Teams Adopt It
Section titled “Why Teams Adopt It”- Local-first by default: keep workflows close to the data.
- Canonical runtime: one truth for validation, lineage, and persistence.
- Typed assets: move beyond ad hoc file scripts.
- Bring-your-own operators: extend workflows without forking the core.
Start Here
Section titled “Start Here”- Read the docs
- Run the evaluator proof workflow
- Open the TraceBoost bundle viewer
- Write an operator
- Inspect the checked-in evaluator bundle
- Inspect the checked-in product proof bundle
- Read the evaluator status
- Read the product workflow status
- Read the bundle viewer status
- Read the operator-family roadmap
- Explore more examples
- Check the public surfaces