From ace8f6c398275cf82412342691e8f4836f2f9f2c Mon Sep 17 00:00:00 2001 From: jochen Date: Sat, 10 Oct 2026 21:35:34 +0200 Subject: [PATCH] Renumber the fixing-status record to ADR 0284 (issue 406) hq #294 (issue 386) and #295 (issue 399) both merged a record numbered 0283; #294 landed first and keeps it. The branch that lands last renumbers. --- 00-META/glossary.md | 4 ++-- 00-META/process/03-issues.md | 2 +- ...ly-the-narrative-of-a-design-or-governance-issue.md | 2 +- ...elivered-and-a-fix-stuck-after-its-merge-is-loud.md | 2 +- ...-name-and-an-issue-is-resolved-only-from-fixing.md} | 4 +++- 03-DESIGN/01-to-be/53-the-issue-tracker.md | 10 +++++----- 6 files changed, 13 insertions(+), 11 deletions(-) rename 02-DECISIONS/{0283-an-agent-moves-an-issue-to-fixing-under-its-own-name-and-an-issue-is-resolved-only-from-fixing.md => 0284-an-agent-moves-an-issue-to-fixing-under-its-own-name-and-an-issue-is-resolved-only-from-fixing.md} (97%) diff --git a/00-META/glossary.md b/00-META/glossary.md index b6d30706..ec656d0b 100644 --- a/00-META/glossary.md +++ b/00-META/glossary.md @@ -551,7 +551,7 @@ asking, never the act. **Decided by** ADR 0152, 0175, 0234, 0259, 0272. ## The record — how this repository works Not a domain of the mesh but of the way it is built, listed because its words meet the mesh's. -**Recorded in** this repository and the issue tracker. **Decided by** ADR 0019, 0080, 0244, 0275, 0283. +**Recorded in** this repository and the issue tracker. **Decided by** ADR 0019, 0080, 0244, 0275, 0284. - **research effort**, **graduation**, **hand-off**, **playbook** — an investigation in `01-RESEARCH/`; its closing into a decision and a design; a design given to a code repository; a documented workflow @@ -579,7 +579,7 @@ Not a domain of the mesh but of the way it is built, listed because its words me - **worker** — of an issue: the agent or person, with its node (who@node), that moved it to `diagnosing` or `fixing` and works on it; another is refused while the worker is current, unless it gives a reason to **take it over**. A worker with nothing done on the issue for a day is **stale**. **Fixing** is the status an issue is at while its fix - is worked on; an issue is resolved only from it ([ADR 0283](../02-DECISIONS/0283-an-agent-moves-an-issue-to-fixing-under-its-own-name-and-an-issue-is-resolved-only-from-fixing.md)). + is worked on; an issue is resolved only from it ([ADR 0284](../02-DECISIONS/0284-an-agent-moves-an-issue-to-fixing-under-its-own-name-and-an-issue-is-resolved-only-from-fixing.md)). Not a *claim* or a *holder*, which are a module's on a seat. - **hq check** — one of `00-META/checks/`, run by `merge-check.sh` as this repository's check. diff --git a/00-META/process/03-issues.md b/00-META/process/03-issues.md index f86f40ff..b336e91d 100644 --- a/00-META/process/03-issues.md +++ b/00-META/process/03-issues.md @@ -82,7 +82,7 @@ import read, which every imported issue names (`imported.commit` in `issue-track `take-over` saying why, which is noted on the issue. A stale worker may be taken over from without a reason. Name the fix in `fixed-by` when it merges, with a move to `fixing` that gives `by` again; the issue stays `fixing` until the acceptance is proven live - ([ADR 0283](../../02-DECISIONS/0283-an-agent-moves-an-issue-to-fixing-under-its-own-name-and-an-issue-is-resolved-only-from-fixing.md), + ([ADR 0284](../../02-DECISIONS/0284-an-agent-moves-an-issue-to-fixing-under-its-own-name-and-an-issue-is-resolved-only-from-fixing.md), [ADR 0281](../../02-DECISIONS/0281-an-issue-knows-whether-its-fix-is-delivered-and-a-fix-stuck-after-its-merge-is-loud.md)). 4. Resolve. `issue-tracker.move` to `resolved`, which the tracker takes only from `fixing`, with `fixed-by`, and, if the root cause was a design gap, run playbook [02](02-graduation.md) and give `amended-design`. **A core issue** — its `located-in` diff --git a/02-DECISIONS/0275-the-mesh-numbers-and-tracks-its-issues-in-a-module-of-its-own-and-hq-keeps-only-the-narrative-of-a-design-or-governance-issue.md b/02-DECISIONS/0275-the-mesh-numbers-and-tracks-its-issues-in-a-module-of-its-own-and-hq-keeps-only-the-narrative-of-a-design-or-governance-issue.md index dffa4f0d..92c8733b 100644 --- a/02-DECISIONS/0275-the-mesh-numbers-and-tracks-its-issues-in-a-module-of-its-own-and-hq-keeps-only-the-narrative-of-a-design-or-governance-issue.md +++ b/02-DECISIONS/0275-the-mesh-numbers-and-tracks-its-issues-in-a-module-of-its-own-and-hq-keeps-only-the-narrative-of-a-design-or-governance-issue.md @@ -117,7 +117,7 @@ along the way". ([ADR 0237](0237-a-change-is-judged-against-the-mesh-that-runs-before-it-merges-on-the-build-seat.md)); `wontfix` needs a reason. `located-in` names an entry of a registered list of repositories and modules. - > **The mechanism changed — 2026-10-10, by [ADR 0283](0283-an-agent-moves-an-issue-to-fixing-under-its-own-name-and-an-issue-is-resolved-only-from-fixing.md).** + > **The mechanism changed — 2026-10-10, by [ADR 0284](0284-an-agent-moves-an-issue-to-fixing-under-its-own-name-and-an-issue-is-resolved-only-from-fixing.md).** > What still stands: the cycle's rules are enforced at the write, and §5 for who acted. What moved: there are six > statuses, `fixing` between `located` and `resolved`; a move to `diagnosing` or `fixing` names the issue's worker > in `by`, which is not the actor of §5 but who works on it as they state it; and `resolved` is reached only from diff --git a/02-DECISIONS/0281-an-issue-knows-whether-its-fix-is-delivered-and-a-fix-stuck-after-its-merge-is-loud.md b/02-DECISIONS/0281-an-issue-knows-whether-its-fix-is-delivered-and-a-fix-stuck-after-its-merge-is-loud.md index f225efd4..fbe61fd4 100644 --- a/02-DECISIONS/0281-an-issue-knows-whether-its-fix-is-delivered-and-a-fix-stuck-after-its-merge-is-loud.md +++ b/02-DECISIONS/0281-an-issue-knows-whether-its-fix-is-delivered-and-a-fix-stuck-after-its-merge-is-loud.md @@ -84,7 +84,7 @@ therefore name a fix in `fixed-by` when it merges, with the issue still `located `move` to the status an issue already has is taken when it changes what the issue holds, such as its `fixed-by`, and refused when it changes nothing. `move` still requires `fixed-by` to resolve. -> **The mechanism changed — 2026-10-10, by [ADR 0283](0283-an-agent-moves-an-issue-to-fixing-under-its-own-name-and-an-issue-is-resolved-only-from-fixing.md).** +> **The mechanism changed — 2026-10-10, by [ADR 0284](0284-an-agent-moves-an-issue-to-fixing-under-its-own-name-and-an-issue-is-resolved-only-from-fixing.md).** > What still stands: delivered is not resolved, and an issue is resolved after the proof. What moved: the fix is > named while the issue stays `fixing`, not `located`, because an issue is resolved only from `fixing`, and a move > to `fixing` names its worker in `by`. diff --git a/02-DECISIONS/0283-an-agent-moves-an-issue-to-fixing-under-its-own-name-and-an-issue-is-resolved-only-from-fixing.md b/02-DECISIONS/0284-an-agent-moves-an-issue-to-fixing-under-its-own-name-and-an-issue-is-resolved-only-from-fixing.md similarity index 97% rename from 02-DECISIONS/0283-an-agent-moves-an-issue-to-fixing-under-its-own-name-and-an-issue-is-resolved-only-from-fixing.md rename to 02-DECISIONS/0284-an-agent-moves-an-issue-to-fixing-under-its-own-name-and-an-issue-is-resolved-only-from-fixing.md index 3aef27a0..43fd68d4 100644 --- a/02-DECISIONS/0283-an-agent-moves-an-issue-to-fixing-under-its-own-name-and-an-issue-is-resolved-only-from-fixing.md +++ b/02-DECISIONS/0284-an-agent-moves-an-issue-to-fixing-under-its-own-name-and-an-issue-is-resolved-only-from-fixing.md @@ -7,7 +7,9 @@ reconstructed: false extends: 02-DECISIONS/0275-the-mesh-numbers-and-tracks-its-issues-in-a-module-of-its-own-and-hq-keeps-only-the-narrative-of-a-design-or-governance-issue.md --- -# 283. An agent moves an issue to fixing under its own name, and an issue is resolved only from fixing +# 284. An agent moves an issue to fixing under its own name, and an issue is resolved only from fixing + +> **Renumbered — 2026-10-10.** This record was merged as 0283 at the same moment as the record of issue 386, which merged first and keeps 0283; the branch that lands last renumbers. The agent rule approved the same evening still cites it as 0283 until its text is approved again. ## Context diff --git a/03-DESIGN/01-to-be/53-the-issue-tracker.md b/03-DESIGN/01-to-be/53-the-issue-tracker.md index 815c8130..e6a65869 100644 --- a/03-DESIGN/01-to-be/53-the-issue-tracker.md +++ b/03-DESIGN/01-to-be/53-the-issue-tracker.md @@ -8,7 +8,7 @@ decisions: - 02-DECISIONS/0278-the-issue-tracker-checks-every-new-issue-for-a-duplicate-through-a-judgement-the-agent-makes-without-tools.md - 02-DECISIONS/0279-the-issue-tracker-triages-every-new-issue-and-an-issue-is-ready-when-what-it-depends-on-is-delivered.md - 02-DECISIONS/0281-an-issue-knows-whether-its-fix-is-delivered-and-a-fix-stuck-after-its-merge-is-loud.md - - 02-DECISIONS/0283-an-agent-moves-an-issue-to-fixing-under-its-own-name-and-an-issue-is-resolved-only-from-fixing.md + - 02-DECISIONS/0284-an-agent-moves-an-issue-to-fixing-under-its-own-name-and-an-issue-is-resolved-only-from-fixing.md --- # 53 — The issue tracker @@ -83,7 +83,7 @@ an agent picks the right one from `mesh_search` alone. A refusal says what was w **The caller is the bus credential, never an argument.** The runtime hands the module the identity of each call's caller; the module records that identity as who acted. No verb takes an actor. `by` on `move` is not one: it names the issue's worker, who works on it, as the worker states it -([ADR 0283](../../02-DECISIONS/0283-an-agent-moves-an-issue-to-fixing-under-its-own-name-and-an-issue-is-resolved-only-from-fixing.md)). +([ADR 0284](../../02-DECISIONS/0284-an-agent-moves-an-issue-to-fixing-under-its-own-name-and-an-issue-is-resolved-only-from-fixing.md)). ## 3. What one issue holds @@ -162,7 +162,7 @@ event carries a secret, and an issue holds none. | `wontfix` | a reason | A refused move changes nothing and says which rule refused it. The rows for `diagnosing`, `fixing` and `resolved` are -[ADR 0283](../../02-DECISIONS/0283-an-agent-moves-an-issue-to-fixing-under-its-own-name-and-an-issue-is-resolved-only-from-fixing.md)'s: +[ADR 0284](../../02-DECISIONS/0284-an-agent-moves-an-issue-to-fixing-under-its-own-name-and-an-issue-is-resolved-only-from-fixing.md)'s: resolved only from `fixing` is the check that an agent said it started the fix. `cycle.py` checked the folders that carried status until slice 3; since then it refuses a status key in any report, and judges no issue's status. @@ -188,7 +188,7 @@ worker; one that stops moves the issue on, or is stale a day later. | The cycle's rules hold at the write | the module's table test over § 5, one case per row, each refused case changing nothing | | The module creates no bucket | the runtime refuses a module that tries (ADR 0201 §3); the controller's raise asserts both buckets | | The caller is who acted | the module's test that the recorded actor is the call's identity, whatever the arguments say | -| A worker is named on a move to diagnosing or fixing, another is refused while it is current, a take-over is noted, a stale one may be taken over from, and resolved is reached only from fixing | the rows of [ADR 0283](../../02-DECISIONS/0283-an-agent-moves-an-issue-to-fixing-under-its-own-name-and-an-issue-is-resolved-only-from-fixing.md)'s "How it is checked" | +| A worker is named on a move to diagnosing or fixing, another is refused while it is current, a take-over is noted, a stale one may be taken over from, and resolved is reached only from fixing | the rows of [ADR 0284](../../02-DECISIONS/0284-an-agent-moves-an-issue-to-fixing-under-its-own-name-and-an-issue-is-resolved-only-from-fixing.md)'s "How it is checked" | | An issue's delivery line follows the delivery; ready to verify once; a stuck fix said once and cleared | the rows of [ADR 0281](../../02-DECISIONS/0281-an-issue-knows-whether-its-fix-is-delivered-and-a-fix-stuck-after-its-merge-is-loud.md)'s "How it is checked" | | The triage fills only what is empty, links no cycle, and an issue is ready only when its dependencies' fixes are delivered | the rows of [ADR 0279](../../02-DECISIONS/0279-the-issue-tracker-triages-every-new-issue-and-an-issue-is-ready-when-what-it-depends-on-is-delivered.md)'s "How it is checked" | | The duplicate check acts only on a clear duplicate, never on an older or a resolved issue, once per issue, loudly when it cannot judge | the rows of [ADR 0278](../../02-DECISIONS/0278-the-issue-tracker-checks-every-new-issue-for-a-duplicate-through-a-judgement-the-agent-makes-without-tools.md)'s "How it is checked" | @@ -277,4 +277,4 @@ stuck after its merge is said** ([ADR 0281](../../02-DECISIONS/0281-an-issue-kno Priorities beyond severity, notifications beyond the `ready` and `ready-to-verify` events and the stuck-fix warning, full-text or semantic search, the forge's own issue lists, and an index of any kind: none of them is in any slice above, and each needs a decision of its own. Who works on an issue, listed here until -2026-10-10, is settled by [ADR 0283](../../02-DECISIONS/0283-an-agent-moves-an-issue-to-fixing-under-its-own-name-and-an-issue-is-resolved-only-from-fixing.md). +2026-10-10, is settled by [ADR 0284](../../02-DECISIONS/0284-an-agent-moves-an-issue-to-fixing-under-its-own-name-and-an-issue-is-resolved-only-from-fixing.md).