Admin mode Planned
The dashboard reads your hive today. Admin mode is the write side: control your devices and update the hive from the browser, not only from the command line. It is in progress, and this is what it will do.
Two jobs: control devices, update the hive
Everything the dashboard surfaces, you can already act on with the hv CLI. Admin mode brings those actions into the view you are already looking at, so the screen that shows you a problem is the screen that fixes it.
Control devices
From the Hive tab: admit a device waiting at the door, revoke one you no longer trust, and purge a device that is gone for good. The same roster where you watch sync status becomes the place you manage it, instead of copying device ids to a terminal.
Update the hive
From the Corpus tab: record a decision, retract a fact that no longer holds, re-confirm a contested one, and adjust tags. The record you are reading is the record you can change, with the same corroboration rules that govern a write from the CLI.
Off by default, and gated
Admin mode does not ship turned on. It is an opt-in you enable in your local config, the same place your node already keeps its settings, and it is tied to node identity so only a device you authorize can write. A laptop you trust can hold the controls; a phone you hand to someone for a look stays read-only. Leave it off and the dashboard behaves exactly as it does now.
Why it stays read-first
A shared memory is only useful if you can trust what is in it. Reading is safe to expose widely; writing is not, so the write side waits behind a deliberate switch and a known identity rather than riding along with every open tab. The default is to observe. Control is something you turn on, on purpose, where you mean to.