coulomb/ops-hub
2
0
Fork 0
generated from coulomb/repo-seed
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
39080333da3f0369123d8179a6d2cac9a33b2299
ops-hub/SCOPE.md
tegwick 39080333da Complete ops-hub Inter-Hub bootstrap and close bootstrap workplans. 
Extract bootstrap logic into src/ops_hub/bootstrap.py with dry-run support,
public hub discovery, and unit tests. Update the gate probe to accept public
hub listing (200 or 401), document dev commands and architecture, and archive
finished OPS-WP-0001 and OPS-WP-0002 workplans.
2026-07-07 01:49:12 +02:00

2.0 KiB
Raw Blame History

SCOPE

One-liner

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

Core Idea

ops-hub is a domain-specific Inter-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 inter-hub: generic framework and API substrate work remains in inter-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.
  • Inter-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 Inter-Hub framework behavior, API substrate, authentication, or registry semantics.
  • State Hub workstream, 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.
  • Inter-Hub: ops-hub hub, active manifest, seed widgets, and first ops-endpoint-verified event are live in production.

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
Reference in New Issue View Git Blame Copy Permalink