An active research effort takes new versions, reviewed as proposals (hq issue 844) #318

Merged

mesh-tools merged 3 commits from fix/844-an-active-effort-takes-new-versions into main 2026-10-15 19:35:08 +00:00

Conversation 3 Commits 3 Files Changed 9

+197 -15

mesh-tools commented 2026-10-15 19:30:29 +00:00

Member

Copy Link

Copy Source

Fixes hq issue 844: knowledge-base.propose refused every new version of an accepted research effort with status active unless it came as a progressive insight, and the review then judged a new finding or document as a correction of fact. Playbook 01 does research in further documents of the same effort.

• Propose (modules/mesh-knowledge cmd/mesh-knowledge/kb.go): a research effort whose served status is active takes a new version without insight, stored pending so the served version stays until the review approves; a graduated or abandoned effort and an accepted decision still need insight. Record.IsInsight(); accept records no empty insight; review.go and operator.go use the same check, so the review does not call such a version a correction of fact. README and the tool's description say the exception.
• Dated rules (deferral, retired words, daemon lines): a new version of an active effort is judged by the rules in force on the day it is proposed (JudgeRecordOn), while the record keeps its own date, so an old effort's marked insights still pass the insight-form rule.
• Tests (active_effort_test.go): an active effort takes a new document, reviewed as a proposal and not an insight in history; a graduated effort and a decision still refuse; a changes verdict leaves the served version served; active to graduated without became still refused; an effort dated 2026-10-01 refuses a retired word in a new version; an effort holding a marked insight of 2026-10-05 takes a new version.

Playbook 08. gofmt, go vet, go test ./..., MESH_CHECK_MODULES=mesh-knowledge merge-check.sh pass. Reviewed independently before push, three rounds: APPROVE at f75e1a91d9 (round 2 found the clone's date read by insight-form; round 3 confirmed its test fails at ebfec39).

Fixes hq issue 844: `knowledge-base.propose` refused every new version of an accepted research effort with status active unless it came as a progressive insight, and the review then judged a new finding or document as a correction of fact. Playbook 01 does research in further documents of the same effort. - `Propose` (modules/mesh-knowledge cmd/mesh-knowledge/kb.go): a research effort whose served status is active takes a new version without `insight`, stored pending so the served version stays until the review approves; a graduated or abandoned effort and an accepted decision still need `insight`. `Record.IsInsight()`; `accept` records no empty insight; review.go and operator.go use the same check, so the review does not call such a version a correction of fact. README and the tool's description say the exception. - Dated rules (deferral, retired words, daemon lines): a new version of an active effort is judged by the rules in force on the day it is proposed (`JudgeRecordOn`), while the record keeps its own date, so an old effort's marked insights still pass the insight-form rule. - Tests (active_effort_test.go): an active effort takes a new document, reviewed as a proposal and not an insight in history; a graduated effort and a decision still refuse; a changes verdict leaves the served version served; active to graduated without `became` still refused; an effort dated 2026-10-01 refuses a retired word in a new version; an effort holding a marked insight of 2026-10-05 takes a new version. Playbook 08. gofmt, go vet, go test ./..., MESH_CHECK_MODULES=mesh-knowledge merge-check.sh pass. Reviewed independently before push, three rounds: APPROVE at f75e1a91d957362e6d418db587bedd2de8683f0e (round 2 found the clone's date read by insight-form; round 3 confirmed its test fails at ebfec39).

mesh-tools added 3 commits 2026-10-15 19:30:29 +00:00

An active research effort takes new versions, reviewed as proposals (hq issue 844) 24d05701d3

Hold an active effort's new version to the dated rules of the day it is proposed (hq issue 844) ebfec39937

Carry the proposal day only into the dated rules, so an old effort's marked insight stands (hq issue 844) f75e1a91d9

mesh-tools commented 2026-10-15 19:30:36 +00:00

Author

Member

Copy Link

Copy Source

Delivery novox/mesh-catalog@f75e1a91d957 — delivered since 2026-10-15T19:36:34Z

Delivery plan — builds mesh-knowledge → novox; no bus step

• tier 0: mesh-knowledge
• novox: receives mesh-knowledge

Machines

• mesh-knowledge on every machine running it: sent

Transitions

• 2026-10-15 19:30 (new) → proposed (announced): novox/mesh-catalog#318's head announced
• 2026-10-15 19:35 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
• 2026-10-15 19:35 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
• 2026-10-15 19:35 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
• 2026-10-15 19:35 published → delivering (go): its walk started: let go by this owner in its group's order, by a person, or on the controller's own path — not a failed walk that carried a later commit for it, after which it waits for a walk of its own commit
• 2026-10-15 19:36 delivering → delivered (done): its walk is done, carrying its own commit: every machine of its deploy plan passed, or was left as its policy says

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

<!-- mesh-delivery:view --> **Delivery** `novox/mesh-catalog@f75e1a91d957` — **delivered** since 2026-10-15T19:36:34Z **Delivery plan** — builds mesh-knowledge → novox; no bus step - tier 0: mesh-knowledge - novox: receives mesh-knowledge **Machines** - mesh-knowledge on every machine running it: sent **Transitions** - 2026-10-15 19:30 (new) → proposed (announced): novox/mesh-catalog#318's head announced - 2026-10-15 19:35 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit - 2026-10-15 19:35 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-15 19:35 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-15 19:35 published → delivering (go): its walk started: let go by this owner in its group's order, by a person, or on the controller's own path — not a failed walk that carried a later commit for it, after which it waits for a walk of its own commit - 2026-10-15 19:36 delivering → delivered (done): its walk is done, carrying its own commit: every machine of its deploy plan passed, or was left as its policy says The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.

mesh-tools added the mesh/ready label 2026-10-15 19:32:18 +00:00

mesh-tools commented 2026-10-15 19:32:18 +00:00

Author

Member

Copy Link

Copy Source

ready at f75e1a91d9 (the operator's word, 2026-10-15; independent review APPROVE at this sha, round 3).

ready at f75e1a91d957362e6d418db587bedd2de8683f0e (the operator's word, 2026-10-15; independent review APPROVE at this sha, round 3).

mesh-tools commented 2026-10-15 19:35:04 +00:00

Author

Member

Copy Link

Copy Source

Merge check at f75e1a91
Judged: head f75e1a91d957 merged into trunk a95b3fa053e0; read beside it: mesh-controller 7543f64911c5, mesh-controller-main 7543f64911c5, mesh-host 198fd34ec497, mesh-tools 6b3e15042fee

• mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-knowledge)
• mesh/repo-check: PASS — its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)

Delivery plan — builds mesh-knowledge → novox; no bus step

• tier 0: mesh-knowledge
• novox: receives mesh-knowledge
• read by no module's build: modules/mesh-knowledge/README.md, modules/mesh-knowledge/cmd/mesh-knowledge/active_effort_test.go

Run by the build seat on shanks as build-1792092631035645003 (builds --log build-1792092631035645003).

--- the gate: mesh-knowledge
note: mesh-knowledge uses the seat "operator-channel", which no module declares and the mesh does not define among the manifests given; registration judges it against the whole catalogue, and passing the declaring module's manifest too judges it here
mesh-knowledge: ok, 2 tool(s), invokes seat:issue-tracker.reserve, claude-code.claude_code_judge, claude-code.claude_code_judged, records.records_status, records.records_list, records.records_read, seat:operator-channel.notify, ready: keep by unit every 30s; watch by its tool knowledge_health every 1m0s
long-running resources without health: 0
files asking for a setting without saying whether it is trusted: 0
1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
judging 0 module(s) changed against 4 machine(s), as the snapshot of 2026-10-15T19:17:28Z says they run
composing every machine as the mesh is
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
composing every machine with the change
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose)
judged by controller development build against the facts of 2026-10-15T19:17:28Z

machines:
  - a machine (f35): composes
  - holds mesh-dns-resolver (idt): composes
  - holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes
  - a machine (yvbpsm): composes

a merge would rebuild 1 module(s) in 1 tier(s): mesh-knowledge

notes:
  - modules/mesh-knowledge/README.md and modules/mesh-knowledge/cmd/mesh-knowledge/active_effort_test.go read by no module's build, and rebuild nothing (issue 280)
--- its merge-check.sh (go toolchain)
ok  	git.novox.be/novox/mesh-catalog/checks/words	0.003s
words: 12 retired words and 70 daemons' lines, none in the 48734 strings of 746 files
ok  	git.novox.be/novox/mesh-catalog/checks/agenthome	0.013s
agent-home: no archive and no file written into under the agent's home
ok  	git.novox.be/novox/mesh-catalog/checks/mailstore	0.010s
mail-store: claimed only by mesh-mail
ok  	git.novox.be/novox/mesh-catalog/checks/secrets	0.013s
secrets: no setting can replace a vault secret in a mergeable file (1 known, nested)
ok  	git.novox.be/novox/mesh-catalog/checks/paths	0.006s
paths: no module names another's state on its machine (3 known, listed to go)
long-running resources without health: 62, as kept
ok  	git.novox.be/novox/mesh-catalog/checks/deps	0.209s
testing modules/mesh-knowledge
ok  	mesh-knowledge/cmd/mesh-knowledge	128.421s
--- its merge-check-typescript.sh (typescript toolchain)

**Merge check** at `f75e1a91` Judged: head `f75e1a91d957` merged into trunk `a95b3fa053e0`; read beside it: mesh-controller `7543f64911c5`, mesh-controller-main `7543f64911c5`, mesh-host `198fd34ec497`, mesh-tools `6b3e15042fee` - `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-knowledge) - `mesh/repo-check`: **PASS** — its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript) **Delivery plan** — builds mesh-knowledge → novox; no bus step - tier 0: mesh-knowledge - novox: receives mesh-knowledge - read by no module's build: modules/mesh-knowledge/README.md, modules/mesh-knowledge/cmd/mesh-knowledge/active_effort_test.go Run by the build seat on shanks as `build-1792092631035645003` (`builds --log build-1792092631035645003`). ``` --- the gate: mesh-knowledge note: mesh-knowledge uses the seat "operator-channel", which no module declares and the mesh does not define among the manifests given; registration judges it against the whole catalogue, and passing the declaring module's manifest too judges it here mesh-knowledge: ok, 2 tool(s), invokes seat:issue-tracker.reserve, claude-code.claude_code_judge, claude-code.claude_code_judged, records.records_status, records.records_list, records.records_read, seat:operator-channel.notify, ready: keep by unit every 30s; watch by its tool knowledge_health every 1m0s long-running resources without health: 0 files asking for a setting without saying whether it is trusted: 0 1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here judging 0 module(s) changed against 4 machine(s), as the snapshot of 2026-10-15T19:17:28Z says they run composing every machine as the mesh is the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued composing every machine with the change the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose) judged by controller development build against the facts of 2026-10-15T19:17:28Z machines: - a machine (f35): composes - holds mesh-dns-resolver (idt): composes - holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes - a machine (yvbpsm): composes a merge would rebuild 1 module(s) in 1 tier(s): mesh-knowledge notes: - modules/mesh-knowledge/README.md and modules/mesh-knowledge/cmd/mesh-knowledge/active_effort_test.go read by no module's build, and rebuild nothing (issue 280) --- its merge-check.sh (go toolchain) ok git.novox.be/novox/mesh-catalog/checks/words 0.003s words: 12 retired words and 70 daemons' lines, none in the 48734 strings of 746 files ok git.novox.be/novox/mesh-catalog/checks/agenthome 0.013s agent-home: no archive and no file written into under the agent's home ok git.novox.be/novox/mesh-catalog/checks/mailstore 0.010s mail-store: claimed only by mesh-mail ok git.novox.be/novox/mesh-catalog/checks/secrets 0.013s secrets: no setting can replace a vault secret in a mergeable file (1 known, nested) ok git.novox.be/novox/mesh-catalog/checks/paths 0.006s paths: no module names another's state on its machine (3 known, listed to go) long-running resources without health: 62, as kept ok git.novox.be/novox/mesh-catalog/checks/deps 0.209s testing modules/mesh-knowledge ok mesh-knowledge/cmd/mesh-knowledge 128.421s --- its merge-check-typescript.sh (typescript toolchain) ```

mesh-tools merged commit de6657c846 into main 2026-10-15 19:35:08 +00:00

mesh-tools deleted branch fix/844-an-active-effort-takes-new-versions 2026-10-15 19:35:09 +00:00

Sign in to join this conversation.

Reviewers

No Reviewers

Labels

Clear labels

mesh/ready

Reviewed and ready: mesh-delivery merges at the marked head once its checks pass (hq ADR 0364)

No labels mesh/ready

Milestone

No items

No Milestone

Projects

Clear projects

No projects

Assignees

Clear assignees

jschoubben mesh-tools miel.truyen

No Assignees

1 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-catalog#318