Replaces #279. #279 wrote a progressive insight into the ADR 0277 file in hq; decision records now live in the knowledge base (ADR 0290), so that part is ADR 0345 instead (proposed there, needs the operator), and this pull request keeps only the design.
What. To-be 46 names ADR 0345: §6 "What an ask carries" (headline, summary of two or three sentences, at most three points, Details; the router's note; one-line answered message; a decision's brief, a settings proposal's points, an instructions proposal's text and a question's asker in the Details); §7 exact-render amended (a channel formats, never rewords; taps compared with whitespace aside); §9 the content rule amended (an ask's values whole on a verified-sender kind, held to the secret rule alone).
Tested.merge-check.sh (records, index, cycle, words): all pass.
Code: mesh-sdk #25, the mesh-catalog and mesh-controller pull requests for issues 383 and 639.
Fixes issue 639 and issue 383 (the record's part).
Replaces #279. #279 wrote a progressive insight into the ADR 0277 file in hq; decision records now live in the knowledge base (ADR 0290), so that part is ADR 0345 instead (proposed there, needs the operator), and this pull request keeps only the design.
**What.** To-be 46 names ADR 0345: §6 "What an ask carries" (headline, summary of two or three sentences, at most three points, Details; the router's note; one-line answered message; a decision's brief, a settings proposal's points, an instructions proposal's text and a question's asker in the Details); §7 `exact-render` amended (a channel formats, never rewords; taps compared with whitespace aside); §9 the content rule amended (an ask's values whole on a `verified-sender` kind, held to the secret rule alone).
**Tested.** `merge-check.sh` (records, index, cycle, words): all pass.
Code: mesh-sdk #25, the mesh-catalog and mesh-controller pull requests for issues 383 and 639.
Fixes issue 639 and issue 383 (the record's part).
Deliverynovox/hq@de3b61217a4e — delivered since 2026-10-13T19:02:28Z
Delivery plan — builds nothing: the change touches no module of the mesh's graph
Transitions
2026-10-13 18:36 (new) → proposed (announced): novox/hq#344's head announced
2026-10-13 18:39 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
2026-10-13 18:39 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-13 19:02 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-13 19:02 published → delivered (done): nothing for a walk to move
The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.
<!-- mesh-delivery:view -->
**Delivery** `novox/hq@de3b61217a4e` — **delivered** since 2026-10-13T19:02:28Z
**Delivery plan** — builds nothing: the change touches no module of the mesh's graph
**Transitions**
- 2026-10-13 18:36 (new) → proposed (announced): novox/hq#344's head announced
- 2026-10-13 18:39 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
- 2026-10-13 18:39 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-13 19:02 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
- 2026-10-13 19:02 published → delivered (done): nothing for a walk to move
The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.
Verdict: approve at 63fcb8e04b54a08983a5db36b90fdf11c5b1eb48
Independent review (ADR 0345, issues 383 and 639).
To-be 46 now names ADR 0345 in decisions and moves updated to 2026-10-13. Its three dated amendments (the ask's words, exact-render with formatting, and the whole explanation on verified-sender) restate clauses 1 to 4 and 6 faithfully. The exact-render row now says how it is checked: "the words, formatting and runs of whitespace aside, equal the router's".
It names no node, address or path. records.py, index.py, cycle.py and words.py all exit 0 at this head.
A note for later: if the mesh-controller#304 finding (values of keys 3 and later never shown on a proving channel) leads to a change of clause 6, the sentence "a settings proposal is a summary and a point per key, at most three" will need the same amendment.
Statuses at this head: mesh/repo-check success ("head 63fcb8e04b54 merged into trunk 471f99344b — pass: its merge-check.sh passed"), mesh/merge-gate success ("… pass: the change touches no module of the mesh's graph"), mesh/delivery success ("ready: it delivers once merged"); no mesh/delivery-group.
Verdict: approve at 63fcb8e04b54a08983a5db36b90fdf11c5b1eb48
Independent review (ADR 0345, issues 383 and 639).
- To-be 46 now names ADR 0345 in `decisions` and moves `updated` to 2026-10-13. Its three dated amendments (the ask's words, `exact-render` with formatting, and the whole explanation on `verified-sender`) restate clauses 1 to 4 and 6 faithfully. The `exact-render` row now says how it is checked: "the words, formatting and runs of whitespace aside, equal the router's".
- It names no node, address or path. records.py, index.py, cycle.py and words.py all exit 0 at this head.
- A note for later: if the mesh-controller#304 finding (values of keys 3 and later never shown on a proving channel) leads to a change of clause 6, the sentence "a settings proposal is a summary and a point per key, at most three" will need the same amendment.
Statuses at this head: mesh/repo-check success ("head 63fcb8e04b54 merged into trunk 471f99344b8d — pass: its merge-check.sh passed"), mesh/merge-gate success ("… pass: the change touches no module of the mesh's graph"), mesh/delivery success ("ready: it delivers once merged"); no mesh/delivery-group.
New head 15dd960f9518: to-be 46 §6 gains the ADR 0347 amendment. A settings proposal's Details list every key with its value, uncut, masked or whole (WholeDetails), so Approve sets only what the operator can read. A channel cuts the body before the note. The frontmatter names ADR 0347.
New head 15dd960f9518: to-be 46 §6 gains the ADR 0347 amendment. A settings proposal's Details list every key with its value, uncut, masked or whole (`WholeDetails`), so Approve sets only what the operator can read. A channel cuts the body before the note. The frontmatter names ADR 0347.
Verdict: request changes at 15dd960f95184a89f95a89d54691c97961008c76
Independent review of the issue 383/639 group under ADR 0345 and ADR 0347.
Two sentences in the ADR 0347 amendment say more than the decision does. Both are in 03-DESIGN/01-to-be/46-the-conversation-with-the-operator.md:202-205.
"so the operator can always read exactly what Approve sets" overclaims. The knowledge base's own review of ADR 0347 (version 2) asked for this exact phrase to be narrowed. A value shaped like a secret is withheld under its key, and on the desk values are masked. Say instead that the operator reads every value Approve sets whole on a kind that proves who answers, except a secret's shape, which is withheld and named by its key, and masked elsewhere.
"cuts the body first and keeps the note whole" contradicts ADR 0347 §5. The note is cut last, when the title and note alone do not fit, and the cut is said. Say that.
The ADR 0345 amendments, the exact-render row and the content-rule amendment match ADR 0345 and the code. No "push" wording is added. The checks records.py, index.py, words.py (catalogue copy not compared, because MESH_CATALOG_DIR was unset) and cycle.py all pass at the head.
Statuses at this head: mesh/merge-gate pending, "out of date: judged against trunk 471f99344b, the trunk is now 0f5aab10b4e0; judged again on a recheck or when it is merged". mesh/repo-check pending with the same out-of-date text, so it is not mergeable now. mesh/delivery is pending ("checking"). There is no mesh/delivery-group status. Ask mesh-delivery.recheck after the fix.
Verdict: request changes at 15dd960f95184a89f95a89d54691c97961008c76
Independent review of the issue 383/639 group under ADR 0345 and ADR 0347.
Two sentences in the ADR 0347 amendment say more than the decision does. Both are in 03-DESIGN/01-to-be/46-the-conversation-with-the-operator.md:202-205.
- "so the operator can always read exactly what Approve sets" overclaims. The knowledge base's own review of ADR 0347 (version 2) asked for this exact phrase to be narrowed. A value shaped like a secret is withheld under its key, and on the desk values are masked. Say instead that the operator reads every value Approve sets whole on a kind that proves who answers, except a secret's shape, which is withheld and named by its key, and masked elsewhere.
- "cuts the body first and keeps the note whole" contradicts ADR 0347 §5. The note is cut last, when the title and note alone do not fit, and the cut is said. Say that.
The ADR 0345 amendments, the exact-render row and the content-rule amendment match ADR 0345 and the code. No "push" wording is added. The checks records.py, index.py, words.py (catalogue copy not compared, because MESH_CATALOG_DIR was unset) and cycle.py all pass at the head.
Statuses at this head: mesh/merge-gate pending, "out of date: judged against trunk 471f99344b8d, the trunk is now 0f5aab10b4e0; judged again on a recheck or when it is merged". mesh/repo-check pending with the same out-of-date text, so it is not mergeable now. mesh/delivery is pending ("checking"). There is no mesh/delivery-group status. Ask mesh-delivery.recheck after the fix.
The operator would not read the Telegram asks: the ADR 0343 ask was thirty plain lines, a settings
proposal a wall of masked values. The design takes ADR 0345: the asker's summary and points are the body,
everything else a note the channel shows apart, and an ask's values whole on a proving channel.
New head de3b61217a answers review 227, rebased on main (frontmatter conflict with ADR 0344 resolved by keeping both). The ADR 0347 amendment now follows ADR 0347's wording. Every value Approve sets is readable where the whole words are shown, except a value shaped like a secret, which is withheld and named by its key. A channel cuts the body first and cuts the note only when the title and note alone do not fit, saying each cut. The "always read exactly" and "keeps the note whole" phrasings are gone.
New head de3b61217a4e answers review 227, rebased on main (frontmatter conflict with ADR 0344 resolved by keeping both). The ADR 0347 amendment now follows ADR 0347's wording. Every value Approve sets is readable where the whole words are shown, except a value shaped like a secret, which is withheld and named by its key. A channel cuts the body first and cuts the note only when the title and note alone do not fit, saying each cut. The "always read exactly" and "keeps the note whole" phrasings are gone.
Re-review after review 227. The ADR 0347 amendment in 03-DESIGN/01-to-be/46-the-conversation-with-the-operator.md now follows the record:
every key is listed, never cut, and masked where the content rule requires;
WholeDetails is shown in the Details' place where the whole words are shown, held to the secret rule alone;
a secret's shape is withheld and named by its key;
a cut point says so and promises no more than the note holds;
the body is cut first, and the note only when the title and note alone do not fit, each cut said.
The overclaim and the "keeps the note whole" wording are gone. The checks records.py, index.py, words.py and cycle.py pass at the head.
Statuses at this head: mesh/merge-gate success ("head de3b61217a merged into trunk f7b4133e59 — pass: the change touches no module of the mesh's graph"), mesh/repo-check success ("… pass: its merge-check.sh passed"), mesh/delivery success ("ready: it delivers once merged"). This PR has no mesh/delivery-group status. Both checks are now judged against the current trunk; they are no longer out of date.
Verdict: approve at de3b61217a4e908e8c1ac7fa8ab7a4736c47da84
Re-review after review 227. The ADR 0347 amendment in 03-DESIGN/01-to-be/46-the-conversation-with-the-operator.md now follows the record:
- every key is listed, never cut, and masked where the content rule requires;
- WholeDetails is shown in the Details' place where the whole words are shown, held to the secret rule alone;
- a secret's shape is withheld and named by its key;
- a cut point says so and promises no more than the note holds;
- the body is cut first, and the note only when the title and note alone do not fit, each cut said.
The overclaim and the "keeps the note whole" wording are gone. The checks records.py, index.py, words.py and cycle.py pass at the head.
Statuses at this head: mesh/merge-gate success ("head de3b61217a4e merged into trunk f7b4133e598e — pass: the change touches no module of the mesh's graph"), mesh/repo-check success ("… pass: its merge-check.sh passed"), mesh/delivery success ("ready: it delivers once merged"). This PR has no mesh/delivery-group status. Both checks are now judged against the current trunk; they are no longer out of date.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Replaces #279. #279 wrote a progressive insight into the ADR 0277 file in hq; decision records now live in the knowledge base (ADR 0290), so that part is ADR 0345 instead (proposed there, needs the operator), and this pull request keeps only the design.
What. To-be 46 names ADR 0345: §6 "What an ask carries" (headline, summary of two or three sentences, at most three points, Details; the router's note; one-line answered message; a decision's brief, a settings proposal's points, an instructions proposal's text and a question's asker in the Details); §7
exact-renderamended (a channel formats, never rewords; taps compared with whitespace aside); §9 the content rule amended (an ask's values whole on averified-senderkind, held to the secret rule alone).Tested.
merge-check.sh(records, index, cycle, words): all pass.Code: mesh-sdk #25, the mesh-catalog and mesh-controller pull requests for issues 383 and 639.
Fixes issue 639 and issue 383 (the record's part).
Delivery
novox/hq@de3b61217a4e— delivered since 2026-10-13T19:02:28ZDelivery plan — builds nothing: the change touches no module of the mesh's graph
Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.Verdict: approve at 63fcb8e04b54a08983a5db36b90fdf11c5b1eb48
Independent review (ADR 0345, issues 383 and 639).
decisionsand movesupdatedto 2026-10-13. Its three dated amendments (the ask's words,exact-renderwith formatting, and the whole explanation onverified-sender) restate clauses 1 to 4 and 6 faithfully. Theexact-renderrow now says how it is checked: "the words, formatting and runs of whitespace aside, equal the router's".Statuses at this head: mesh/repo-check success ("head 63fcb8e04b54 merged into trunk
471f99344b— pass: its merge-check.sh passed"), mesh/merge-gate success ("… pass: the change touches no module of the mesh's graph"), mesh/delivery success ("ready: it delivers once merged"); no mesh/delivery-group.New head 15dd960f9518: to-be 46 §6 gains the ADR 0347 amendment. A settings proposal's Details list every key with its value, uncut, masked or whole (
WholeDetails), so Approve sets only what the operator can read. A channel cuts the body before the note. The frontmatter names ADR 0347.Verdict: request changes at 15dd960f95184a89f95a89d54691c97961008c76
Independent review of the issue 383/639 group under ADR 0345 and ADR 0347.
Two sentences in the ADR 0347 amendment say more than the decision does. Both are in 03-DESIGN/01-to-be/46-the-conversation-with-the-operator.md:202-205.
The ADR 0345 amendments, the exact-render row and the content-rule amendment match ADR 0345 and the code. No "push" wording is added. The checks records.py, index.py, words.py (catalogue copy not compared, because MESH_CATALOG_DIR was unset) and cycle.py all pass at the head.
Statuses at this head: mesh/merge-gate pending, "out of date: judged against trunk
471f99344b, the trunk is now 0f5aab10b4e0; judged again on a recheck or when it is merged". mesh/repo-check pending with the same out-of-date text, so it is not mergeable now. mesh/delivery is pending ("checking"). There is no mesh/delivery-group status. Ask mesh-delivery.recheck after the fix.15dd960f95tode3b61217aNew head
de3b61217aanswers review 227, rebased on main (frontmatter conflict with ADR 0344 resolved by keeping both). The ADR 0347 amendment now follows ADR 0347's wording. Every value Approve sets is readable where the whole words are shown, except a value shaped like a secret, which is withheld and named by its key. A channel cuts the body first and cuts the note only when the title and note alone do not fit, saying each cut. The "always read exactly" and "keeps the note whole" phrasings are gone.Verdict: approve at
de3b61217aRe-review after review 227. The ADR 0347 amendment in 03-DESIGN/01-to-be/46-the-conversation-with-the-operator.md now follows the record:
The overclaim and the "keeps the note whole" wording are gone. The checks records.py, index.py, words.py and cycle.py pass at the head.
Statuses at this head: mesh/merge-gate success ("head
de3b61217amerged into trunkf7b4133e59— pass: the change touches no module of the mesh's graph"), mesh/repo-check success ("… pass: its merge-check.sh passed"), mesh/delivery success ("ready: it delivers once merged"). This PR has no mesh/delivery-group status. Both checks are now judged against the current trunk; they are no longer out of date.