The knowledge base keeps the roadmap: a research effort can be an idea, and at most three are active (issue 1970, ADR 0629) #609

2026-11-04T13:36:11Z

mesh-tools commented

2026-11-04 13:36:11 +00:00

Issue 1970, ADR 0629 (the knowledge base's review approved version 7; it waits for the operator's Approve, asked on Telegram 14:28).

Why: the operator, 2026-11-04, limited active research to three; the rest are ideas, the mesh's roadmap, not truths, researched again when taken up.

§1: research status idea; list at idea is the roadmap.
§2: an idea is not in force: ask skips it, holds serves nothing from it (Served), get names it as one to research again.
§3: an idea takes new versions like an active effort; proposing it at active is a take-up.
§4: propose refuses a research effort becoming active (new or taken up) at the limit, naming the active ones; an effort already active always takes a new version. Setting research-active-at-most, default 3 (module.json config, files/settings.json).
§5/§6 (the move of 23 efforts to idea) follow the delivery, read back on issue 1970.

Tests: idea_test.go, two table tests, each case shown to fail without its change by the reviewer; module at 107 of 500 unit tests, no integration test added. go vet, vet -tags integration and go test pass locally (21 s).

Quick or thorough: quick = the status only; thorough (chosen, what ADR 0629 decides) = status, not-in-force, refusal and setting.

Reviewed-by: mesh-code-reviewer@shanks at 55a88cdba4

https://claude.ai/code/session_01JG73KG7AfSdh6FP8VrBqCn

Issue 1970, ADR 0629 (the knowledge base's review approved version 7; it waits for the operator's Approve, asked on Telegram 14:28). Why: the operator, 2026-11-04, limited active research to three; the rest are ideas, the mesh's roadmap, not truths, researched again when taken up. - §1: research status `idea`; `list` at `idea` is the roadmap. - §2: an idea is not in force: `ask` skips it, `holds` serves nothing from it (Served), `get` names it as one to research again. - §3: an idea takes new versions like an active effort; proposing it at `active` is a take-up. - §4: `propose` refuses a research effort becoming active (new or taken up) at the limit, naming the active ones; an effort already active always takes a new version. Setting `research-active-at-most`, default 3 (module.json config, files/settings.json). - §5/§6 (the move of 23 efforts to `idea`) follow the delivery, read back on issue 1970. Tests: idea_test.go, two table tests, each case shown to fail without its change by the reviewer; module at 107 of 500 unit tests, no integration test added. go vet, vet -tags integration and go test pass locally (21 s). Quick or thorough: quick = the status only; thorough (chosen, what ADR 0629 decides) = status, not-in-force, refusal and setting. Reviewed-by: mesh-code-reviewer@shanks at 55a88cdba4e54696f718dd4b67e54f6b46d860a7 https://claude.ai/code/session_01JG73KG7AfSdh6FP8VrBqCn

mesh-tools added 3 commits 2026-11-04 13:36:11 +00:00

Research efforts can be ideas, and at most three are active (issue 1970, ADR 0629) b0a275c126

The roadmap lives in the knowledge base: an idea is listed, never served as in force; propose refuses a further active effort.

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

Research limit: a new version of an active effort is never refused; holds and tool text follow (issue 1970, ADR 0629) 29f6039fb1

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

Drop a holds test that passes without its change; the propose description names the limit's setting

mesh/check being carried to 55a88cdba4e5 on 79c2fc7fe1d5 | from 7fe569ef4067

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

Details

55a88cdba4

Round 2 of issue 1970's review: a research effort has no clauses, so holds never serves one; Served on an
idea is tested in TestAnIdeaIsListedAndNeverServedAsTruth.

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

mesh-tools commented

2026-11-04 13:36:14 +00:00

Delivery novox/mesh-catalog@55a88cdba4e5 — merged since 2026-11-04T13:57:24Z

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

Transitions

2026-11-04 13:36 (new) → proposed (announced): novox/mesh-catalog#609's head announced
2026-11-04 13:36 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 13:57 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@55a88cdba4e5` — **merged** since 2026-11-04T13:57:24Z **Source** — source.main moved to novox/mesh-catalog@79c2fc7fe1d5. Whether it reached the machines is `mesh-delivery-view`'s, derived from `source.main`, the wants and the haves. **Transitions** - 2026-11-04 13:36 (new) → proposed (announced): novox/mesh-catalog#609's head announced - 2026-11-04 13:36 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 13:57 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 79c2fc7fe1 into main

2026-11-04 13:57:21 +00:00

mesh-tools deleted branch fix/1970-research-ideas

2026-11-04 13:57:22 +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#609