diff options
| author | Christophe Besson <cbesson@gmail.com> | 2026-09-10 18:45:03 +0200 |
|---|---|---|
| committer | Christophe Besson <cbesson@gmail.com> | 2026-09-10 18:45:03 +0200 |
| commit | d82a0e7eec97844cd5eaf8aa49315146d5ed3d33 (patch) | |
| tree | fbc161e518f31274d2f86d87417b7393c4e40718 /docs/invite-pairing-v1.md | |
| parent | b88bb8a8bcdc27a092f902f7adbe90373f15732e (diff) | |
| download | meshbay-d82a0e7eec97844cd5eaf8aa49315146d5ed3d33.tar.gz | |
docs: point the superseded drafts at the design document
Twenty-three documents that MESHBAY_DESIGN.md absorbs gain a header saying so
and naming the sections their content went to. None is deleted: code comments,
tests and the documents themselves cite their sections and their labels, and
each records reasoning a synthesis compresses.
The header states the precedence, because two documents describing one system
will disagree eventually: where a draft disagrees with MESHBAY_DESIGN.md the
design document is right, and where either disagrees with the code the code is.
Seven status lines were corrected on the way through, all of them claiming less
than the truth. Videos, Music, Photos, partial-read hashing and account recovery
were headed "proposal, not implemented" months after they shipped; the desktop
client said "nothing here is implemented" with stages A through D running; draft
v6 still called itself the current specification.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01YVoHVCcfBqud6ZjG4db3y7
Diffstat (limited to 'docs/invite-pairing-v1.md')
| -rw-r--r-- | docs/invite-pairing-v1.md | 10 |
1 files changed, 10 insertions, 0 deletions
diff --git a/docs/invite-pairing-v1.md b/docs/invite-pairing-v1.md index ee4d257..8eb378f 100644 --- a/docs/invite-pairing-v1.md +++ b/docs/invite-pairing-v1.md @@ -1,5 +1,15 @@ # MeshBay — Invitation and Pairing (design) +> **Superseded by `MESHBAY_DESIGN.md`.** This was the admission and pairing design; its design +> content now lives in §3.4 and §3.5. +> +> It is kept because code comments, tests and other documents cite its +> sections and its labels, and because it records reasoning a synthesis +> compresses. **Where it disagrees with `MESHBAY_DESIGN.md`, the design +> document is right; where either disagrees with the code, the code is.** +> `MESHBAY_DESIGN.md` §16 maps every section reference here onto its +> replacement, and §13 defines every label. + > Status: **implemented and deployed** (2026-08-14). Written 2026-08-13 as a proposal; > §9bis records what shipped, what departed from the plan, and what a browser found > that the automated run could not. |