Development record
The product thinker, ruling on 2026-10-15 at about 20:15 BST that a pull request waiting on a person holds its reservation for a day (iss-2610152020234609), also asked for this to be captured: if the one-day hold still leaves people duplicating work, count an open pull request for a record as holding it too. Today the pick judges a record held only by its reservation on the shared remote, as last fetched; an open pull request for the record does not hold it. A pull request still waiting after its day, with nothing renewing it, leaves the record open to a colleague's drain. Reading open pull requests at pick time would close that gap, at the cost of a forge call when the pick runs, which breaks the offline pick invariant 7 keeps today. This stays open until the one-day hold is seen to fall short.
The product thinker, ruling on 2026-10-15 at about 20:15 BST that a pull request waiting on a person holds its reservation for a day (iss-2610152020234609), also asked for this to be captured: if the one-day hold still leaves people duplicating work, count an open pull request for a record as holding it too. Today the pick judges a record held only by its reservation on the shared remote, as last fetched; an open pull request for the record does not hold it. A pull request still waiting after its day, with nothing renewing it, leaves the record open to a colleague's drain. Reading open pull requests at pick time would close that gap, at the cost of a forge call when the pick runs, which breaks the offline pick invariant 7 keeps today. This stays open until the one-day hold is seen to fall short.
Frontmatter
| id | iss-2610152026530442 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | minor |
.abcd/work/issues/open/iss-2610152026530442-open-pull-request-holds-its-record-at.md
open on GitHub ↗ · commit history ↗
mentions1
- iss-2610152020234609The product thinker ruled on 2026-10-15, at about 20:15 BST: a pull request the land step leaves waiting on a person holds its reservation on the shared remote for a day, mirror or not. Today the land fence (fenceLease in internal/core/implement/loop/reservation.go) renews for lease.Max only where the checkout has a ruleset mirror (.abcd/work/rulesets/), and for the two-hour lease.Default otherwise, per decision 29 and criterion C44 of itd-2609091034175565 (spc-2610031753359849). Without a mirror, a pull request that is only waiting to merge loses its reservation two hours after the fence unless something renews it, and a colleague's drain can then take the record and redo the work.