First extension struggles. Should I just drop the haskel approach?

wiki/OpsHubInventory.md

@@ -1,18 +1,34 @@
 # Ops Hub Initial Inventory
 
-Date: 2026-05-16
+Date: 2026-06-06
 
 ## Purpose
 
 This document is the first structured inventory for `ops-hub`, the VSM
 Operations / System 1 hub. It turns the current operations situation into a
-catalogable model before `ops-hub` has its own repository, collectors, or UI.
+catalogable model and now serves as a handoff reference for the dedicated
+`ops-hub` implementation repository.
 
 Source background:
 
 - `wiki/CurrentOperationsSituation.md`
 - `workplans/HF-WP-0001-establish-ops-hub-first-extension.md`
 
+## Repository Boundary
+
+As of 2026-06-06, `ops-hub` implementation belongs in `/home/worsch/ops-hub`
+with remote `gitea-remote:coulomb/ops-hub.git`.
+
+- `ops-hub` owns future collectors, adapters, scheduled probes, runtime
+  packaging, UI/extensions, tests, and Inter-Hub bootstrap/smoke clients.
+- `inter-hub` remains the generic hub framework, manifest/registry substrate,
+  authentication surface, widget/event API, and bootstrap API owner.
+- `helix-forge` keeps this initial inventory and readiness vocabulary as
+  architecture and handoff material until the implementation repo ports or
+  supersedes it.
+- Railiance repos own deployable infrastructure/service state and the
+  operational evidence that `ops-hub` should surface.
+
 ## VSM Placement
 
 | Field | Value |