The knowledge base's close verb: a research effort graduates, is abandoned or parked as an idea, judged only on its closing (issue 784, ADR 0630) #610

2026-11-04T14:16:53Z

mesh-tools commented

2026-11-04 14:16:53 +00:00

Issue 784, ADR 0630 (accepted).

Why: closing a research effort meant proposing it again whole, and the review judged weeks-old text afresh: three groomings met it on 2026-11-04 (1 of 12 efforts parked as ideas got through). The thorough fix issue 784's note names.

§1: close (number, to graduated|abandoned|idea, links, note, why; the proven caller is the author) writes one version: the served text unchanged, the status, the links, one section Graduated / Abandoned / Parked as an idea.
§2: one-record rules run on the added links and note only; old-text findings come back as notes; the background review uses a closing-only question. A graduated close needs a became over all the effort's links, each to an accepted record.
§3: a version left waiting (whoever its author) and its operator ask end; the ask is cancelled on the router's cancel subject, as withdraw does; the answer names both.
§4: active -> graduated|abandoned|idea, idea -> abandoned; anything else refused naming the allowed moves. The record size limit is checked as in propose.
§5 (the 21 efforts left of ADR 0629 §5) is closed with it after the delivery, read back on issue 1970.

Tests: close_test.go, four tests; the reviewer showed each fails without its change. Module well under 500 unit tests, no integration test added. go vet, vet -tags integration and go test pass locally (21 s).

Quick or thorough: quick = answer each record's findings by hand (~20 records, rounds each, again at every grooming); thorough (chosen) = this verb.

Reviewed-by: mesh-code-reviewer@shanks at e9ba05bd9a

https://claude.ai/code/session_01JG73KG7AfSdh6FP8VrBqCn

Issue 784, ADR 0630 (accepted). Why: closing a research effort meant proposing it again whole, and the review judged weeks-old text afresh: three groomings met it on 2026-11-04 (1 of 12 efforts parked as ideas got through). The thorough fix issue 784's note names. - §1: `close` (number, to graduated|abandoned|idea, links, note, why; the proven caller is the author) writes one version: the served text unchanged, the status, the links, one section Graduated / Abandoned / Parked as an idea. - §2: one-record rules run on the added links and note only; old-text findings come back as notes; the background review uses a closing-only question. A graduated close needs a became over all the effort's links, each to an accepted record. - §3: a version left waiting (whoever its author) and its operator ask end; the ask is cancelled on the router's cancel subject, as withdraw does; the answer names both. - §4: active -> graduated|abandoned|idea, idea -> abandoned; anything else refused naming the allowed moves. The record size limit is checked as in propose. - §5 (the 21 efforts left of ADR 0629 §5) is closed with it after the delivery, read back on issue 1970. Tests: close_test.go, four tests; the reviewer showed each fails without its change. Module well under 500 unit tests, no integration test added. go vet, vet -tags integration and go test pass locally (21 s). Quick or thorough: quick = answer each record's findings by hand (~20 records, rounds each, again at every grooming); thorough (chosen) = this verb. Reviewed-by: mesh-code-reviewer@shanks at e9ba05bd9a3cb6d0bd216e968fafc0cc0a826afd https://claude.ai/code/session_01JG73KG7AfSdh6FP8VrBqCn

mesh-tools added 2 commits 2026-11-04 14:16:53 +00:00

The knowledge base's close verb closes or parks a research effort, judged only on its closing (issue 784, ADR 0630) 8f5667cca5

Claude-Session: https://claude.ai/code/session_01JG73KG7AfSdh6FP8VrBqCn

close: read the became links the effort already carries, check the record size, drop empty table cases (issue 784, ADR 0630)

mesh/check being carried to e9ba05bd9a3c on d2f326dff40e | from 79c2fc7fe1d5

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

Details

e9ba05bd9a

Claude-Session: https://claude.ai/code/session_01JG73KG7AfSdh6FP8VrBqCn

mesh-tools commented

2026-11-04 14:16:55 +00:00

Delivery novox/mesh-catalog@e9ba05bd9a3c — merged since 2026-11-04T14:44:00Z

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

Transitions

2026-11-04 14:16 (new) → proposed (announced): novox/mesh-catalog#610's head announced
2026-11-04 14:16 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-11-04 14:44 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@e9ba05bd9a3c` — **merged** since 2026-11-04T14:44:00Z **Source** — source.main moved to novox/mesh-catalog@d2f326dff40e. Whether it reached the machines is `mesh-delivery-view`'s, derived from `source.main`, the wants and the haves. **Transitions** - 2026-11-04 14:16 (new) → proposed (announced): novox/mesh-catalog#610's head announced - 2026-11-04 14:16 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-11-04 14:44 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 d2f326dff4 into main

2026-11-04 14:43:58 +00:00

mesh-tools deleted branch fix/784-close-verb

2026-11-04 14:43:59 +00:00

mesh-tools referenced this pull request

2026-11-04 15:01:28 +00:00

mesh-knowledge: a closing is reviewed on its closing alone, a graduation on every became link it carries (issue 784) #611

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-catalog#610