coulomb/ops-hub
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

docs(CORE-WP-0007): point ops-hub extension at Core Hub
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 3s
Details

Browse source
This commit is contained in:
tegwick 2026-07-08 12:48:04 +02:00
parent 4ca5c5906e
commit 7ac1871f94
4 changed files with 24 additions and 23 deletions
Download patch file Download diff file Expand all files Collapse all files

17
INTENT.md
View file

@ -7,16 +7,17 @@ updated: "2026-06-06"
## Why it exists
`ops-hub` is the Operations / System 1 extension for Inter-Hub. It turns
operational reality into governed, queryable, and evidence-backed hub records:
environments, hosts, clusters, services, endpoints, releases, backups,
`ops-hub` is the Operations / System 1 extension for the interaction framework.
It turns operational reality into governed, queryable, and evidence-backed hub
records: environments, hosts, clusters, services, endpoints, releases, backups,
incidents, risks, runbooks, readiness gates, and migration waves.
It exists because Railiance and HelixForge operations need a durable
operational truth surface while the current CoulombCore environment transitions
toward the ThreePhoenix production shape. State Hub continues to own
workstreams and decisions; Inter-Hub continues to own the generic hub substrate.
`ops-hub` owns the operations extension behavior built on top of that substrate.
operational truth surface while the fleet transitions toward railiance01
production. State Hub continues to own workstreams and decisions; **Core Hub**
owns the production framework API (`hub.coulomb.social` since 2026-07-03).
Historical Haskell Inter-Hub lives in `inter-hub-haskell` (retired). `ops-hub`
owns the operations extension behavior and posts evidence to Core Hub.
## Governing principle
@ -25,7 +26,7 @@ authority, ownership boundaries, or operational promises should be captured in a
workplan before implementation.
The first implementation rule is: domain-specific runtime code belongs here,
while generic hub framework behavior belongs in `inter-hub`.
while generic hub framework behavior belongs in Core Hub.
## What it enables