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

docs: complete predecessor deployment reality plan

Browse source 
Assistant: codex
Assistant-Model: gpt-5.6-sol
Assistant-Session: 01a06d83-1cbc-71f2-b0dc-e0f48cedae43
This commit is contained in:
tegwick 2026-09-04 22:23:49 +02:00
parent 94e31e3d92
commit 5979dd895a
6 changed files with 180 additions and 11 deletions
Download patch file Download diff file Expand all files Collapse all files

2
inventory/README.md
View file

@ -20,6 +20,8 @@ implementation workplans (T05).
| [`mcp-tools.yaml`](mcp-tools.yaml) | MCP tools |
| [`dashboard.yaml`](dashboard.yaml) | Observable dashboard pages |
| [`jobs-callers-ops.yaml`](jobs-callers-ops.yaml) | Jobs, callers, ops deps, migrations |
| [`inter-hub-disposition.yaml`](inter-hub-disposition.yaml) | Generation-2 capability destinations and current providers |
| [`repository-scope-reality-20260904.md`](repository-scope-reality-20260904.md) | Participating repository scope/reality ledger and routed corrections |
## Disposition legend

70
inventory/inter-hub-disposition.yaml Normal file
View file

@ -0,0 +1,70 @@
inventory_id: SHR-INV-0002
title: Inter-Hub generation-2 capability disposition
version: 0.1.0
created: '2026-09-04'
updated: '2026-09-04'
workplan_task: SHR-WP-0002-T02
source_evidence:
- core-hub/INTENT.md
- core-hub/workplans/archived/260703-CORE-WP-0005-data-migration-and-cutover.md
- core-hub/workplans/archived/260708-CORE-WP-0007-haskell-retirement.md
- core-hub/workplans/CORE-WP-0011-railiance01-production-relocation.md
state_values: [served, planned, dropped]
rules:
- retired implementation does not imply dropped capability
- served names the observable current provider
- planned requires a named owner and workplan or routed intake
capabilities:
- id: domain-hubs
generation_2_intent: Separate domain hubs with shared framework contracts.
state: served
current_provider: core-hub
evidence: Production /api/v2 hub registry and migrated ops-hub manifest.
target: hub-core extension contract with domain-owned implementations
target_owner: hub-core
target_workplan: HUB-WP-0004
- id: shared-manifests
generation_2_intent: Publish hub manifests through a common contract.
state: served
current_provider: core-hub
evidence: The production cutover imported and validated the ops-hub manifest.
target: hub-core manifest and extension contract
target_owner: hub-core
target_workplan: HUB-WP-0004
- id: widgets
generation_2_intent: Domain-provided operator widgets with registered types.
state: served
current_provider: core-hub
evidence: CORE-WP-0005 migrated 15 widgets and all seven ops widget types.
target: hub-core projection and extension UI contracts
target_owner: hub-core
target_workplan: HUB-WP-0004
- id: registries
generation_2_intent: Shared hub, widget-type, event-type, annotation, and policy registries.
state: served
current_provider: core-hub
evidence: Production compatibility smokes served 26 widget types and 30 event types.
target: versioned hub-core registries
target_owner: hub-core
target_workplan: HUB-WP-0004
- id: interaction-events
generation_2_intent: Common interaction-event publication and query.
state: served
current_provider: core-hub
evidence: CORE-WP-0005 migrated an interaction event and verified /api/v2 parity.
target: hub-core interaction contracts; activity-core remains execution/event-bridge authority
target_owner: hub-core
target_workplan: HUB-WP-0004
- id: unified-operator-surface
generation_2_intent: One navigable surface for hubs, widgets, events, and registry facts.
state: planned
current_provider: core-hub
evidence: Core Hub retains the compatibility/operator surface during consolidation.
target: hub-core projection UI composed from domain extensions
target_owner: hub-core
routed_intake: 01a06e07-658e-73fa-9164-0b522504c0ee
summary:
capabilities: 6
served: 5
planned: 1
dropped: 0

34
inventory/repository-scope-reality-20260904.md Normal file
View file

@ -0,0 +1,34 @@
# Participating repository scope versus reality
**Workplan task:** `SHR-WP-0002-T04`
**Observed:** 2026-09-04
This ledger records current project interpretation and routes source-text
corrections to their owners. It does not make this project authoritative for
another repository's scope.
| Repository | Stated position | Observed reality | Disposition / route |
| --- | --- | --- | --- |
| `hub-core` | Importable package and target runtime; preserves a library boundary. | Candidate runtime is deployed on railiance01 and is the consolidation target. | Aligned; continue `HUB-WP-0004`. |
| `core-hub` | Generation-3 production framework; hub-core described as a shared library with a future host decision. | Core Hub moved to railiance01 under `CORE-WP-0011`; hub-core now has a selected runtime shape and deployed candidate. | Refresh current-state prose: `01a06e07-7ca4-70de-a011-f9aad8655a50`. |
| `state-hub` | Local-first coordination service; current scope does not foreground retirement. | Primary runs on railiance01; repository files remain authoritative while capabilities are being dispositioned. | Corrected in `STATE-WP-0081`; dashboard handoff: `01a06e07-658e-73fa-9164-0b522504c0ee`. |
| `repo-manager` | Repository representation, file-backed indexing, and governed repository control. | Exact-commit Forge reconciliation is operational and replaced shared-checkout registrar writeback. | Aligned; preserve boundary. |
| `activity-core` | Event bridge and execution authority; State Hub progress is a current safe sink. | Matches live transitional operation; it remains a migration caller until successor sinks are proven. | Aligned but re-check at `G-FREEZE`. |
| `issue-core` | Optional external issue-tracker connector, not source of repository work. | Boundary is accurate; one obsolete Gitea PyPI publication target remains. | Registry cleanup: `01a06e08-7a37-7a86-b456-67a40fdc3fef`. |
| `the-custodian` | Canon/continuity authority; standalone State Hub only as integration. | Matches the extraction and retirement architecture. | Aligned. |
| `ops-hub` | Operations extension for Core Hub; generic framework remains in core-hub. | Domain ownership is correct, but the target generic framework owner is hub-core; Core Hub is transitional compatibility runtime. | Refresh ownership language: `01a06e07-ab16-734e-89b2-4b59796d5073`. |
| `fin-hub` | Financial authority consuming generic hub primitives. | Boundary remains valid; Fabric authority correction already recorded separately. | Aligned. |
| `railiance-fabric` | Repository-authored ecosystem graph and State Hub read-model export. | Boundary remains valid; State Hub is a replaceable consumer, not author. | Aligned. |
| `ops-bridge` | Describes State Hub as workstation-local and remote nodes phoning home. | Primary State Hub now runs on railiance01; bridge/relay are access paths, not authority. | Refresh topology language: `01a06e07-cdc3-763d-a746-eaaa289baad6`. |
## Registry and lane routes found by the same reconciliation
| Owner | Required correction | Routed intake |
| --- | --- | --- |
| `ops-warden` | Decide `inter-hub-bootstrap-ssh`; retire/repoint obsolete Gitea publication lanes without moving credential custody. | `01a06e07-f2f9-7586-9745-b359eb0025b6` |
| `whynot-design` | Publish `@whynot/design` through Forgejo before the lane is repointed. | `01a06e08-6936-7762-a347-f832182b7705` |
| `issue-core` | Remove the redundant Gitea PyPI upload target. | `01a06e08-7a37-7a86-b456-67a40fdc3fef` |
| `railiance-platform` | Remove the legacy Gitea ArgoCD source allow-list after confirming it is inert. | `01a06e08-9718-786e-b753-b56aa5f4c005` |
All listed intakes were moved to `routed` on 2026-09-04. Owner repositories
must promote or absorb them through their normal workplan process.