Issue 345, as the operator extended it on 2026-10-12: the betterbird module sets Betterbird up on every desktop node.
Adds to-be 56, the mail client, set up by the mesh, naming ADR 0316 (proposed in the knowledge base, marked needs-operator):
Betterbird ships as its upstream release, pinned by URL and sha256 and mirrored by the builder into the artifact store, unpacked at the community package's own path so the profile Betterbird opens does not change; the community package is removed on the operator's yes, per node, with Betterbird quit.
Owl is pinned by digest, mirrored into the artifact store (never a repository: its licence forbids copying), and installed by Betterbird's enterprise policy as force_installed with updates off.
Accounts are a trusted setting accounts without credentials, written under the mesh's own keys; the account list is written into, so Owl's own account survives. The work account is created in Owl's setup at the person's first sign-in; no password or token passes through the mesh.
Also a row in the to-be index. merge-check.sh passes locally (records, index, cycle, words).
Merge only once ADR 0316 is accepted (knowledge base review, then the operator's Approve).
Issue 345, as the operator extended it on 2026-10-12: the `betterbird` module sets Betterbird up on every desktop node.
Adds to-be 56, *the mail client, set up by the mesh*, naming ADR 0316 (proposed in the knowledge base, marked needs-operator):
- Betterbird ships as its upstream release, pinned by URL and sha256 and mirrored by the builder into the artifact store, unpacked at the community package's own path so the profile Betterbird opens does not change; the community package is removed on the operator's yes, per node, with Betterbird quit.
- Owl is pinned by digest, mirrored into the artifact store (never a repository: its licence forbids copying), and installed by Betterbird's enterprise policy as `force_installed` with updates off.
- Accounts are a trusted setting `accounts` without credentials, written under the mesh's own keys; the account list is written into, so Owl's own account survives. The work account is created in Owl's setup at the person's first sign-in; no password or token passes through the mesh.
Also a row in the to-be index. `merge-check.sh` passes locally (records, index, cycle, words).
Merge only once ADR 0316 is accepted (knowledge base review, then the operator's Approve).
Deliverynovox/hq@db92ca73ff4e — delivered since 2026-10-12T10:35:26Z
Delivery plan — builds nothing: the change touches no module of the mesh's graph
Transitions
2026-10-12 10:29 (new) → proposed (announced): novox/hq#322's head announced
2026-10-12 10:29 proposed → checked (checked): the verdict names this commit
2026-10-12 10:29 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-12 10:35 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-12 10:35 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@db92ca73ff4e` — **delivered** since 2026-10-12T10:35:26Z
**Delivery plan** — builds nothing: the change touches no module of the mesh's graph
**Transitions**
- 2026-10-12 10:29 (new) → proposed (announced): novox/hq#322's head announced
- 2026-10-12 10:29 proposed → checked (checked): the verdict names this commit
- 2026-10-12 10:29 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-12 10:35 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
- 2026-10-12 10:35 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`.
Checked clause by clause against ADR 0316 (knowledge-base, accepted, version 9, which includes the progressive insight recorded 2026-10-12 on Owl's licence reading). All 16 clauses are represented. In particular clause 6: the design's section 3 says Owl's xpi "is never committed to a repository, and a node never fetches it from the vendor" and is kept "in the mesh's private artifact store, used only on the operator's own machines," with the licence question on copying to the licensee's own machines named as "the operator's call, made on 2026-10-12" — matching the accepted record's current text exactly.
Frontmatter: layer: to-be, status: designed, code: [] (correct pre-handoff, per playbook 02), updated: 2026-10-12, decisions: ["ADR 0316"]. That citation form matches the other to-be docs that name a knowledge-base-only record (55, 47, 48, 45) now that decisions live in the knowledge base and not as files under 02-DECISIONS (ADR 0290) — confirmed: 02-DECISIONS/ in this tree holds only its README now.
Prose only: no manifest is pasted and there are no code fences; the "what the module places" table names paths and classes in prose. Public-repo rule: grepped the new file for absolute paths, node names (g14/ace/shanks/novox), domains/addresses and usernames — none found. The design correctly generalizes ADR 0316's /opt/betterbird and the AUR package name betterbird-bin into "the installation directory the community package uses," and drops the vendor's literal add-on id.
"How it is checked" is present and concrete (catalogue tests, module tests, builder tests, live per-node checks), satisfying AGENTS.md's rule that a stated rule says how it is checked.
Ran this repository's merge-check.sh on the PR head in a fresh worktree at db92ca73ff: records, index, cycle and words all passed (exit 0), matching the recorded mesh/repo-check "pass" status; mesh/merge-gate also reads pass (touches no module of the graph).
Non-blocking remark: knowledge-base.get still reports needs-operator: true on ADR 0316 even though both its original acceptance and its progressive insight show an operator Approve in the history (versions 6 and 9). That looks like stale metadata on the record, not a defect in this design.
Verdict: approve at db92ca73ff4ef506e7e877e112852df50c9f82fe
Checked clause by clause against ADR 0316 (knowledge-base, accepted, version 9, which includes the progressive insight recorded 2026-10-12 on Owl's licence reading). All 16 clauses are represented. In particular clause 6: the design's section 3 says Owl's xpi "is never committed to a repository, and a node never fetches it from the vendor" and is kept "in the mesh's private artifact store, used only on the operator's own machines," with the licence question on copying to the licensee's own machines named as "the operator's call, made on 2026-10-12" — matching the accepted record's current text exactly.
Frontmatter: layer: to-be, status: designed, code: [] (correct pre-handoff, per playbook 02), updated: 2026-10-12, decisions: ["ADR 0316"]. That citation form matches the other to-be docs that name a knowledge-base-only record (55, 47, 48, 45) now that decisions live in the knowledge base and not as files under 02-DECISIONS (ADR 0290) — confirmed: 02-DECISIONS/ in this tree holds only its README now.
Prose only: no manifest is pasted and there are no code fences; the "what the module places" table names paths and classes in prose. Public-repo rule: grepped the new file for absolute paths, node names (g14/ace/shanks/novox), domains/addresses and usernames — none found. The design correctly generalizes ADR 0316's /opt/betterbird and the AUR package name betterbird-bin into "the installation directory the community package uses," and drops the vendor's literal add-on id.
"How it is checked" is present and concrete (catalogue tests, module tests, builder tests, live per-node checks), satisfying AGENTS.md's rule that a stated rule says how it is checked.
Ran this repository's merge-check.sh on the PR head in a fresh worktree at db92ca73ff4ef506e7e877e112852df50c9f82fe: records, index, cycle and words all passed (exit 0), matching the recorded mesh/repo-check "pass" status; mesh/merge-gate also reads pass (touches no module of the graph).
Non-blocking remark: knowledge-base.get still reports needs-operator: true on ADR 0316 even though both its original acceptance and its progressive insight show an operator Approve in the history (versions 6 and 9). That looks like stale metadata on the record, not a defect in this design.
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.
Issue 345, as the operator extended it on 2026-10-12: the
betterbirdmodule sets Betterbird up on every desktop node.Adds to-be 56, the mail client, set up by the mesh, naming ADR 0316 (proposed in the knowledge base, marked needs-operator):
force_installedwith updates off.accountswithout credentials, written under the mesh's own keys; the account list is written into, so Owl's own account survives. The work account is created in Owl's setup at the person's first sign-in; no password or token passes through the mesh.Also a row in the to-be index.
merge-check.shpasses locally (records, index, cycle, words).Merge only once ADR 0316 is accepted (knowledge base review, then the operator's Approve).
Delivery
novox/hq@db92ca73ff4e— delivered since 2026-10-12T10:35:26ZDelivery 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
db92ca73ffChecked clause by clause against ADR 0316 (knowledge-base, accepted, version 9, which includes the progressive insight recorded 2026-10-12 on Owl's licence reading). All 16 clauses are represented. In particular clause 6: the design's section 3 says Owl's xpi "is never committed to a repository, and a node never fetches it from the vendor" and is kept "in the mesh's private artifact store, used only on the operator's own machines," with the licence question on copying to the licensee's own machines named as "the operator's call, made on 2026-10-12" — matching the accepted record's current text exactly.
Frontmatter: layer: to-be, status: designed, code: [] (correct pre-handoff, per playbook 02), updated: 2026-10-12, decisions: ["ADR 0316"]. That citation form matches the other to-be docs that name a knowledge-base-only record (55, 47, 48, 45) now that decisions live in the knowledge base and not as files under 02-DECISIONS (ADR 0290) — confirmed: 02-DECISIONS/ in this tree holds only its README now.
Prose only: no manifest is pasted and there are no code fences; the "what the module places" table names paths and classes in prose. Public-repo rule: grepped the new file for absolute paths, node names (g14/ace/shanks/novox), domains/addresses and usernames — none found. The design correctly generalizes ADR 0316's /opt/betterbird and the AUR package name betterbird-bin into "the installation directory the community package uses," and drops the vendor's literal add-on id.
"How it is checked" is present and concrete (catalogue tests, module tests, builder tests, live per-node checks), satisfying AGENTS.md's rule that a stated rule says how it is checked.
Ran this repository's merge-check.sh on the PR head in a fresh worktree at
db92ca73ff: records, index, cycle and words all passed (exit 0), matching the recorded mesh/repo-check "pass" status; mesh/merge-gate also reads pass (touches no module of the graph).Non-blocking remark: knowledge-base.get still reports needs-operator: true on ADR 0316 even though both its original acceptance and its progressive insight show an operator Approve in the history (versions 6 and 9). That looks like stale metadata on the record, not a defect in this design.