deslop(governance): resolve duplicate ADR-0023 (renumber wloczykij to 0026) #730

Closed
opened 2026-06-05 14:45:48 +02:00 by claude · 1 comment
Collaborator

From the 2026-06-05 deslop audit (HIGH — governance integrity).

Problem

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

  • decisions/0023-gemini-3-5-flash-reviewer-cousin.md
  • decisions/0023-wloczykij-gold-vault-and-iskra-promotion-boundary.md

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

Fix

Renumber the wloczykij one (keep gemini as 0023, it's the more-referenced):

  1. Rename decisions/0023-wloczykij-gold-vault-and-iskra-promotion-boundary.mddecisions/0026-wloczykij-gold-vault-and-iskra-promotion-boundary.md.
  2. Add a "Renumeration note" mirroring ADR-0010's format (was 0023, renumbered to 0026 on 2026-06-05 to resolve a duplicate-number collision).
  3. Update the inbound refs that mean 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. Leave the 3 gemini-meaning ADR-0023 refs pointing at 0023: MAP.md:105, state/strategy/memory-control-plane-2026-05-24.md:200, policies/agent-capabilities.yaml:16.

Note: the ADRs' internal Date headers are 2026-05-24 (gemini) / 2026-05-19 (wloczykij); 2026-05-28 is only the file mtime.

Acceptance

  • No two ADR files share a number.
  • Every bare ADR-0023 ref resolves unambiguously to gemini; wloczykij refs point at 0026.
  • Renumber note present.

Authored from the deslop audit (claude). Execution = Codex.

From the 2026-06-05 deslop audit (HIGH — governance integrity). ## Problem **Two distinct ADRs both numbered 0023**, both `Status: Accepted`, neither carrying a renumber note — a regression against the documented 0006→0010 / 0007→0011 renumber discipline: - `decisions/0023-gemini-3-5-flash-reviewer-cousin.md` - `decisions/0023-wloczykij-gold-vault-and-iskra-promotion-boundary.md` Inbound bare `ADR-0023` refs already resolve ambiguously to both. ## Fix Renumber the **wloczykij** one (keep gemini as 0023, it's the more-referenced): 1. Rename `decisions/0023-wloczykij-gold-vault-and-iskra-promotion-boundary.md` → `decisions/0026-wloczykij-gold-vault-and-iskra-promotion-boundary.md`. 2. Add a "Renumeration note" mirroring ADR-0010's format (was 0023, renumbered to 0026 on 2026-06-05 to resolve a duplicate-number collision). 3. Update the inbound refs that mean **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. Leave the 3 **gemini**-meaning `ADR-0023` refs pointing at 0023: `MAP.md:105`, `state/strategy/memory-control-plane-2026-05-24.md:200`, `policies/agent-capabilities.yaml:16`. Note: the ADRs' internal Date headers are 2026-05-24 (gemini) / 2026-05-19 (wloczykij); 2026-05-28 is only the file mtime. ## Acceptance - [ ] No two ADR files share a number. - [ ] Every bare `ADR-0023` ref resolves unambiguously to gemini; wloczykij refs point at 0026. - [ ] Renumber note present. *Authored from the deslop audit (claude). Execution = Codex.*
Collaborator

Picking up as codex; scope is ADR renumber + inbound refs only. I will use a short Ollama/AntiGravity scout pass on a sanitized packet, then implement locally. No runtime mutation, no secrets, no deploy.

Picking up as codex; scope is ADR renumber + inbound refs only. I will use a short Ollama/AntiGravity scout pass on a sanitized packet, then implement locally. No runtime mutation, no secrets, no deploy.
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#730
No description provided.