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.
I0801 · M003 · p1 · wave 0
Narrow the Clean Extraction Boundary and record what was adopted
Rewrite the Clean Extraction Boundary in docs/DESIGN.md so that it permits a generic deterministic provenance graph derived from this repository's own artifacts while continuing to exclude everything it excludes today, and record in docs/EXTRACTION_REPORT.md which architectural ideas from the studied prior art were adopted by re-derivation and which were refused, each with its reason.
- Depends on
- none
- Blocked by
- none
- Unblocks
I0807- Serves
- none
- Scope
docs/DESIGN.mddocs/EXTRACTION_REPORT.md- Evidence
- 1 of 1
- Started
- 2026-09-04 15:37:53Z
- Verified
- not yet
- Completed
- 2026-09-04 15:40:54Z
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.