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

SCOPE.md

@@ -63,6 +63,8 @@ and operating model. It is not yet an application implementation.
 - You need deployable infrastructure code; use the relevant Railiance repos.
 - You need State Hub implementation details; use `the-custodian/state-hub`.
 - You need Inter-Hub API or UI implementation details; use `inter-hub`.
+- You need deployable `ops-hub` implementation work; use `/home/worsch/ops-hub`
+  (`gitea-remote:coulomb/ops-hub.git`).
 - You need a production-ready HelixForge runtime; this repo is not there yet.
 
 ---
@@ -84,9 +86,9 @@ test suite. `INTENT.md` is the main source of truth.
 - Upstream dependencies: Orthogonal Architecture Standard vocabulary and the
   State Hub workplan/coordination model.
 - Downstream consumers: future HelixForge implementation repos, Inter-Hub
-  extension work, and capability catalog/tooling efforts.
+  extension work, `ops-hub`, and capability catalog/tooling efforts.
 - Often used with: `inter-hub`, `the-custodian/state-hub`, Railiance ops repos,
-  and future `ops-hub` artifacts.
+  and the `ops-hub` implementation repo.
 
 ---
 
@@ -106,6 +108,8 @@ test suite. `INTENT.md` is the main source of truth.
 ## Related / Overlapping Repositories
 
 - `inter-hub` - governed interaction substrate that HelixForge may extend.
+- `ops-hub` - VSM Operations / System 1 Inter-Hub extension implementation;
+  local path `/home/worsch/ops-hub`.
 - `the-custodian/state-hub` - cross-repo state, workstream, capability, and
   progress index.
 - `railiance-infra`, `railiance-cluster`, `railiance-platform`,