This is the record of an abcd-managed repository

abcdBetav0.16.2 · 2026-11-06

Development record

itd-40 lists an in-tree .abcd/ directory as a strong managed marker; the ahoy chapter says it does not make a folder managed on its own

issuewontfixminoriss-2610262033139821

itd-40 lists an in-tree .abcd/ directory as a strong managed marker; the ahoy chapter says it does not make a folder managed on its own

A premise contradiction (severity minor) found by the cross-document consistency pass.

  • End A: .abcd/development/brief/04-surfaces/01-ahoy.md:569 — "recorded as a signal and reported, but it does not make a folder managed on its"
  • End B: .abcd/development/intents/shipped/itd-40-folder-classification.md:33 — "a CLAUDE.md/AGENTS.md marker block, an in-tree .abcd/ directory, or an entry for cwd's root-commit SHA"

The folder-classification intent puts an in-tree .abcd/ directory among the strong markers that decide managed against unmanaged. The ahoy chapter says that directory is only recorded as a signal and a folder holding nothing but .abcd/ reports as unmanaged-folder (iss-88). Under one rule a bare .abcd/ folder classifies as managed-repo and under the other as unmanaged-folder, so a classifier cannot follow both.

Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 376.

Grounds

  • declined: Closed in the 2026-10-27 triage (dcn-2610271112330536): a later record already settles which end holds. Ahoy cites iss-88 for the narrowing, so a later record already says which rule holds; the shipped intent states the earlier rule.

Frontmatter

idiss-2610262033139821
typeissue
lifecyclewontfix
severityminor

References1

mentions2