diff --git a/docs/DOME-GEOMETRY-CAPABILITY.md b/docs/DOME-GEOMETRY-CAPABILITY.md
index 180ce72..2a83de2 100644
--- a/docs/DOME-GEOMETRY-CAPABILITY.md
+++ b/docs/DOME-GEOMETRY-CAPABILITY.md
@@ -44,7 +44,7 @@ bill-of-materials calculation. The obvious answer was Blender — it has
 
 ## Registering capabilities
 
-This comparison feeds into the mother node's PostgreSQL `usb_nodes` table.
+This comparison feeds into the mother node's PostgreSQL `hive_nodes` table.
 When a node registers its hardware profile, the capability derivation trigger
 marks nodes that can run `geodesic-dome-mcp` (all of them — numpy + Pillow
 are universal). Nodes that have Blender installed get an additional
diff --git a/docs/SETUP-USB-TO-MOTHER.md b/docs/SETUP-USB-TO-MOTHER.md
index 99022b1..bb1e994 100644
--- a/docs/SETUP-USB-TO-MOTHER.md
+++ b/docs/SETUP-USB-TO-MOTHER.md
@@ -4,7 +4,7 @@
 
 Connects a booted Clawdie USB to the mother node (OSA) via MCP over SSH.
 After setup, `clawdie-hw-probe` runs on the USB, the hardware profile is
-sent to mother, and stored in PostgreSQL `mother_hive.usb_nodes`.
+sent to mother, and stored in PostgreSQL `mother_hive.hive_nodes`.
 
 ## Hosts used in this guide
 
@@ -48,7 +48,7 @@ sent to mother, and stored in PostgreSQL `mother_hive.usb_nodes`.
 │  colibri-mcp-ssh → strips forced-command wrapper              │
 │                  → passes "tools" subcommand to colibri-mcp    │
 │                                                               │
-│  PostgreSQL mother_hive.usb_nodes ← hw-probe JSON stored       │
+│  PostgreSQL mother_hive.hive_nodes ← hw-probe JSON stored       │
 │                                                               │
 └───────────────────────────────────────────────────────────────┘
 ```
@@ -203,13 +203,13 @@ echo "$HW_JSON" | python3.11 -m json.tool | head -15
 # 3. Send to mother via MCP (once node_register tool exists on mother)
 # For now: manual insert via SSH to mother
 echo "$HW_JSON" | ssh m0th3r 'cat - | sudo -u postgres psql -d mother_hive \
-    -c "INSERT INTO usb_nodes (hostname, hw_profile, status) \
+    -c "INSERT INTO hive_nodes (hostname, hw_profile, status) \
     VALUES ('\''$(hostname)'\'', '\''$(cat)'\''::jsonb, '\''online'\'') \
     ON CONFLICT (hostname) DO UPDATE SET hw_profile = EXCLUDED.hw_profile, last_seen = now();"'
 
 # 4. Verify on mother
 ssh m0th3r 'sudo -u postgres psql -d mother_hive \
-    -c "SELECT hostname, status, capabilities FROM usb_nodes;"'
+    -c "SELECT hostname, status, capabilities FROM hive_nodes;"'
 # Expected: both osa.smilepowered.org and clawdie-usb listed
 ```
 
diff --git a/docs/USB-MOTHER-MCP-CONNECTION.md b/docs/USB-MOTHER-MCP-CONNECTION.md
index 0eb1f9f..09456bf 100644
--- a/docs/USB-MOTHER-MCP-CONNECTION.md
+++ b/docs/USB-MOTHER-MCP-CONNECTION.md
@@ -7,7 +7,7 @@
 Boot the live USB, and the colibri-daemon automatically connects to mother
 (OSA) via MCP over SSH. The first action on autospawn: `clawdie-hw-probe` runs,
 hardware profile is sent to mother via `colibri_external_mcp_call_tool`, and
-mother stores it in PostgreSQL `mother_hive.usb_nodes`.
+mother stores it in PostgreSQL `mother_hive.hive_nodes`.
 
 ## Current state
 
@@ -135,7 +135,7 @@ HW_JSON=$(sudo clawdie-hw-probe 2>/dev/null)
 #  with the mother server registered)
 
 # 3. Verify on mother:
-sudo -u postgres psql -d mother_hive -c "SELECT hostname, status, capabilities FROM usb_nodes;"
+sudo -u postgres psql -d mother_hive -c "SELECT hostname, status, capabilities FROM hive_nodes;"
 ```
 
 Expected: the USB node appears in PostgreSQL with hardware profile and