This is the record of an abcd-managed repository

abcdBetav0.16.2 · 2026-11-06

Development record

itd-2610141956319695 defines a deferral as capturing a finding as its own record; the capture surface's deferral is a waiver written onto an existing open record past one cut

issuewontfixminoriss-2610262034081102

itd-2610141956319695 defines a deferral as capturing a finding as its own record; the capture surface's deferral is a waiver written onto an existing open record past one cut

A terminology drift (severity minor) found by the cross-document consistency pass.

  • End A: .abcd/development/intents/disciplines/itd-2610141956319695-a-deferred-finding-is-its-own-captured.md:20 — "A deferral is always a capture. There is no exception."
  • End B: .abcd/development/brief/04-surfaces/06-capture.md:327 — "writes the release cut's waiver onto an open record"

Under itd-2610141956319695 a deferral is always a capture: a deferred finding becomes an open issue of its own. The capture surface's deferring writes the release cut's waiver onto an open record that already exists, for a major or critical grade only, and carries it past one cut. A receipt reading deferred and a record carrying a deferral therefore name different acts under one word.

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

Grounds

  • declined: Closed in the 2026-10-27 triage (dcn-2610271112330536): the two ends do not conflict when read in full. The two statements can both hold: a deferred finding names an open issue record, and a major or critical record may then be waived past one cut. The shared word is an overlap, not a conflict; a one-line cross-reference in either document would help but is not owed.

Frontmatter

idiss-2610262034081102
typeissue
lifecyclewontfix
severityminor

References1

mentions1