aboutsummaryrefslogtreecommitdiffstats
path: root/docs
diff options
context:
space:
mode:
Diffstat (limited to 'docs')
-rw-r--r--docs/meshbay-draft-v5.md18
1 files changed, 17 insertions, 1 deletions
diff --git a/docs/meshbay-draft-v5.md b/docs/meshbay-draft-v5.md
index 9e1ddb3..8035824 100644
--- a/docs/meshbay-draft-v5.md
+++ b/docs/meshbay-draft-v5.md
@@ -203,7 +203,23 @@ ordering enforced, size capped. Previously uploads landed in the shared root und
client-chosen name and overwrote anything there — which also defeated deletion
authorization, since overwriting a file made the attacker its recorded uploader.
-### 5.3 Local admin UI
+### 5.3 Operator interface
+
+Two personas, and they need different tools:
+
+| Operator | Reaches the node via |
+|---|---|
+| Desktop | the local admin UI in their own browser |
+| **Headless / SSH** | the CLI — `meshbay-node status`, `ui`, `gek-init` |
+
+The CLI is the primary interface for servers, which is the normal deployment.
+`status` deliberately reads the keystore and config directly so it works while
+the daemon is stopped — the state an operator is most often in, since the daemon
+will not stay up before its key is linked or before a group exists. Anything the
+UI can do should eventually have a CLI equivalent (Phase 14); until then a
+headless operator still needs a browser to invite members or delete files.
+
+### 5.4 Local admin UI
Loopback plus a **per-run session token** (`?t=` or `X-MeshBay-Token`), printed at
startup. "Localhost only" is not authentication: any local process can reach it, as can