Kolaboro / Engineering / Shipping log
We ship every day. Here is the record.
Every day since the first commit of kolaboro.com, counted from the git history of the live site: what changed, how many changes, and how they reached you. Nothing on this page is typed by hand.
Every day since the first commit
One square per UTC day, darker when more changes shipped. Choose a day to see what shipped, in plain English and as the original commit subjects.
Loading the shipping log…
Source: commits on the live branch (pub/_lovable) that change the site (_s/kolaboro.com/) or its server code (the kolaboro worker modules). A ship is a commit made by a person or by Claude working for one; commits made by our scheduled workflows are counted separately as data updates, and rollbacks by the deploy guard as rollbacks. Days are UTC. The streak counts consecutive days with at least one ship; today counts once something ships. The full repository is private; the commit ids are shown so changes can be dated. Commit subjects pass a privacy filter first: no project names, web addresses or emails.
Day by day
Once a day is over, Claude (claude-sonnet-5-5) turns that day's commit subjects into 3 to 6 lines a buyer can read. Code then checks that every line maps to at least one commit of the day (the ids are shown) and contains no number that is not in those commits; otherwise the page falls back to the day's own commit subjects. Days without a page written by a person get an automatic day page in the changelog, marked as such.
Engineering numbers, live
How changes reach the site, how often they are checked, and whether the site stayed up.
Roadmap, checked against the live site
Items on the roadmap link to the page that delivers them. Every night the job fetches each linked page; an item counts as shipped only when that page answers, is the page it claims to be, and contains the item's marker text. Items without a delivering page are not linked and keep the status we gave them by hand.
Loading…
Feeds and badge
Daily summaries as Atom and JSON Feed 1.1, and the raw data as /data/shipping.json.
<a href="https://kolaboro.com/shipping/"><img src="https://kolaboro.com/api/x/ship/badge.svg" alt="Kolaboro: shipped today and daily streak"></a>
The badge is drawn from the same data, may be embedded anywhere (CORS open) and is cached for 5 minutes.
Limits: the data is rebuilt every hour, so today's count can be up to an hour behind. A commit is a unit of work, not a measure of size: one commit can be a typo fix or a new tool. Deploy numbers start when the deploy guard started (3 November 2026). How it is built: GitHub Actions reads the history without file contents, writes this data and the feeds, and publishes them to the live branch like our other data jobs. See also Engineering, System status and Changelog.