go/asks: a message carries its note apart, and an explanation is held to a glance (issues 383 and 639) #25

Merged

mesh-admin merged 3 commits from fix/639-an-ask-reads-at-a-glance into main

2026-10-13 19:02:17 +00:00

Author	SHA1	Message	Date
jochen	5933eb757d	go/asks: whole details never digest as another ask's Whole and Details (the review of #25 ) mesh/merge-gate head 5933eb757d44 merged into trunk a0fc82fdcd7c — pass, with a note: builds mesh-sdk (+40 dependent(s)) → ace, g14, novox, shanks; no bus … Details mesh/repo-check head 5933eb757d44 merged into trunk a0fc82fdcd7c — pass: its merge-check.sh passed, each part in its toolchain: merge-check.sh (typescript)… Details mesh/delivery delivered Details WholeDetails was written after a tag, so an ask with only whole details "+ x: 1" encoded as one whose Whole was "whole-details" and Details "+ x: 1". Whole and Details are now written whenever whole details are given, then the whole details, untagged: the number of trailing values tells the three shapes apart, and an ask without whole details digests as before. The note's comment says what ADR 0347 §5 holds of cuts.	2026-10-13 20:29:24 +02:00
jochen	f4745447ba	go/asks: an ask may carry its Details whole, for a channel that proves who answers (hq issue 383) mesh/merge-gate head f4745447ba6d merged into trunk a0fc82fdcd7c — pass, with a note: builds mesh-sdk (+40 dependent(s)) → ace, g14, novox, shanks; no bus … Details mesh/repo-check head f4745447ba6d merged into trunk a0fc82fdcd7c — pass: its merge-check.sh passed, each part in its toolchain: merge-check.sh (typescript)… Details mesh/delivery superseded: a newer head of the same pull request Details The review of mesh-controller #304: a settings proposal with more than three keys showed only the names of the rest, and its Details could carry no value under the content rule, so Approve bound values the operator never saw. WholeDetails carries every value whole for the note on a proving channel, held to the secret rule alone, as Whole is; it is digested only when given.	2026-10-13 16:56:22 +02:00
jochen	9588871d66	go/asks: a message carries its note apart, and an explanation is held to a glance (hq issues 639 and 383) mesh/merge-gate head 9588871d6629 merged into trunk a0fc82fdcd7c — pass, with a note: builds mesh-sdk (+40 dependent(s)) → ace, g14, novox, shanks; no bus … Details mesh/repo-check head 9588871d6629 merged into trunk a0fc82fdcd7c — pass: its merge-check.sh passed, each part in its toolchain: merge-check.sh (typescript)… Details mesh/delivery superseded: a newer head of the same pull request Details The operator will not read a Telegram ask of thirty plain lines. The secondary words (who asked, what each answer does, the expiry, the fingerprint, how to read it whole) travel as Message.Note, so a channel can show them small or collapsed; an ask's Details go there. Glance names the bound of an explanation: a summary of at most 300 characters, then at most three points of at most 160.	2026-10-13 16:15:20 +02:00