SCOPE

One-liner

Operations / System 1 extension for Core Hub, focused on operational truth, readiness evidence, and migration gates.

Core Idea

ops-hub is a domain-specific Core Hub extension. It should professionalize operations by making environments, hosts, clusters, services, endpoints, releases, backups, incidents, risks, runbooks, readiness gates, and migration waves explicit and evidence-backed.

The repo is intentionally separate from Core Hub: generic framework and API substrate work remains in core-hub; operations-specific collectors, adapters, probes, bootstrap clients, UI/extensions, tests, and packaging belong here.

In Scope

Operations hub implementation code and tests.
Ops vocabulary clients, collectors, adapters, and scheduled probes.
Core Hub bootstrap/smoke tooling for the ops-hub extension.
Operations service catalog, readiness, migration, endpoint, backup, restore, incident, and runbook models.
Repo-local workplans for growing the Operations / System 1 extension.

Out of Scope

Generic Core Hub framework behavior, API substrate, authentication, or registry semantics.
State Hub workplan, task, decision, or progress implementation.
Railiance infrastructure, cluster, platform, enablement, or app desired state.
Manual production DB seeding unless the operator explicitly chooses that fallback.
Irreversible operational decisions without human approval.

Current State

Status: production bootstrap complete (2026-07-07).
Implementation: Python package under src/ops_hub/, operator scripts, seeds, tests, and Makefile targets for gate probe and attended bootstrap.
Core Hub: ops-hub hub, active manifest, seed widgets, and ops-endpoint-verified events post to production Core Hub.

Getting Oriented

Start with: INTENT.md
Agent instructions: AGENTS.md
Workplans: workplans/
HelixForge handoff: /home/worsch/helix-forge/workplans/HF-WP-0001-establish-ops-hub-first-extension.md

1.9 KiB Raw Permalink Blame History