From 5bce0acad6d10f9b952874f1359406b4eae3a8f9 Mon Sep 17 00:00:00 2001 From: Christophe Besson Date: Wed, 23 Sep 2026 17:46:48 +0200 Subject: docs: drop the invitation-link plan from the tree The plan was a working document; what it decided lives in MESHBAY_DESIGN.md and MESHBAY_NODE_PROTOCOL.md. Code and tests now cite those instead. Co-Authored-By: Claude Opus 5.5 --- packages/meshbay-node/tests/test_link_invites.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'packages/meshbay-node/tests/test_link_invites.py') diff --git a/packages/meshbay-node/tests/test_link_invites.py b/packages/meshbay-node/tests/test_link_invites.py index f5081d2..10f9ca8 100644 --- a/packages/meshbay-node/tests/test_link_invites.py +++ b/packages/meshbay-node/tests/test_link_invites.py @@ -4,7 +4,7 @@ Invitation links: a code bound to no account until somebody redeems it. A link is sent to someone who may not have an account yet, so its code cannot name one. That makes it a bearer code at the node — the hub's ticket, bound to a verified address, is what decides who can reach the node at all -(docs/invite-links.md §3). Everything here is a way a bearer code could be made +(docs/MESHBAY_DESIGN.md §3.4). Everything here is a way a bearer code could be made to mean more than "one new member of this group, once", or a way an unbound row could leak into the code paths written for bound ones. The second family is the one to watch: `user_id = ''` must never read as "anyone" (AV1). -- cgit v1.2.3