Skip to content

[medium] Make ADR supersession identifiers unambiguous #416

Description

@SUaDtL

Finding

The repository contains two ADR files numbered 0014:

  • 0014-pi-host-authentication-and-fail-closed-tool-boundary.md
  • 0014-githook-shim-dropin-fail-closed.md

Later ADR frontmatter can only say supersedes: 0014. ADR-0015 and ADR-0016 therefore have ambiguous machine-readable supersession metadata even though their prose is clear.

Impact

/ca-adr-status and other forward-chain tooling cannot identify the intended predecessor reliably by number alone.

Required resolution

Define a forward-compatible unique ADR identity or disambiguation rule, migrate the duplicate chain without rewriting historical decisions silently, and add parser/status tests covering duplicate legacy numbers.

Metadata

Metadata

Assignees

No one assigned

    Labels

    sev:medTribunal/triage: medium severity

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions