ops-hub-bootstrap

wiki/OpsHubBootstrapRunbook.md

@@ -29,7 +29,15 @@ VSM classification is stored in the manifest capability description for now:
 - `vsm_function`: `OPS`
 - `vsm_system`: `S1`
 
-Inter-Hub does not yet have first-class hub metadata columns for these values.
+Newer Inter-Hub schemas have first-class hub metadata columns for these values.
+The SQL fallback sets those columns when present and still carries the same
+classification in the manifest description for older deployments.
+
+As of the 2026-05-19 access check, the workstation kubeconfig only points at
+CoulombCore (`92.205.130.254`) and does not include the Railiance01
+(`92.205.62.239`) cluster where `hub.coulomb.social` resolves. SSH key access
+to `root`, `worsch`, and `ubuntu` on Railiance01 was denied, so the SQL fallback
+must be run from a host/session that already has Railiance01 cluster access.
 
 ## UI Path
 
@@ -61,6 +69,31 @@ Inter-Hub does not yet have first-class hub metadata columns for these values.
 11. Seed the widgets from `wiki/ops-hub-widgets.seed.json` through the UI or
     migration fallback.
 
+## SQL Fallback Path
+
+From a shell with Railiance01 Kubernetes access, run:
+
+```bash
+kubectl exec -i -n databases net-kingdom-pg-1 -- \
+  psql -U postgres -d interhub \
+  < /home/worsch/helix-forge/wiki/ops-hub-bootstrap.sql
+```
+
+If using the HostEurope kubeconfig from the workstation, first restore
+`~/.kube/config-hosteurope` as documented by `railiance-cluster`, then run:
+
+```bash
+KUBECONFIG=~/.kube/config-hosteurope \
+kubectl exec -i -n databases net-kingdom-pg-1 -- \
+  psql -U postgres -d interhub \
+  < /home/worsch/helix-forge/wiki/ops-hub-bootstrap.sql
+```
+
+The SQL fallback creates the hub, active manifest, registry entries, API
+consumer row, and seed widgets. It does not create the one-time visible static
+API key; generate that in the authenticated Inter-Hub UI and store it outside
+Git.
+
 ## Validation
 
 After manifest activation:

wiki/ops-hub-bootstrap.sql

@@ -23,6 +23,25 @@ SET name = EXCLUDED.name,
     domain = EXCLUDED.domain,
     hub_kind = EXCLUDED.hub_kind;
 
+-- Newer inter-hub schemas have first-class VSM metadata columns. Keep this
+-- block conditional so the bootstrap still works against an older deployment
+-- where the metadata is only carried by the manifest description.
+DO $$
+BEGIN
+    IF EXISTS (
+        SELECT 1
+        FROM information_schema.columns
+        WHERE table_name = 'hubs'
+          AND column_name = 'hub_family'
+    ) THEN
+        UPDATE hubs
+        SET hub_family = 'vsm',
+            vsm_function = 'OPS',
+            vsm_system = '1'
+        WHERE slug = 'ops-hub';
+    END IF;
+END $$;
+
 WITH hub AS (
     SELECT id FROM hubs WHERE slug = 'ops-hub'
 )