How do you use HybridOps?¶
HybridOps is a contract runtime for infrastructure operations. It owns the operation boundary across authority, policy, readiness, ordered execution, verification, recovery, and closure. Each resource platform remains authoritative for its live state.
Operating path: declared intent → resolved contracts and policy → verified readiness → controlled execution → validated state → run record
Choose the path that matches what you need to do.
Operator¶
Install Core, initialise an environment, and run a shipped operation.
Start with the quickstart or open the runbook catalogue.
Platform engineer¶
Follow a complete operating scenario, then trace each capability to its blueprint, module, contract, and verification material.
Browse reference scenarios or use the capability map.
Contributor¶
Inspect the extension contracts, author a module specification, or prepare a focused correction.
Read the contribution guide or author a module spec.
Architect or reviewer¶
Review authority, policy, lifecycle, and evidence boundaries independently of any selected execution pack.
Open the architecture contracts or the decision record index.
Operating model¶
| Part | Responsibility |
|---|---|
| Operation contract | Defines the outcome, authority requirements, inputs, dependency graph, and required checks. |
| Runtime | Resolves environment policy, validates readiness, orders and dispatches each stage, verifies the outcome, and writes environment-scoped state and the run record. |
| Execution pack | Implements a resolved stage behind a versioned module contract. |
| Resource authority | Owns the applied resource state while HybridOps retains the operation decision and verification record. |
Representative operations¶
| Outcome | Worked reference scenario |
|---|---|
| Govern infrastructure from an explicit authority | Authoritative On-Prem Foundation |
| Recover a service and return it safely | PostgreSQL HA DR Cycle |
| Extend networking across sites and execution environments | Hybrid WAN Edge and Site Extension |
| Adopt or operate a high-resource network lab across ephemeral compute | Network Lab Continuity Across Ephemeral Compute |
| Build and operate a highly available Kubernetes platform | RKE2 HA Platform Foundation |
Reference scenarios are repeatable technical case studies from HybridOps-controlled environments. Each identifies the implementation exercised, the state verified and the resulting operating record. Browse the wider reference scenario library or use the capability map to trace a capability to its design, procedure and verification material.