What shipped
Gathered from what merged.
Every project keeps one rolling next-release board. It gathers what merged in every repository the release spans, the server counts the facts, the AI writes the prose, and one notes document leaves in the shape each of its readers needs.
01
One window, every repository
A release is a window over what merged. In each repository it starts at the commit that repository's part of the last release ended at — never at a date guess — so a release across a web app, an API and a mobile app still reads as one page.
- Every bound repository — a new release track takes every repository bound to the project, each on its own branch. A pull request link names its repository, so two repositories' #123 never mix.
- Facts from the server, prose from the AI — the stats strip, the pull request links and the boards the window touched are computed from what was actually swept; the AI writes the hero and the new, fixed and improved entries. A count never travels through a model.
- Refresh, then cut — ↻ refresh sweeps GitHub and regenerates only the AI's own cards, never what a person put on the board. ✂ cut freezes the board as the release and opens the next window where each repository's part ended.
02
The best screens, not the last ones
Each entry carries at most one screenshot, picked from up to 24 candidates: the screens captured inside the window and the runner and upload shots on the boards it touched. No screenshot appears twice: a shot two entries want goes to the one its board is evidence for.
- Scored on its pixels — a visual score computed in the server's own code — no model and no network, so an air-gapped install keeps it — sends blank and noisy frames down the order, and a screen whose text reads as an error sinks with them.
- Ranked for this release — quality, relevance to the window's pull requests and freshness decide the order, and near-duplicates drop out — one per route and device.
- Made this sprint — each entry links up to three of the boards behind it, and portals to up to 24 boards the window touched sit under the entries, so the evidence stays one click from the line it backs.
03
One document, every reader
The full notes are a document of their own, and the release links it: the board shows a preview beside the stats, and the Release section of the project's brief opens it. Its register is made for a release — chapters, KPI tiles, screens as galleries.
- Galleries and compare charts — screens sit in a bento, masonry, carousel or grid gallery instead of a stack of figures, and a number that moved is drawn as a before-and-after compare chart.
- Tagged by audience — a block can be written for the public, for engineers or for the team. The reader picks Everyone, Public, Technical or Internal in the viewer, and the blocks written for the others drop away.
- Leaves as PDF, HTML, Email or Word — every export keeps the audience the reader picked, so the customer's copy and the team's come from one source. The server produces PDF, Email and Word and records each export in the audit log.