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.
I2417 · public-proof · p1 · wave 0
The landing page is a click-through story: an editorial hero and an evidence chain a visitor steps through
Give the homepage the editorial typography and the click-through interactivity of the prismatic case reports: a serif display hero and section heads, and an interactive evidence chain in the proof section — what the repository declares, what the registry generates, the interfaces it reaches, the rules a machine decides, the guaranteed claims, the executable use cases and what a recorded run supports — in which every node is a button that opens its figure, its sentence and its source, and every edge is solid where a machine holds the link and dashed where it is declared and awaits evidence.
- Depends on
- none
- Blocked by
- none
- Unblocks
- none
- Serves
- none
- Scope
site/templates/index.htmlsite/templates/components.htmlsite/templates/partials/evidence-chain.htmlsite/data/marketing.tomlscripts/lib/interaction-specs/evidence-chain.mjs- Evidence
- 0 of 1
- 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.