Operator Packages
Audience: platform and operator maintainers Status: Preview
Ophiolite treats built-in compute and extensions as one operator system. The durable surface is the operator manifest plus Rust-owned validation, execution-mode handling, provenance, and derived-asset persistence.
Operator Model
Section titled “Operator Model”An operator package should declare:
- package name
- package version
- runtime kind
- compatible Ophiolite version range
- exported operator ids
- entrypoint information
- supported asset families
- expected provenance and evidence records
Execution Model
Section titled “Execution Model”Operator execution should flow through platform-owned commands and project policy:
- preview and materialize are explicit modes
- materialization is policy-gated
- inputs resolve to exact revisions before execution
- generated outputs carry provenance
- run bundles and event logs record the execution
Current Implementation
Section titled “Current Implementation”The repo supports:
- per-project installation
- project operator locking
- manifest-driven catalog exposure
- Rust-owned validation and provenance
- derived-asset persistence through the normal project flow
Package-specific helper APIs are intentionally not a public product story. Operator packages must not bypass the platform execution and evidence chain.