A snapshot: read at commit 707a04c7ce8 on 2026-10-18T00:01:48Z by majordomus 0.29.0. Nothing on this page is read again. See it live
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.
I1900 · intent-lifecycle · p1 · wave 0
An intent is a typed record whose stage and satisfaction are derived
Deliver slice 1 of the intent-lifecycle milestone: the intent kind and schema, the read-only capabilities intent.list, intent.record, intent.validate and intent.preflight on every surface, and the intent-check gate.
- Depends on
- none
- Blocked by
- none
- Serves
intent-lifecycle#stage-is-derivedintent-lifecycle#surfaces-agreeintent-lifecycle#model-is-gated- Scope
apps/majordomus-cli/src/intent.rsapps/majordomus-cli/src/capability/builtin/intents.rsshare/schemas/majordomus/intent.ai/repo/project/intents.ai/repo/ci/gates.yaml- Evidence
- 0 of 2
- Started
- not yet
- Verified
- not yet
- Completed
- not yet
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.