The record for issue 383 (the issue tracker's): the operator could not read what they were approving on the phone — the values masked as ‹path› and ‹address›, the fingerprint and a how-to paragraph after them.
ADR 0277: two progressive insights, dated 2026-10-10. On a channel that proves who answers (verified-sender) the exact values are shown whole and only a value shaped like a secret is withheld; the masking stays for every channel that proves nothing and for every condition's words. The message is the change alone, then who proposed it and when; the fingerprint, where the whole is read and that the layer is set at once are the Details answer's. A row in the acceptance table names the checks (controller, router, telegram channel).
To-be 46: the content rule (§9) takes the amendment — an ask may carry its explanation whole, shown only on an ask's own message on a verified-sender kind that carries its answers, held to the secret rule alone — and exact-render says a channel may format the router's words and escapes their markup, never rewords them.
The four checks (cycle, records, index, words) pass. Code: mesh-sdk (branch fix/383-an-ask-says-what-a-proving-channel-shows-whole), mesh-catalog #178, mesh-controller #202.
The record for issue 383 (the issue tracker's): the operator could not read what they were approving on the phone — the values masked as ‹path› and ‹address›, the fingerprint and a how-to paragraph after them.
- **ADR 0277**: two progressive insights, dated 2026-10-10. On a channel that proves who answers (`verified-sender`) the exact values are shown whole and only a value shaped like a secret is withheld; the masking stays for every channel that proves nothing and for every condition's words. The message is the change alone, then who proposed it and when; the fingerprint, where the whole is read and that the layer is set at once are the Details answer's. A row in the acceptance table names the checks (controller, router, telegram channel).
- **To-be 46**: the content rule (§9) takes the amendment — an ask may carry its explanation whole, shown only on an ask's own message on a `verified-sender` kind that carries its answers, held to the secret rule alone — and `exact-render` says a channel may format the router's words and escapes their markup, never rewords them.
The four checks (cycle, records, index, words) pass. Code: mesh-sdk (branch fix/383-an-ask-says-what-a-proving-channel-shows-whole), mesh-catalog #178, mesh-controller #202.
The operator could not read what they were approving on the phone: the values were masked as
‹path› and ‹address›, and the fingerprint and a how-to paragraph made the message a wall of
text. On a channel that proves who answers the exact values are shown whole and only a value
shaped like a secret is withheld; the masking stays for conditions and for channels that prove
nothing; the fingerprint and the how-to are the Details answer's. To-be 46 takes the amendment
to the content rule and to exact-render.
The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.
<!-- mesh-delivery:view -->
**Delivery** `novox/hq@4507de7b651c` — **stopped** since 2026-10-13T14:37:24Z
**Delivery plan** — builds nothing: the change touches no module of the mesh's graph
**Transitions**
- 2026-10-10 13:51 (new) → proposed (announced): novox/hq#279's head announced
- 2026-10-10 13:52 proposed → checked (checked): the verdict names this commit
- 2026-10-10 13:52 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-13 14:37 ready → stopped (closed): the pull request closed unmerged
The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.
Rework needed before merge (triage, 2026-10-11): main deleted the ADR 0277 file this edits (#312), so it conflicts. The insight from issue 383 is not in the knowledge base (ADR 0277 there is version 4, imported without it): add it there as a progressive insight (knowledge-base.propose with insight), then resubmit only the to-be 46 change, citing "ADR 0277".
Rework needed before merge (triage, 2026-10-11): main deleted the ADR 0277 file this edits (#312), so it conflicts. The insight from issue 383 is not in the knowledge base (ADR 0277 there is version 4, imported without it): add it there as a progressive insight (`knowledge-base.propose` with `insight`), then resubmit only the to-be 46 change, citing "ADR 0277".
Replaced by #344. Decision records now live in the knowledge base (ADR 0290), so this PR's edit of the ADR 0277 file cannot land here; its rule (values whole on a proving channel) is clause 6 of ADR 0345, proposed in the knowledge base and marked needs-operator. #344 carries the to-be 46 amendments, updated for issue 639. Closing this one.
Replaced by #344. Decision records now live in the knowledge base (ADR 0290), so this PR's edit of the ADR 0277 file cannot land here; its rule (values whole on a proving channel) is clause 6 of ADR 0345, proposed in the knowledge base and marked needs-operator. #344 carries the to-be 46 amendments, updated for issue 639. Closing this one.
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.
The record for issue 383 (the issue tracker's): the operator could not read what they were approving on the phone — the values masked as ‹path› and ‹address›, the fingerprint and a how-to paragraph after them.
verified-sender) the exact values are shown whole and only a value shaped like a secret is withheld; the masking stays for every channel that proves nothing and for every condition's words. The message is the change alone, then who proposed it and when; the fingerprint, where the whole is read and that the layer is set at once are the Details answer's. A row in the acceptance table names the checks (controller, router, telegram channel).verified-senderkind that carries its answers, held to the secret rule alone — andexact-rendersays a channel may format the router's words and escapes their markup, never rewords them.The four checks (cycle, records, index, words) pass. Code: mesh-sdk (branch fix/383-an-ask-says-what-a-proving-channel-shows-whole), mesh-catalog #178, mesh-controller #202.
Delivery
novox/hq@4507de7b651c— stopped since 2026-10-13T14:37:24ZDelivery 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.Rework needed before merge (triage, 2026-10-11): main deleted the ADR 0277 file this edits (#312), so it conflicts. The insight from issue 383 is not in the knowledge base (ADR 0277 there is version 4, imported without it): add it there as a progressive insight (
knowledge-base.proposewithinsight), then resubmit only the to-be 46 change, citing "ADR 0277".Replaced by #344. Decision records now live in the knowledge base (ADR 0290), so this PR's edit of the ADR 0277 file cannot land here; its rule (values whole on a proving channel) is clause 6 of ADR 0345, proposed in the knowledge base and marked needs-operator. #344 carries the to-be 46 amendments, updated for issue 639. Closing this one.
Pull request closed