This is the record of an abcd-managed repository

abcdBetav0.16.2 · 2026-11-06

Development record

the lifeboat licence gate's allowlist is named .abcd/launch-allowlist.json; launch says that allowlist and release packaging are two mechanisms never given one name

issuewontfixnitpickiss-2610262032542009

the lifeboat licence gate's allowlist is named .abcd/launch-allowlist.json; launch says that allowlist and release packaging are two mechanisms never given one name

A naming conflict (severity nitpick) found by the cross-document consistency pass.

  • End A: .abcd/development/brief/04-surfaces/04-launch.md:483 — "Two mechanisms, never one name."
  • End B: .abcd/development/brief/05-internals/09-provenance-substrate.md:89 — "unless .abcd/launch-allowlist.json explicitly names it"

04-launch says the restrictive-licence gate is the lifeboat's, not the release artefact's, and that the gate's evaluation-input allowlist and packaging are two mechanisms, never one name. 09-provenance names that lifeboat gate's allowlist .abcd/launch-allowlist.json, beside a .abcd/launch.allow, so the lifeboat's mechanism carries launch's name, the conflation launch's rule exists to prevent.

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

Grounds

  • declined: Closed in the 2026-10-27 triage (dcn-2610271112330536): the two ends do not conflict when read in full. Launch's rule bars one name for two mechanisms; 09-provenance keeps them distinct by name and says so, and the gate itself is unbuilt, so a shared file-name prefix is not the conflation the rule forbids.

Frontmatter

idiss-2610262032542009
typeissue
lifecyclewontfix
severitynitpick

mentions1