{"repo":"hybridops-tech/hybridops-core","free":true,"listed":false,"github":"https://github.com/hybridops-tech/hybridops-core","clone":"git clone https://github.com/hybridops-tech/hybridops-core.git","description":"Community edition of HybridOps. A platform exploring contract-driven automation for hybrid infrastructure.","language":"Python","stars":191,"topics":["ansible","devops-platform","disaster-recovery","gitops","hybrid-infrastructure","hybridops","infrastructure-automation","kubernetes","network-automation","platform-engineering"],"license":null,"category":"deployment-docker-iac","readme_excerpt":"HybridOps Core A contract-driven runtime for governed infrastructure operations across hybrid environments. = 3.11\" src=\"https://img.shields.io/badge/python-%3E%3D3.11-blue\" 80 runtime modules 28 reference blueprints 52 public decision records 8 supported targets --- What this is An individual control system can complete its work while the wider operation remains incomplete: an authority may be stale, a dependency unavailable, a result unverified, or teardown unfinished. HybridOps Core governs that cross-system transition through a stable operator contract across environments, lifecycle stages, and implementation changes. Native platforms remain authoritative for their own resources; Core governs whether the wider operation may advance. A ModuleSpec defines intended capability. A Profile carries environment policy. A Driver binds execution. A versioned Pack carries implementation assets. A Blueprint composes modules into a dependency-aware lifecycle. The runtime resolves these contracts, performs preflight, executes the selected implementation, publishes outputs, and writes a structured run record. Core governs across these handoffs: - contract resolution: deterministic input merge, validation, dependency ordering, and environment policy - controlled execution: driver-based dispatch through versioned implementation packs and isolated workdirs - preflight and verification: required conditions and module probes around execution - run records: non-secret execution records with m","default_branch":null,"files":null,"tree":[],"storefront":"/r/hybridops-tech","claimed":false,"request_supported":{"post":"https://gitbuyer.com/r/hybridops-tech/hybridops-core/request-supported","requests":0},"note":"indexed from public GitHub; nothing is for sale on this page. Clone it from GitHub. Paid listings live at /search."}