2026-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).

Frontmatter

.abcd/work/decisions/dcn-2610161425496537-a-record-the-consistency-pass-files-is.md
open on GitHub ↗ · commit history ↗

mentions6

• adr-2609291342092738A drain takes an issue alone only when its fields say it needs no decision
• dcn-26092900000000162026-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.
• dcn-26101614014491552026-10-16 — An issue an after-merge audit files is handed back as promoted (facilitator-on-delegation, drain-many-accounts step 4): the owed-check issue names its audited intent in related_intents, so the promoted rule of invariant 19 hands it back to that intent whatever its severity, and its check is paid through abcd intent audit rather than by a drain lane; this replaces the as-built note of dcn-2609300000000027 that an undecided audit's minor inconsistency is one the drain takes, which was the lane's reading and not part of ruling DQ1c, and keeps the rule field-only with no exception by source (grounds: the spec's wording for the rule, dcn-2610161040365515, and one rule over special cases; iss-2610161015370582)
• dcn-26101618355297572026-10-16 — A drain plan read from a commit reads the intent store from that commit too (facilitator-on-delegation, drain-many-accounts review round): the promoted rule's question for a record the consistency pass filed (which intents name it back in related_issues) is answered from the intent store as origin's default branch holds it at the commit the plan read the ledger from, read through one bounded cat-file batch and parsed as intent.Load parses the checkout's, so a checkout behind origin never hands such a finding to a lane that an intent on origin owns, and a draft half-written in the checkout never refuses a plan read from origin; the checkout's store is read only for a plan that reads the checkout's ledger, and a commit's store that cannot be read, or holds a malformed intent, refuses the plan as the checkout's would (grounds: spc-2610161044461448 steps 1 and 4; ruling H12, dcn-2610161425496537; the review of steps 1 to 18).
• iss-2610161015370582A drain's hand-backs and judgements live only in the checkout that made them: routeHandBack promotes the issue to an intent draft in that checkout, uncommitted, then the release pushes a tombstone so the issue reads free everywhere, and eligibility ignores related_intents, so every other account's drain judges or works the same issue again and promotes it to its own draft id.
• itd-2610161016394967Drains on several accounts share the work