ADR 0283: an agent moves an issue to fixing under its own name, and an issue is resolved only from fixing (issue 399) #295

Merged
mesh-admin merged 2 commits from feat/399-fixing-status into main 2026-10-10 19:13:25 +00:00
Contributor

Issue 399: nothing on an issue says who works on it, and an issue can be resolved without anyone having said they started its fix.

This pull request:

  • adds ADR 0283, extending ADR 0275 and settling what to-be 53 left out as "claims": the status fixing (open, diagnosing, located, fixing, resolved, or wontfix); a move to diagnosing or fixing names the issue's worker in by (who@node); another worker is refused while the worker is current unless take-over gives a reason, which is noted; a worker with nothing done on the issue for 24 hours (worker-stale-after) is stale and may be taken over from without one; resolved is reached only from fixing, which is the check that the agent rule holds; the moved event carries by, since and caller;
  • proposes the glossary word worker (glossary's claim and holder are a module's on a seat);
  • amends to-be 53 (§2, §3, §4, §5, §6, §7, §9, §11, What it leaves out), playbook 03 (an agent moves to diagnosing or fixing with by before it starts), the hq-diagnose and hq-status skills;
  • adds dated "mechanism changed" notes to ADR 0275 §6 and ADR 0281 §3.

The module change is mesh-catalog feat/399-fixing-status. The consequences name issue 400 (an alert names the issue tracking its condition and that issue's state) as the next step.

Checks run locally: records.py, cycle.py, index.py, words.py (with MESH_CATALOG_DIR), merge-check.sh, all passing.

Issue 399: nothing on an issue says who works on it, and an issue can be resolved without anyone having said they started its fix. This pull request: - adds ADR 0283, extending ADR 0275 and settling what to-be 53 left out as "claims": the status `fixing` (open, diagnosing, located, fixing, resolved, or wontfix); a move to `diagnosing` or `fixing` names the issue's **worker** in `by` (who@node); another worker is refused while the worker is current unless `take-over` gives a reason, which is noted; a worker with nothing done on the issue for 24 hours (`worker-stale-after`) is stale and may be taken over from without one; `resolved` is reached only from `fixing`, which is the check that the agent rule holds; the `moved` event carries `by`, `since` and `caller`; - proposes the glossary word **worker** (glossary's *claim* and *holder* are a module's on a seat); - amends to-be 53 (§2, §3, §4, §5, §6, §7, §9, §11, What it leaves out), playbook 03 (an agent moves to diagnosing or fixing with `by` before it starts), the hq-diagnose and hq-status skills; - adds dated "mechanism changed" notes to ADR 0275 §6 and ADR 0281 §3. The module change is mesh-catalog `feat/399-fixing-status`. The consequences name issue 400 (an alert names the issue tracking its condition and that issue's state) as the next step. Checks run locally: records.py, cycle.py, index.py, words.py (with MESH_CATALOG_DIR), merge-check.sh, all passing.
mesh-admin added 1 commit 2026-10-10 19:07:30 +00:00
ADR 0283: an agent moves an issue to fixing under its own name, and resolves only from fixing (issue 399)
mesh/delivery-group group feat/399-fixing-status checking: 0 of 2 member(s) ready
mesh/merge-gate pass: the change touches no module of the mesh's graph
mesh/repo-check pass: its merge-check.sh passed
mesh/delivery superseded: a newer head of the same pull request
21973e2e4a
Two agents could start on one issue without seeing each other, and an issue
could be resolved without anyone having said they started its fix. Adds the
status fixing, the issue's worker (by, who@node) with take-over and a stale
bound, and resolved only from fixing; settles what to-be 53 left out as
claims, under the new glossary word worker. Amends to-be 53, playbook 03 and
the hq-diagnose and hq-status skills, with pointer notes on ADR 0275 and 0281.
Author
Contributor

Delivery novox/hq@8cdc9706e1c0 — delivered since 2026-10-10T19:13:29Z

Delivery plan — builds nothing: the change touches no module of the mesh's graph

Group feat/399-fixing-status, in order: novox/hq@8cdc9706e1 → novox/mesh-catalog@a73b04843d

Transitions

  • 2026-10-10 19:08 (new) → proposed (announced): novox/hq#295's head announced
  • 2026-10-10 19:09 proposed → checked (checked): the verdict names this commit
  • 2026-10-10 19:09 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
  • 2026-10-10 19:13 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
  • 2026-10-10 19:13 published → delivered (done): nothing for a walk to move

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

<!-- mesh-delivery:view --> **Delivery** `novox/hq@8cdc9706e1c0` — **delivered** since 2026-10-10T19:13:29Z **Delivery plan** — builds nothing: the change touches no module of the mesh's graph **Group** `feat/399-fixing-status`, in order: novox/hq@8cdc9706e1c0 → novox/mesh-catalog@a73b04843dd1 **Transitions** - 2026-10-10 19:08 (new) → proposed (announced): novox/hq#295's head announced - 2026-10-10 19:09 proposed → checked (checked): the verdict names this commit - 2026-10-10 19:09 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-10 19:13 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-10 19:13 published → delivered (done): nothing for a walk to move The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.
jschoubben added 1 commit 2026-10-10 19:08:27 +00:00
Use role names, not node names, in the worker examples (public repository)
mesh/merge-gate pass: the change touches no module of the mesh's graph
mesh/repo-check pass: its merge-check.sh passed
mesh/delivery delivered
mesh/delivery-group group feat/399-fixing-status merged: every member is merged
8cdc9706e1
mesh-admin merged commit 61255b56d4 into main 2026-10-10 19:13:25 +00:00
mesh-admin deleted branch feat/399-fixing-status 2026-10-10 19:13:25 +00:00
Sign in to join this conversation.
No Reviewers
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: novox/hq#295