# 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: active bootstrap.
- Implementation: no executable source tree yet; first real workplan is seeded
  in `workplans/OPS-WP-0002-interhub-extension-bootstrap.md`.
- Live Inter-Hub production gate: `/api/v2/hubs` still returned `404` on
  2026-06-06, so supported API bootstrap is not yet available 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`