To-be 46: every value an approval sets is in the ask's note (ADR 0347, issue 383)
mesh/merge-gate 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 out of date: judged against trunk 471f99344b8d, the trunk is now 0f5aab10b4e0; judged again on a recheck or when it is merged
mesh/delivery superseded: a newer head of the same pull request

This commit is contained in:
jochen
2026-10-13 17:05:11 +02:00
parent 63fcb8e04b
commit 15dd960f95
@@ -4,6 +4,7 @@ status: in-progress
code: [mesh-controller, mesh-tools, mesh-sdk, mesh-catalog]
updated: 2026-10-13
decisions:
- "ADR 0347"
- "ADR 0345"
- "ADR 0332"
- "ADR 0308"
@@ -197,6 +198,12 @@ decision that needs the operator carries a brief its ask shows in place of its c
a summary and a point per key, at most three; an instructions proposal's text and a question's asker are their
Details.
*Amended 2026-10-13, ADR 0347 (issue 383):* **every value an approval sets is in the note.** A settings
proposal's Details list every key with its value, one line each and uncut — masked under the content rule, and
whole (`WholeDetails`) where the router shows the whole words — so the operator can always read exactly what
Approve sets; a point cut for the glance says so. A channel that bounds a message's length cuts the body first
and keeps the note whole, saying where it cut.
### Life
**open → answered | defaulted | expired | cancelled.**