Design 47: R3a's issues, the two controller fixes it needed first, and R3c's open question on Go-compiling images #431

Merged

mesh-tools merged 1 commits from docs/design-47-r3a-issues into main 2026-10-19 09:13:16 +00:00

Conversation 1 Commits 1 Files Changed 1

+2 -2

mesh-tools commented 2026-10-19 09:11:01 +00:00

Member

Copy Link

Copy Source

Design 47's milestone table, written back from R3a's prepare step and build (playbook 07, the design's state is written back):

• R3a: issues 1200 (source revision, candidates, modules, forge messages), 1201 (merges, asks, owed acts, answers), 1202 (a condition on its one subject), 1203 (the source fingerprint, proven against three fingerprints the live builder recorded); ahead of it in mesh-controller, 1204 and 1208 (builds says each build's source fingerprint), without which no recorded fingerprint could be read.
• R3c: its prepare step first settles issue 1209: an image that compiles a Go program enters the fingerprint by the hash of its build source, which git trees alone do not give, so ADR 0437 clause 5's 'root tree' is a fact to correct and the indexer needs a way.

A design edit of two lines: no reviewer (playbook 08 step 4); the operator's Approve of this merge is its review. hq's merge-check.sh passed locally.

Reviewed-by: none (design edit of two lines, playbook 08 step 4) at 95bf5cbf20

Design 47's milestone table, written back from R3a's prepare step and build (playbook 07, the design's state is written back): - R3a: issues 1200 (source revision, candidates, modules, forge messages), 1201 (merges, asks, owed acts, answers), 1202 (a condition on its one subject), 1203 (the source fingerprint, proven against three fingerprints the live builder recorded); ahead of it in mesh-controller, 1204 and 1208 (builds says each build's source fingerprint), without which no recorded fingerprint could be read. - R3c: its prepare step first settles issue 1209: an image that compiles a Go program enters the fingerprint by the hash of its build source, which git trees alone do not give, so ADR 0437 clause 5's 'root tree' is a fact to correct and the indexer needs a way. A design edit of two lines: no reviewer (playbook 08 step 4); the operator's Approve of this merge is its review. hq's merge-check.sh passed locally. Reviewed-by: none (design edit of two lines, playbook 08 step 4) at 95bf5cbf2089b7a47005c94b1e9c637dc292c45d

mesh-tools added 1 commit 2026-10-19 09:11:02 +00:00

Design 47: R3a's issues, the two controller fixes it needed first, and R3c's open question on Go-compiling images (issues 1200-1204, 1208, 1209) 95bf5cbf20

mesh-tools commented 2026-10-19 09:11:09 +00:00

Author

Member

Copy Link

Copy Source

Delivery novox/hq@95bf5cbf2089 — delivered since 2026-10-19T09:13:17Z

Delivery plan — builds nothing: the change touches no module of the mesh's graph

Transitions

• 2026-10-19 09:11 (new) → proposed (announced): novox/hq#431's head announced
• 2026-10-19 09:12 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
• 2026-10-19 09:12 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
• 2026-10-19 09:13 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
• 2026-10-19 09:13 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@95bf5cbf2089` — **delivered** since 2026-10-19T09:13:17Z **Delivery plan** — builds nothing: the change touches no module of the mesh's graph **Transitions** - 2026-10-19 09:11 (new) → proposed (announced): novox/hq#431's head announced - 2026-10-19 09:12 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit - 2026-10-19 09:12 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-19 09:13 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-19 09:13 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-tools merged commit 59c6954b0c into main 2026-10-19 09:13:16 +00:00

mesh-tools deleted branch docs/design-47-r3a-issues 2026-10-19 09:13:17 +00:00

Sign in to join this conversation.

Reviewers

No Reviewers

Labels

Clear labels

mesh/ready

Reviewed and ready: mesh-delivery merges at the marked head once its checks pass (hq ADR 0364)

No labels

Milestone

No items

No Milestone

Assignees

Clear assignees

agent-ace agent-g14 agent-novox agent-shanks jschoubben mesh-tools miel.truyen nox-agent

No Assignees

1 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/hq#431