Operator Contracts
Audience: operator maintainers Status: Preview
An Ophiolite operator is not just a function. It is a cataloged, revision-aware execution contract.
Required Shape
Section titled “Required Shape”Every operator needs:
- stable operator id
- owning family
- typed inputs and parameters
- declared output family
- preview/materialization behavior
- validation rules
- provenance/evidence records
- execution tests
Execution Rule
Section titled “Execution Rule”Operator drafts may reference a data item, semantic role, or follow-latest selection. Before execution, the backend must resolve inputs to exact revisions. Provenance must record the exact revisions and parameters used.
Proof Rule
Section titled “Proof Rule”If an operator can materialize output, the resulting run must be inspectable as a bundle or project run record with artifacts, digests, assertions, lineage, events, and actor context.