fix(decisions): resolve duplicate ADR-0023 — renumber wloczykij to 0026 #756

Closed
opened 2026-06-08 23:07:57 +02:00 by ollama · 1 comment
Collaborator

Spec sources (whitelist)

  • decisions/0023-wloczykij-gold-vault-and-iskra-promotion-boundary.md — duplicate ADR number
  • decisions/0023-gemini-3-5-flash-reviewer-cousin.md — the other ADR-0023 (keep as-is)
  • state/roadmap/wloczykij-gold-vault-implementation-plan.md:6 — inbound ref to wloczykij ADR
  • modules/obsidian-headless-sync/runbook.md:14 — inbound ref to wloczykij ADR
  • modules/iskra-things-sync/runbook.md:270 — inbound ref to wloczykij ADR
  • MAP.md:105 — inbound ref to gemini ADR-0023 (verify still correct after rename)
  • state/strategy/memory-control-plane-2026-05-24.md:200 — inbound ref to gemini ADR-0023 (verify still correct)
  • policies/agent-capabilities.yaml:16 — inbound ref to gemini ADR-0023 (verify still correct)

Extracted context

Two distinct ADRs both numbered 0023, both Status: Accepted, neither has a renumber note — a regression against the documented 0006→0010 / 0007→0011 renumber discipline from earlier collisions.

Inbound bare ADR-0023 refs resolve ambiguously to both files.

Scope

  1. Rename file: decisions/0023-wloczykij-gold-vault-and-iskra-promotion-boundary.mddecisions/0026-wloczykij-gold-vault-and-iskra-promotion-boundary.md
  2. Add renumeration note in the renamed file header (mirror ADR-0010 format):
    > **Renumeration note (2026-06-08):** This ADR was originally drafted as 0023. Renumbered to 0026 to resolve a duplicate-number collision with `decisions/0023-gemini-3-5-flash-reviewer-cousin.md`.
    
  3. Update 3 inbound refs that point to wloczykij:
    • state/roadmap/wloczykij-gold-vault-implementation-plan.md:6
    • modules/obsidian-headless-sync/runbook.md:14
    • modules/iskra-things-sync/runbook.md:270
  4. Verify 3 gemini refs still correct (pointing at 0023, not the moved file)

Acceptance criteria

  • No two ADR files share number 0023
  • Every bare ADR-0023 ref resolves unambiguously to gemini
  • Wloczykij refs point at 0026
  • Renumber note present in 0026 file

Do NOT read

  • Only read the files listed above
  • Do NOT modify the gemini ADR-0023 file
  • Do NOT modify MAP.md (it correctly references gemini 0023)

Agent notes

  • Recommended executor: Gemini 3.1 Pro (mechanical rename + 3 ref updates)
  • Size: Small (~20 LOC + rename)
  • Review tier: tier/lite (touches decisions/ directory)
  • Audit ref: state/audit/deepseek-2026-06-08-multiperspective.md §A5
  • Reference: this is a subset of #730 (claude's deslop issue)
## Spec sources (whitelist) - `decisions/0023-wloczykij-gold-vault-and-iskra-promotion-boundary.md` — duplicate ADR number - `decisions/0023-gemini-3-5-flash-reviewer-cousin.md` — the other ADR-0023 (keep as-is) - `state/roadmap/wloczykij-gold-vault-implementation-plan.md:6` — inbound ref to wloczykij ADR - `modules/obsidian-headless-sync/runbook.md:14` — inbound ref to wloczykij ADR - `modules/iskra-things-sync/runbook.md:270` — inbound ref to wloczykij ADR - `MAP.md:105` — inbound ref to gemini ADR-0023 (verify still correct after rename) - `state/strategy/memory-control-plane-2026-05-24.md:200` — inbound ref to gemini ADR-0023 (verify still correct) - `policies/agent-capabilities.yaml:16` — inbound ref to gemini ADR-0023 (verify still correct) ## Extracted context Two distinct ADRs both numbered 0023, both `Status: Accepted`, neither has a renumber note — a regression against the documented 0006→0010 / 0007→0011 renumber discipline from earlier collisions. Inbound bare `ADR-0023` refs resolve ambiguously to both files. ## Scope 1. Rename file: `decisions/0023-wloczykij-gold-vault-and-iskra-promotion-boundary.md` → `decisions/0026-wloczykij-gold-vault-and-iskra-promotion-boundary.md` 2. Add renumeration note in the renamed file header (mirror ADR-0010 format): ``` > **Renumeration note (2026-06-08):** This ADR was originally drafted as 0023. Renumbered to 0026 to resolve a duplicate-number collision with `decisions/0023-gemini-3-5-flash-reviewer-cousin.md`. ``` 3. Update 3 inbound refs that point to wloczykij: - `state/roadmap/wloczykij-gold-vault-implementation-plan.md:6` - `modules/obsidian-headless-sync/runbook.md:14` - `modules/iskra-things-sync/runbook.md:270` 4. Verify 3 gemini refs still correct (pointing at 0023, not the moved file) ## Acceptance criteria - [ ] No two ADR files share number 0023 - [ ] Every bare `ADR-0023` ref resolves unambiguously to gemini - [ ] Wloczykij refs point at 0026 - [ ] Renumber note present in 0026 file ## Do NOT read - Only read the files listed above - Do NOT modify the gemini ADR-0023 file - Do NOT modify MAP.md (it correctly references gemini 0023) ## Agent notes - Recommended executor: Gemini 3.1 Pro (mechanical rename + 3 ref updates) - Size: Small (~20 LOC + rename) - Review tier: tier/lite (touches decisions/ directory) - Audit ref: state/audit/deepseek-2026-06-08-multiperspective.md §A5 - Reference: this is a subset of #730 (claude's deslop issue)
Owner

Closing as already implemented on current main. Evidence: decisions/0026-wloczykij-gold-vault-and-iskra-promotion-boundary.md exists with a renumeration note, the old duplicate decisions/0023-wloczykij-gold-vault-and-iskra-promotion-boundary.md is absent, and Wloczykij inbound refs now point at ADR-0026 while Gemini refs still point at ADR-0023. Verification: full platformctl test suite passed with UV_CACHE_DIR=/tmp/platform-uv-cache PYTHONPATH=control-plane uv run --project control-plane --extra dev pytest control-plane/platformctl/tests -q -> 756 passed.

Closing as already implemented on current main. Evidence: `decisions/0026-wloczykij-gold-vault-and-iskra-promotion-boundary.md` exists with a renumeration note, the old duplicate `decisions/0023-wloczykij-gold-vault-and-iskra-promotion-boundary.md` is absent, and Wloczykij inbound refs now point at ADR-0026 while Gemini refs still point at ADR-0023. Verification: full `platformctl` test suite passed with `UV_CACHE_DIR=/tmp/platform-uv-cache PYTHONPATH=control-plane uv run --project control-plane --extra dev pytest control-plane/platformctl/tests -q` -> `756 passed`.
Sign in to join this conversation.
No labels
W6d-automerge-calibration
agent/claude-code
agent/codex
agent/hermes
agent/iskra
agent/ollama
agent/patchwarden
automerge-candidate
class/security-sensitive
cutover-gate
dependency/blocked
dependency/blocks-others
dependency/cross-repo
dependency/needs-confirmation
domain:agents
domain:ci
domain:docs
domain:forgejo
domain:infra
domain:memory
domain:runtime
domain:signal
domain:ux
flow/architecture
flow/blocked
flow/deployed
flow/done
flow/implementation
flow/intake
flow/maintained
flow/observed
flow/ready
flow/refining
flow/retired
flow/review
iterating
judge/codex-candidate
judge/hermes-candidate
judge/low-confidence
judge/needs-refinement
judge/operator-needed
judge/p0
judge/p1
judge/p2
judge/p3
judge/park
judge/patchwarden-candidate
judge/stale-priority
kind/adr
kind/bug
kind/chore
kind/feature
kind/infra
kind/ops
kind/refactor
kind/research
large-impact
merge/auto
merge/manual
merge/manual-dependency-conflict
merge/manual-failing-tests
merge/manual-merge-conflict
merge/manual-missing-review
merge/manual-operator-preference
merge/manual-red-zone
merge/manual-security-sensitive
merge/manual-unclear-scope
merge/manual-unknown
meta
mode:operator-only
mode:patchwarden-iskra-approved
mode:safe-auto
needs-operator-decision
needs-triage
not-ready
observed/erroring
observed/needs-followup
observed/pending
observed/retire-candidate
observed/unused
observed/used
operator-emotional
owner-attention
phase/02
phase/03
priority:p0
priority:p1
priority:p2
priority:p3
proposed
ready-for-agent
ready-for-operator
recovery
review:claude-reviewed
review:codex-reviewed
review:dziadek-reviewed
review:needs-human
risk/exposure
risk/process
risk/product
risk/runtime
safety:external-write
safety:no-prod-mutation
safety:prod-impact
safety:secret-touch
size/large
size/medium
size/small
size/tiny
size/unknown
source/adr
source/agent-generated
source/manual
source/operator-chat
source/voice-note
status:blocked
status:codex-ready
status:merged:pending-evidence
status:needs-evidence
status:operator-needed
status:parked
tier/full
tier/lite
tier/stacked
tier:0-platform-substrate
tier:1-iskra-value-layer
tier:2-tools-products-modules
type:bug
type:chore
type:docs
type:feat
type:policy
type:research
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
pdurlej/platform#756
No description provided.