Development record
The pace window clock and the locked JSON state file beside the runs exist twice in the implement loop: loop/drain.go keeps drain.json under drain.lock with window_started_at and next_eligible_at, and build next's series (loop/nextseries.go, landing with itd-2609211116005482) keeps next.json under next.lock with the same fields and the same window logic, copied because drain.go is mid-change under itd-82. Two copies is the point the one-canonical-primitive principle files it.
issueopenminoriss-2610111007107579
The pace window clock and the locked JSON state file beside the runs exist twice in the implement loop: loop/drain.go keeps drain.json under drain.lock with window_started_at and next_eligible_at, and build next's series (loop/nextseries.go, landing with itd-2609211116005482) keeps next.json under next.lock with the same fields and the same window logic, copied because drain.go is mid-change under itd-82. Two copies is the point the one-canonical-primitive principle files it.
Frontmatter
| id | iss-2610111007107579 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | minor |
.abcd/work/issues/open/iss-2610111007107579-window-clock-and-series-state-twice.md
open on GitHub ↗ · commit history ↗
mentions2
- itd-82`abcd drain` fixes the issues that need no decision, and hands the rest back by kind
- itd-2609211116005482`abcd build next` picks the readiest planned intent itself, and writes down why