PR Drain
Pull requests converging on master, one at a time.
Every open pull request as the integration lane assessed it: what it waits for, what would move it, what it depends on and overlaps, and the issue it carries.
- Issues ready86plan.status /counts/by_status/READY
- Issues active1plan.status /counts/by_status/ACTIVE
- Issues blocked159plan.status /counts/by_status/BLOCKED
- Issues done161plan.status /counts/by_status/DONE
Issue
One issue of the plan, as the plan records it.
I2398 · development-runtime · p1 · wave 0
A derive offloaded to another machine waits its turn in a declared queue
Make the derive offload a capability of the executable: the hosts and their limits declared once under .ai/repo, the host chosen by free disk and queue length, a FIFO queue on the host in which a dead waiter's ticket blocks nobody, a build directory of each derive's own, and the bundle-in/bundle-back round trip with its refusals, tested without a network and documented.
- Depends on
- none
- Blocked by
- none
- Unblocks
- none
- Serves
- none
- Scope
.ai/repo/offload/derive.yaml.ai/repo/offload/README.mdshare/schemas/majordomus/derive-offload/derive-offload.v1.schema.jsonshare/kinds.yaml.ai/repo/knowledge/sources.yamlapps/majordomus-cli/src/offload/mod.rsand 14 more- Evidence
- 2 of 2
- Started
- 2026-10-14 07:59:13Z
- Verified
- not yet
- Completed
- 2026-10-14 07:59:22Z
plan.issues0 msAPI/api/v1/plan/issuesMCPmajordomus_plan_issuestechnical view
Pull-request drain
The integration lane asks the forge for every open pull request; this takes a while and arrives after the screen.