docs(CORE-WP-0007): point ops-hub extension at Core Hub
This commit is contained in:
parent
4ca5c5906e
commit
7ac1871f94
4 changed files with 24 additions and 23 deletions
19
SCOPE.md
19
SCOPE.md
|
|
@ -2,33 +2,32 @@
|
|||
|
||||
## One-liner
|
||||
|
||||
Operations / System 1 extension for Inter-Hub, focused on operational truth,
|
||||
Operations / System 1 extension for Core Hub, focused on operational truth,
|
||||
readiness evidence, and migration gates.
|
||||
|
||||
## Core Idea
|
||||
|
||||
`ops-hub` is a domain-specific Inter-Hub extension. It should professionalize
|
||||
`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 `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.
|
||||
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.
|
||||
- Inter-Hub bootstrap/smoke tooling for the `ops-hub` extension.
|
||||
- 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 Inter-Hub framework behavior, API substrate, authentication, or
|
||||
- Generic Core 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.
|
||||
|
|
@ -41,8 +40,8 @@ here.
|
|||
- 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.
|
||||
- Core Hub: `ops-hub` hub, active manifest, seed widgets, and
|
||||
`ops-endpoint-verified` events post to production Core Hub.
|
||||
|
||||
## Getting Oriented
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue