knowledge-base.progress: how far a design, milestone, issue or record has come, in one call (issue 1947) #504

2026-10-26T16:28:38Z

mesh-tools commented

2026-10-26 16:28:38 +00:00

Issue 1947 (the operator, 2026-10-26: one generic progress call for every level, minimal for every five minutes, detailed for about every thirty). One delivery group with novox/hq feat/1947-progress.

mesh-issues: issue-tracker.list rows say moved (the issue's last change) and list takes linked (such as decision:0493).
mesh-knowledge: the seat verb knowledge-base.progress {of: mesh | design N | milestone N/id | issue N | ADR N | research N, detail: minimal|detailed, bound}. It reads designs through the records (cached by hq's commit) and asks issue-tracker and mesh-delivery over the bus (2 calls for a minimal answer on a cache hit). Milestones are read from the design's Milestones table until issue 1781's milestone records are delivered. Done = resolved and delivered (or nothing to deliver); held/failed/stopped = stuck; merged not delivered = moving; nothing heard = waiting. A failed tracker, deliveries or groups call is an error; a failed show/get, unanswered rows or cut linked issues are warnings. The answer is bounded (minimal within 4 KiB).
Tests: 6 unit functions, 1 integration test (TestProgressOverTheBus, the module whole on a real bus).

Review notes left as notes on 1947: an over-bound answer cuts warnings from the end, so call-failure warnings go first (the answer says how many were cut); detailed reads show for up to 30 open deliveries mesh-wide.

ADR 0290 v8 (insight accepted): progress joins the seat's verbs when this is delivered.

Try try-1793030600346972276 passed (unit 2051, integration 2072).

Reviewed-by: review-progress@shanks at 87fe2c45cf

Issue 1947 (the operator, 2026-10-26: one generic progress call for every level, minimal for every five minutes, detailed for about every thirty). One delivery group with novox/hq feat/1947-progress. - mesh-issues: `issue-tracker.list` rows say `moved` (the issue's last change) and `list` takes `linked` (such as decision:0493). - mesh-knowledge: the seat verb `knowledge-base.progress` {of: mesh | design N | milestone N/id | issue N | ADR N | research N, detail: minimal|detailed, bound}. It reads designs through the records (cached by hq's commit) and asks issue-tracker and mesh-delivery over the bus (2 calls for a minimal answer on a cache hit). Milestones are read from the design's Milestones table until issue 1781's milestone records are delivered. Done = resolved and delivered (or nothing to deliver); held/failed/stopped = stuck; merged not delivered = moving; nothing heard = waiting. A failed tracker, deliveries or groups call is an error; a failed show/get, unanswered rows or cut linked issues are warnings. The answer is bounded (minimal within 4 KiB). - Tests: 6 unit functions, 1 integration test (TestProgressOverTheBus, the module whole on a real bus). Review notes left as notes on 1947: an over-bound answer cuts warnings from the end, so call-failure warnings go first (the answer says how many were cut); detailed reads show for up to 30 open deliveries mesh-wide. ADR 0290 v8 (insight accepted): `progress` joins the seat's verbs when this is delivered. Try try-1793030600346972276 passed (unit 2051, integration 2072). Reviewed-by: review-progress@shanks at 87fe2c45cfedc01096c6da9913c0af965692dd75

mesh-tools added 4 commits 2026-10-26 16:28:38 +00:00

Issue tracker: list rows say when each issue last moved, and list takes linked (issue 1947) 5e516317e9

The knowledge base's progress verb reads a milestone's issues in one call and must say
when each last moved, and the issues linked to a record or a design; neither was
readable without one get per issue.

Knowledge base: progress says how far a design, milestone, issue or record has come (issue 1947) 8da33e43d4

A lead's five-minute report and 'is design 47 nearing its end' were joined by hand from
the design file, the tracker and the deliveries. One verb now works the state out
(ADR 0424 §1), minimal for every five minutes, detailed for the report's tree.
Milestones are read from the design's table until the tracker's milestone records
(issue 1781) are delivered.

Knowledge base: progress is proven over the bus with the module started whole (issue 1947) 5baf8ad1d7

The verb asks three seats and the records module; only a run over a real bus shows its
grants and subjects line up with what the manifest invokes.

Knowledge base: progress counts an issue done only once its fix is delivered, and says every gap (issue 1947, review round 1)

mesh/delivery merged: source.main moved to novox/mesh-catalog@26908a89506f

Details

mesh/delivery-group group feat/1947-progress merged: every member is merged

Details

mesh/check pass 87fe2c45cfed on 26908a89506f | carried from 27a7757b970e, hq 3a5c4c7c4d9c | unit 2091 run, 2327 kept, 6 skipped | integration 2112 run…

87fe2c45cf

A resolved issue whose delivery is held or failed is stuck, one merged and not delivered
is moving; a row the tracker did not answer, an answer that does not read and linked
issues cut by the list's limit are said as warnings instead of passing silently.

mesh-tools commented

2026-10-26 16:28:45 +00:00

Delivery novox/mesh-catalog@87fe2c45cfed — merged since 2026-10-26T16:42:31Z

Source — source.main moved to novox/mesh-catalog@26908a8950. Whether it reached the machines is mesh-delivery-view's, derived from source.main, the wants and the haves.

Group feat/1947-progress: novox/hq@a6e27687db, novox/mesh-catalog@87fe2c45cf

composed together: pass — the checker's verdict at the members' heads (b960c0fff34e)

Transitions

2026-10-26 16:28 (new) → proposed (announced): novox/mesh-catalog#504's head announced
2026-10-26 16:28 proposed → ready (accepted): a verdict names this commit and the trunk's head as its trunk commit, the gate passed or warned, and the repository's own check did not fail; or the check gates no merge (check-gates-merge false)
2026-10-26 16:42 ready → merged (merged): on the trunk its modules follow: merged there

The commit's note under refs/notes/mesh-plan keeps every transition of this change up to its merge: git log --notes=mesh-plan.

**Delivery** `novox/mesh-catalog@87fe2c45cfed` — **merged** since 2026-10-26T16:42:31Z **Source** — source.main moved to novox/mesh-catalog@26908a89506f. Whether it reached the machines is `mesh-delivery-view`'s, derived from `source.main`, the wants and the haves. **Group** `feat/1947-progress`: novox/hq@a6e27687db42, novox/mesh-catalog@87fe2c45cfed - composed together: pass — the checker's verdict at the members' heads (b960c0fff34e) **Transitions** - 2026-10-26 16:28 (new) → proposed (announced): novox/mesh-catalog#504's head announced - 2026-10-26 16:28 proposed → ready (accepted): a verdict names this commit and the trunk's head as its trunk commit, the gate passed or warned, and the repository's own check did not fail; or the check gates no merge (check-gates-merge false) - 2026-10-26 16:42 ready → merged (merged): on the trunk its modules follow: merged there The commit's note under `refs/notes/mesh-plan` keeps every transition of this change up to its merge: `git log --notes=mesh-plan`.

mesh-tools merged commit 26908a8950 into main

2026-10-26 16:42:30 +00:00

mesh-tools deleted branch feat/1947-progress

2026-10-26 16:42:30 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-catalog#504