Development record
2026-09-29 — Every new issue carries a remedy, and abcd's own automatic filers write one machine value when they have no fix (the product thinker's rulings BX3 and H12 of 2026-09-29, applied by lane remedyRequired of autonomous run A; partial of itd-82, whose decision 6 already required the field). BX3, verbatim: "REFUSE the filing; every new issue must carry remedy:". H12, verbatim: "'NO FIX YET' ALLOWED: automatic filers may write remedy 'none (filed automatically)'; the record is filed, drain skips it until a person writes a real remedy." As built: `capture` refuses a new issue with no remedy or a blank one, exit 2 and nothing written, naming `--remedy` and the machine value; the value is spelt once, `issueschema.MachineRemedy`, and written by every in-binary filer (the consistency pass, and an inbox report promoted without a remedy of its own, whose own remedy otherwise becomes the issue's); `abcd drain --dry-run` lists a record carrying it as ineligible, naming the automatic filer and the verb that answers it; and `capture remedy <iss-N> "<fix>"` writes or replaces the remedy on an open issue. A record filed before the rule carries none, stays readable and valid, and is listed as ineligible. The one-line capture friction that `commands/capture.md` and the principle `adversarial-review-scales-with-blast-radius` promised is tightened by the ruling, and both now say so. A person typing the machine value is REFUSED, by `capture --remedy` and by `capture remedy`, compared trimmed and case-folded: the value is useful only while it means that a machine filed the record, and a person has either a fix to name or the choice not to file; allowing it would let a hand-filed record pass as machine-filed and be skipped silently. A remedy chosen in an autonomous run cites its grounds, a prior-art or state-of-the-art check where the fix depends on outside practice (principle `prefer-sota`), in the capture's text; nothing checks that mechanically yet.
2026-09-29 — Every new issue carries a remedy, and abcd's own automatic filers write one machine value when they have no fix (the product thinker's rulings BX3 and H12 of 2026-09-29, applied by lane remedyRequired of autonomous run A; partial of itd-82, whose decision 6 already required the field). BX3, verbatim: "REFUSE the filing; every new issue must carry remedy:". H12, verbatim: "'NO FIX YET' ALLOWED: automatic filers may write remedy 'none (filed automatically)'; the record is filed, drain skips it until a person writes a real remedy." As built: capture refuses a new issue with no remedy or a blank one, exit 2 and nothing written, naming --remedy and the machine value; the value is spelt once, issueschema.MachineRemedy, and written by every in-binary filer (the consistency pass, and an inbox report promoted without a remedy of its own, whose own remedy otherwise becomes the issue's); abcd drain --dry-run lists a record carrying it as ineligible, naming the automatic filer and the verb that answers it; and capture remedy <iss-N> "<fix>" writes or replaces the remedy on an open issue. A record filed before the rule carries none, stays readable and valid, and is listed as ineligible. The one-line capture friction that commands/capture.md and the principle adversarial-review-scales-with-blast-radius promised is tightened by the ruling, and both now say so. A person typing the machine value is REFUSED, by capture --remedy and by capture remedy, compared trimmed and case-folded: the value is useful only while it means that a machine filed the record, and a person has either a fix to name or the choice not to file; allowing it would let a hand-filed record pass as machine-filed and be skipped silently. A remedy chosen in an autonomous run cites its grounds, a prior-art or state-of-the-art check where the fix depends on outside practice (principle prefer-sota), in the capture's text; nothing checks that mechanically yet.
Frontmatter
| id | dcn-2609290000000016 |
|---|---|
| type | decision |
| date | 2026-09-29 |
.abcd/work/decisions/dcn-2609290000000016-every-new-issue-carries-a-remedy-and.md
open on GitHub ↗ · commit history ↗
mentions2
- dcn-26101614254965372026-10-16 — A record the consistency pass files is outside the drain's promoted rule (facilitator-on-delegation, drain-many-accounts step 4): the pass writes into related_intents the two intents its contradiction is between, which are the finding's subjects and not intents that took the work on, so under the promoted rule its record would be handed back for good, against the product thinker's ruling H12 as dcn-2609290000000016 records it, that an automatic filer's record is filed and a drain passes it over only until a person writes a real remedy; such a record is skipped while it carries the machine remedy and may be taken by a drain once a person writes one. The record is told by the three fields the filer writes, category inconsistency, source agent-finding and a found_during opening "abcd intent consistency, finding ", which no other filer in the binary writes, and not by finding_ref, which a record the pass filed before keys existed lacks. This narrows the "no exception by source" of dcn-2610161401449155 by this one filer: every other issue whose related_intents names an intent, the after-merge audit's owed-check issue included, is still handed back as promoted (grounds: ruling H12; the filer's own fields in internal/core/capture/consistency.go; iss-2610161015370582).
- itd-82`abcd drain` fixes the issues that need no decision, and hands the rest back by kind