HybridOps governs infrastructure operations that cross multiple systems. It separates the requested outcome from environment policy and implementation, checks readiness before execution, verifies the resulting state, and records the lifecycle while native platforms remain authoritative for what they own.

Choose a path

What you need	Start here
Install HybridOps.Core and prepare a target	Quickstart
See complete operating examples	Reference Scenarios
Run a supported procedure	Runbooks
Find a capability and its evidence	Capability Map
Inspect shipped lifecycle contracts	Blueprint Index
Understand design decisions	Architecture Decision Records
Report a problem or contribute	Contributing

Representative paths

Outcome	Worked example
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 providers	Hybrid WAN Edge and Site Extension
Operate a high-resource network lab across ephemeral compute	Network Lab Continuity Across Ephemeral Compute
Build a platform foundation and hand off workloads	RKE2 HA Platform Foundation

The Reference Scenarios index contains the wider set. The Capability Map links each capability to design, operating and verification material.

Repositories

Repository	Responsibility
HybridOps.Core	Runtime, hyops CLI, contracts, modules, blueprints, validation and run records
HybridOps.Workloads	Versioned desired state for applications and platform workloads

Contributing

Documentation corrections can be raised through HybridOps.Core issues. Include the public page link and the correction, observed behaviour or supporting evidence. Implementation discussion and technical review can use the same issue tracker.