Active Mounts

Inspect the live mount state of every hive — sentient, node, or general-purpose — that's currently open in the app.

When to use this

Something feels stuck during a switch and you want to see what's actually mounted

You're auditing which hives are live before unmounting external storage

You're debugging a per-node hive issue and want to confirm the layered mount worked

You're curious what mount paths the app is using on this OS

For the conceptual background — what a hive is, what makes a hive "active" — see Sentient Identity.

Reach it from the Hive Lobby

The Hive Lobby is reachable two ways:

Click the hive button (bare green hexagon glyph, left side of the Lanyard) — visible only when a sentient hive is mounted.
Sentient Lobby → Hives — from the sentient chip, then the Hives entry.

Inside the Hive Lobby, pick Active mounts to open ActiveMountsActivity.

What you'll see

ActiveMountsActivity is a Qt table view backed by MountedHivesModel. The columns:

Column	What it shows
Identicon	The owning entity's identicon (sentient identicon for sentient hives; node identicon for node hives; blank for general-purpose hives).
Type	`Sentient` / `Node` / `General` per §HT-1's typed-hive taxonomy.
Display name	The owning entity's friendly name (sentient name for `SID-`, node name for `NID-`, free-form for general).
On-disk id	The raw hive identifier — `SID-<hex>` for sentient hives, `NID-<hex>` for node hives, the chosen name for general. Useful when correlating against logs.
Mount path	The OS-level path the encrypted volume is mounted at. Typical layout on Linux: `${OCTOMY_BASE}/hivecluster-0/<volume>/`.
Mount time	When this mount happened. Useful for telling which side of a switch is fresh.

Rows refresh in place when a mount or unmount happens — the model subscribes to HiveSession's hiveMounted / hiveUnmounted / nodeHiveMounted / nodeHiveUnmounted signals.

What a healthy session looks like

After §SP-1's auto-create on a new device, you'll see exactly one row:

Type Sentient, identicon = your face, display name = your adjective_noun phrase, on-disk id SID-<your-sid-hex>.

After selecting a Node (§SP-7's node-hive ignition), you'll see two rows — the sentient row plus a Node row layered on top:

Type Node, identicon = the node's identicon, display name = the node's name, on-disk id NID-<your-nid-hex>.

The node row's mount path is under the sentient row's mount path — the node hive is a layered mount on top of the sentient volume, not a sibling.

What it doesn't show

ActiveMountsActivity is a read-only diagnostic surface. It doesn't let you unmount or switch identities — those go through:

Switch Sentient for sentient unmount + re-mount
Switch Node for node unmount + re-mount
The Hive Lobby's Unmount entry for a full session end

The activity also doesn't show future mounts (catalog of registered hives that aren't currently mounted) — for that, see Sentient Selection from the lanyard sentient chip.

Troubleshooting

A row I expect to see is missing. The mount probably failed silently. Check the app log for a mountHiveAsync failed line near the relevant SID/NID. Common causes: wrong passphrase on the sentient hive, corrupted key file on the node hive, drive number collision (rare since §SP-7 / Hive::allocateDriveNumber).

A row I expect to be gone is still there. A switch may have partially failed and left the previous identity mounted. Check whether Identity Switching shows a rollback signal in the log. The session is recoverable; restart the app if needed.

Mount path is empty. The hive opened but the ExFat filesystem registration didn't complete. Restart the app.