Development record
2026-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).
2026-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).
Frontmatter
| id | dcn-2610161835529757 |
|---|---|
| type | decision |
| date | 2026-10-16 |
.abcd/work/decisions/dcn-2610161835529757-a-drain-plan-read-from-a-commit-reads.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).
- spc-2610161044461448drain-many-accounts