Issue 270: Phase 1 watches signals that come later; to-be 45 in progress #130

2026-10-06T08:22:57Z

mesh-admin commented

2026-10-06 08:22:57 +00:00

Building Phase 1 of to-be 45 (mesh-controller#79, mesh-host#33, mesh-tools#16):

to-be 45 flipped to status: in-progress, code: its five repositories (playbook 04).
Issue 270: S12, D5 (lease, Phase 2), S14 (facts, Phase 5) cannot be built in Phase 1; S13 cannot name the writer before epochs; S9 hears other principals' slow consumers / refused subjects only with a system account. Records the decisions the build made that §1–§4 do not state (history bucket, event shape and doctor-heartbeat, key tokens, probe DW, mesh-named consumer deletions, provisional bounds, the orphaned provider_standing table) and asks for the amendment.

records.py, index.py, cycle.py pass.

Building Phase 1 of to-be 45 (mesh-controller#79, mesh-host#33, mesh-tools#16): - to-be 45 flipped to `status: in-progress`, `code:` its five repositories (playbook 04). - Issue 270: S12, D5 (lease, Phase 2), S14 (facts, Phase 5) cannot be built in Phase 1; S13 cannot name the writer before epochs; S9 hears other principals' slow consumers / refused subjects only with a system account. Records the decisions the build made that §1–§4 do not state (history bucket, event shape and `doctor-heartbeat`, key tokens, probe DW, mesh-named consumer deletions, provisional bounds, the orphaned `provider_standing` table) and asks for the amendment. records.py, index.py, cycle.py pass.

mesh-admin added 1 commit 2026-10-06 08:22:57 +00:00

Issue 270: Phase 1 watches signals that come later; to-be 45 in progress fc9b252949

Building Phase 1 of to-be 45 found four of its rows depend on later phases
and S9 hears only the controller's own connection; the decisions the build
made that the design does not state are recorded for an amendment.

mesh-admin merged commit 358cce00a7 into main

2026-10-06 08:37:47 +00:00

mesh-admin deleted branch issues/270-phase-1-watchdogs-whose-signals-come-later

2026-10-06 08:37:48 +00:00

mesh-admin commented

2026-10-06 23:07:06 +00:00

Delivery novox/hq@358cce00a7e4 — held since 2026-10-06T23:05:28Z

Held for a person: merged without a passing check: only a person decides that it goes on — mesh-delivery.release with why lets it go on.

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

Transitions

2026-10-06 23:05 (new) → proposed (announced): novox/hq#130 merged; its head was not heard by this owner, so it is made from the forge's word
2026-10-06 23:05 proposed → held (merged-unchecked): merged without a passing check — a verdict known with it is taken first: only a person decides that it goes on

The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.

**Delivery** `novox/hq@358cce00a7e4` — **held** since 2026-10-06T23:05:28Z Held for a person: merged without a passing check: only a person decides that it goes on — `mesh-delivery.release` with why lets it go on. **Delivery plan** — builds nothing: the change touches no module of the mesh's graph **Transitions** - 2026-10-06 23:05 (new) → proposed (announced): novox/hq#130 merged; its head was not heard by this owner, so it is made from the forge's word - 2026-10-06 23:05 proposed → held (merged-unchecked): merged without a passing check — a verdict known with it is taken first: only a person decides that it goes on The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/hq#130