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.
I0901 · fly-deployment · p0 · wave 0
The deployment description is a kind of the layer, not a provider file
Register `deployment` as a kind of the AI layer — allowed keys, schema, directory contract — and describe this repository's own deployment as one object under .ai/repo/deployments/, so that every later projection reads one file and no provider file is ever authoritative.
- Depends on
- none
- Blocked by
- none
- Serves
- none
- Scope
.ai/repo/deploymentsshare/kinds.yamlshare/allow/deployment.txtshare/schemas- Evidence
- 4 of 4
- Started
- 2026-10-04 09:55:21Z
- Verified
- 2026-10-04 09:59:52Z
- Completed
- 2026-10-04 10:00:11Z
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.