aboutsummaryrefslogtreecommitdiffstats
path: root/docs/MESHBAY_DESIGN.md
diff options
context:
space:
mode:
Diffstat (limited to 'docs/MESHBAY_DESIGN.md')
-rw-r--r--docs/MESHBAY_DESIGN.md6
1 files changed, 5 insertions, 1 deletions
diff --git a/docs/MESHBAY_DESIGN.md b/docs/MESHBAY_DESIGN.md
index d051d87..2cfe7a4 100644
--- a/docs/MESHBAY_DESIGN.md
+++ b/docs/MESHBAY_DESIGN.md
@@ -33,6 +33,7 @@
| `QUICKSTART.md` | one machine to a working group, for somebody who has installed nothing |
| `USERGUIDE.md` | using a group and running a node, for the person who does either |
| `MESHBAY_NODE_PROTOCOL.md` | the MNP wire format, message by message |
+| `MESHBAY_HTTP_API.md` | every route of the hub and of the node's control API, generated from the code |
| `transfers-v1.md` | the transfer system's failure-mode analysis, kept because a synthesis cannot carry "every way a slot can be lost" |
| `playlists.md` | the playlist design and its interface in full, with what building it corrected (§9.10) |
| `cast-smart-tv.md` | the DLNA/UPnP device backend — designed, not built (§11.4) |
@@ -1888,7 +1889,8 @@ is not authentication: any local process can reach it, as can a page in the
operator's browser via DNS rebinding — and this API re-initialises group keys,
issues invitations and reads the audit log. There is no server-rendered dashboard;
the desktop client's Node page and the CLI are the two consumers, and each
-operation endpoint is one `_op(...)` line onto `ops` (§5.4).
+operation endpoint is one `_op(...)` line onto `ops` (§5.4). Its routes are listed
+in `MESHBAY_HTTP_API.md`.
**The node's own controls are not on MNP.** Its status — which lists every group
on the machine with each root's absolute path — settings, roster, denylist and
@@ -1950,6 +1952,8 @@ an operator-signed op.
## 7. The hub
+Its routes are listed in `MESHBAY_HTTP_API.md`.
+
### 7.1 Role — chosen, not minimal
Hub minimisation was considered and **deferred, and may be dropped** (decision D4).