Development record
abcd's own drain rule (adr-2609291342092738) holds abcd at the strict baseline, taking nitpick and minor and handing every security issue back, and a test pins it there, so urgent fixes that need no decision wait for a person. The product thinker ruled on 2026-10-16 that abcd's own repository takes every severity and security, most urgent first.
issueopenminoriss-2610161655393137
abcd's own drain rule (adr-2609291342092738) holds abcd at the strict baseline, taking nitpick and minor and handing every security issue back, and a test pins it there, so urgent fixes that need no decision wait for a person. The product thinker ruled on 2026-10-16 that abcd's own repository takes every severity and security, most urgent first.
Frontmatter
| id | iss-2610161655393137 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | minor |
.abcd/work/issues/open/iss-2610161655393137-abcd-s-own-drain-rule.md
open on GitHub ↗ · commit history ↗
mentions3
- adr-2609291342092738A drain takes an issue alone only when its fields say it needs no decision
- iss-2611050840338995A running drain's own order is fixed: category, then severity, then its tie-breaks (orderEligible in internal/core/capture/eligible.go), and its flags can only hold an issue back (--skip), so it cannot be told which eligible issue to take first. The route a person has today is to build one issue themselves with `abcd build <iss-N>` (internal/surface/cli/build.go:102), under the same drain rule. Inside a running drain, an issue a person or a release cut wants sooner waits behind every eligible issue ahead of it.
- itd-2610301750162657abcd's unattended work is spot-checked against specs and intents