The records pointed at branches that no longer exist, and two fixes had no sequel #195

Merged
jschoubben merged 1 commits from issue/pointers-that-resolve-to-nothing into main 2026-09-29 22:29:03 +00:00
Owner

An audit of what last night's work actually left in the records, prompted by being asked whether it was documented. Six gaps, all real:

  • fixed-by: in 152, 155 and 156 named the branch that fixed them, and a branch is deleted when it merges. They name commits and PRs now.
  • 152 named the repository by its local directory (mesh-control) rather than the repository (mesh-controller).
  • 146 did not say that one of its fixes crash-looped the control plane — the record somebody arrives at to learn why the delivery subject carries the stream said nothing about the sequel, or that the raise path was the only one exercised.
  • 151 did not say that 152 removed the false reasons its roster moved, nor that it stays open for the real ones.
  • Playbook 03 said "take the next free number" with no mention of open pull requests, while a check now enforces uniqueness. It also now says fixed-by names a commit, not a branch.
  • ADR 0080 enumerates what cycle.py enforces and named four things; it enforces five. A dated progressive insight names the fifth — the decision stands, the list had gone stale.

Checks: records, index, cycle all pass.

An audit of what last night's work actually left in the records, prompted by being asked whether it was documented. Six gaps, all real: - `fixed-by:` in 152, 155 and 156 named the **branch** that fixed them, and a branch is deleted when it merges. They name commits and PRs now. - 152 named the repository by its local directory (`mesh-control`) rather than the repository (`mesh-controller`). - **146 did not say that one of its fixes crash-looped the control plane** — the record somebody arrives at to learn why the delivery subject carries the stream said nothing about the sequel, or that the raise path was the only one exercised. - **151 did not say that 152 removed the false reasons its roster moved**, nor that it stays open for the real ones. - Playbook 03 said "take the next free number" with no mention of open pull requests, while a check now enforces uniqueness. It also now says `fixed-by` names a commit, not a branch. - ADR 0080 enumerates what `cycle.py` enforces and named four things; it enforces five. A dated progressive insight names the fifth — the decision stands, the list had gone stale. Checks: records, index, cycle all pass.
jschoubben added 1 commit 2026-09-29 22:28:51 +00:00
Three issues named the branch that fixed them, and a branch is deleted
when it merges — so every `fixed-by:` was a pointer that resolved to
nothing by the time anyone followed it. They name commits and pull
requests now, and playbook 03 says to.

Two records were missing the thing a reader arrives for. 146 did not say
that one of its fixes crash-looped the control plane on a running mesh,
which is the whole reason the delivery subject carries the stream and the
raise path was the only one exercised. 151 did not say that 152 removed
the false reasons its roster moved, or that it stays open for the real
ones.

ADR 0080 enumerates what cycle.py enforces and named four things; it
enforces five. A progressive insight names the fifth — the decision
stands, the list had gone stale. The checks README and playbook 03 gained
the same rule, and 155 points at all three.
jschoubben merged commit 5a3dee9e9e into main 2026-09-29 22:29:03 +00:00
jschoubben deleted branch issue/pointers-that-resolve-to-nothing 2026-09-29 22:29:03 +00:00
Sign in to join this conversation.
No Reviewers
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: novox/hq#195