ADR-0173shipped

ADR Number Collision Remediation

Status: shipped
Date: 2026-02-28
Updated: 2026-02-28
Deciders: Joel Hooks
Related: ADR-0166 (documentation gardener system), ADR-0174 (vault ADR audit CLI)

Context

The ADR store had duplicate numeric IDs:

  • 0088
  • 0089
  • 0153
  • 0154
  • 0158

This made references ambiguous (ADR-0154 meant two different records) and weakened tooling checks.

Decision

Run a one-time renumber migration so ADR numeric prefixes are globally unique in ~/Vault/docs/decisions.

Canonical owners kept in place

  • 0088-nas-backed-storage-tiering.md
  • 0089-single-source-inngest-worker-deployment.md
  • 0153-pdf-brain-rest-api.md
  • 0154-content-migration-mdx-to-convex.md
  • 0158-worker-supervisor-binary.md (kept to preserve the Talon supersession chain in ADR-0159)

Renumbered ADRs

  • 0088-joelclaw-design-system-responsive-layout.md0175-joelclaw-design-system-responsive-layout.md
  • 0089-transcript-indexing-typesense.md0176-transcript-indexing-typesense.md
  • 0153-secret-redaction-network-intercept.md0177-secret-redaction-network-intercept.md
  • 0154-livekit-voice-worker-durability.md0178-livekit-voice-worker-durability.md
  • 0158-automated-skill-gardening.md0179-automated-skill-gardening.md

Migration requirements

  1. Update ADR titles/frontmatter IDs to match new filenames.
  2. Update internal references and README index.
  3. Enforce collision checks via joelclaw vault adr audit.

Consequences

  • ADR IDs are unambiguous again.
  • joelclaw vault adr collisions can gate future drift.
  • Talon supersession lineage remains coherent (01580159).