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.
I2075 · a-session-leaves-what-it-observed · p1 · wave 2
A candidate is routed by what it is about
Derive route for every observation candidate from its subject, in ADR 0118's order: command:, capability:, rule:majordomus.*, the vendored rules directory, or the tool's share/ when inside the repository -> platform; another rule: or gate: -> enforcement; a path the scope declares generated or .gitattributes marks merge=derived -> generator; docs/ -> documentation; anything else -> project.
- Depends on
I2074- Blocked by
- none
- Unblocks
- none
- Scope
lib/knowledge.shlib/changed.shdocs/KNOWLEDGE.mdtest/cases/982_a_candidate_is_routed_by_what_it_is_about.sh- Evidence
- 1 of 1
- Started
- 2026-10-14 23:33:12Z
- Verified
- 2026-10-14 23:33:18Z
- Completed
- 2026-10-14 23:33:27Z
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.