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.
I2000 · intent-bound-work · p1 · wave 0
What a piece of work serves is one derivation, with a revision
Add Intents::binding over the preflight: the work named by an issue, an intent, paths or a declared exemption resolves to a standing (bound, maintenance, exempt, refused), the intents and criteria served, and two pins of what was resolved — plan_revision, a hash of each served intent's statement, invariants and criteria, the links that reach it and its critique, and evidence_standing, a hash of the served criteria's evidence states; answer it as the read-only capability intents.binding on the command line, HTTP and MCP.
- Depends on
- none
- Blocked by
milestone:intent-bound-work- Scope
apps/majordomus-cli/src/intent_binding.rsapps/majordomus-cli/src/intent.rsapps/majordomus-cli/src/policy.rsapps/majordomus-cli/src/capability/builtin/intents.rsapps/majordomus-cli/src/commands/intent.rsapps/majordomus-cli/src/cli.rsand 5 more- Evidence
- 0 of 4
- 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.