From f71218c1e114737791db98d3d55321577ee593e0 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Alejandro=20Guti=C3=A9rrez?= <35082514+alezmad@users.noreply.github.com> Date: Sat, 2 May 2026 02:06:29 +0100 Subject: [PATCH] =?UTF-8?q?docs(spec):=20v0.2.0=20=E2=80=94=20humans-in-me?= =?UTF-8?q?sh=20interface=20is=20REST,=20not=20browser=20WS?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Broker already plumbs peer_type. Real blocker is browser-side ed25519 hello-sig — sidestepped by exposing REST API for humans (and external scripts/bots), with web chat UI as a thin REST client using dashboard session auth. Collapses #2 (humans) and #3 (REST) into one deliverable. Co-Authored-By: Claude Opus 4.7 (1M context) --- .artifacts/specs/2026-05-02-v0.2.0-scope.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/.artifacts/specs/2026-05-02-v0.2.0-scope.md b/.artifacts/specs/2026-05-02-v0.2.0-scope.md index 9cfa9e1..56ea978 100644 --- a/.artifacts/specs/2026-05-02-v0.2.0-scope.md +++ b/.artifacts/specs/2026-05-02-v0.2.0-scope.md @@ -128,6 +128,8 @@ claudemesh send "#deploys" "rolling out 1.5.1" **Mental model:** a human is a peer with `peer_type: "human"` whose presence is durable (no session pubkey rotation; identity tied to an account). They join *topics*, not the whole mesh — so they only see relevant traffic. +> **Implementation update (2026-05-02):** `peer_type: "ai" | "human" | "connector"` is already plumbed end-to-end in the broker (hello envelope, ConnectedPeer, list_peers). What was missing wasn't broker support — it's the **interface** for humans, who don't have browser-side ed25519 to do hello-sig. Realistic path: **REST API is the human interface** (rolled into #3 below). The web chat panel becomes a thin client that posts/reads via REST using the dashboard user's session auth — not its own keypair. This collapses #2 and #3 into a single deliverable: REST → UI on top. + **Wire:** ```jsonc