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/src/meshbay_node/roster.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'packages/meshbay-node/src/meshbay_node/roster.py') diff --git a/packages/meshbay-node/src/meshbay_node/roster.py b/packages/meshbay-node/src/meshbay_node/roster.py index 8360df3..7bc2067 100644 --- a/packages/meshbay-node/src/meshbay_node/roster.py +++ b/packages/meshbay-node/src/meshbay_node/roster.py @@ -61,7 +61,7 @@ DEFAULT_DEVICE_REQUEST_TTL = 3600 # What an invitation is bound to. An `account` code names its user_id when it is # issued; a `link` code names nobody until it is redeemed, because a link goes to -# someone who may not have an account yet (docs/invite-links.md). The kind is a +# someone who may not have an account yet (docs/MESHBAY_DESIGN.md §3.4). The kind is a # column rather than an empty user_id so that "bound to nobody" can never be # read as "bound to anybody" — the mistake AV1 records, once per codebase. KIND_ACCOUNT = "account" -- cgit v1.2.3