Hi,

This release, in numbers

Tests keep outnumbering code — 48,658 lines of tests against 47,626 of code — and 41% of this cycle went to fixing what was already shipped, not to building anything new. I'd rather say that than spin it.

The pipeline stops re-doing delivered work

A merged ticket used to get spawned again fifteen seconds later, with a new timer running against work that was already done — three times in two days, because the spawn chokepoint graded it owned-in-lane and only logged that. It refuses now, before the tmux session, the model process or the billable timer start. A push that would void a GOLDEN review is refused too, with the cost named and a recorded reason required to proceed, and a hotfix that lands on main comes down into the open release lane by itself instead of sitting there for hours.

Sprints carry their dates

A sprint can no longer exist without a begin date and an end date — every door that creates one now checks, and the audit reads every ticket a sprint has, open and closed, not just the open ones. A ratified plan now lands paved — documents and a DAG, no dates yet — and one command fires it into a dated sprint with its epic and tickets, asking the begin date first; and the "Plans ready to fire" shelf now lands with every install and update instead of waiting on two commands typed by hand. And a finished container — an epic, a milestone, a sprint, an initiative — closes itself the moment every child is done; nobody has to ask, and nobody has to remember to.

Screens that explain themselves

Press ? inside the Gantt and a legend opens for every glyph and header term it draws with; b filters the Gantt the same way it already filters the War Room. And the War Room's own title row now says whether its data loaded — a glyph and a word, never colour alone — names what's missing when a read fails, shows — instead of a quiet zero for anything that depends on it, and r reloads the whole board in place without losing your cursor, scope or filters.

Colado

Colado is a jiu-jitsu term for a position with no gaps — justo, perfectly adjusted, full pressure. It's the name we gave the FlowForge gates that leave no space between the rule and your work. This release closes five more gaps, each one a door that now refuses instead of a line that only logged: a delivered ticket can no longer be spawned again, a push can no longer silently void a GOLDEN review, a sprint can no longer be created without its begin and end dates, a release can no longer be cut without its letter or a recorded reason, and the commit-message wall can no longer refuse commits the base already holds.

Small things that change everything

Not every change earns a headline. These fit in a line each, and you feel them every day.

Marking a radio favourite with f used to write to disk and tell you nothing back — a second press silently un-marked it. It works now, on the first press. A shelf sprint used to read ○ unknown and repeat its own date inside its name; it reads as a sprint, plainly, and the name says the rest once. And flowforge doctor now reads whether Claude Code's own outside-the-working-directory prompt is armed on your machine, because a worker nobody is watching can otherwise sit at that prompt until a human answers it.

One setup step

Release Letters sends only what you configure. With nothing set, the cut still hands you a .eml — that is the whole delivery. A send needs a sender (a Resend key or your own SMTP relay), and a letter with images needs an image host; recipients and unsubscribe complete it. Each is set in Settings → Release Letters or with flowforge marketing set, and flowforge doctor names whatever is still missing.

Not yet

The Release Letters tab's own "send a test to me" button isn't wired yet — the sender itself is built, and flowforge marketing test sender sends that one test message from the command line. The voice preview, and the rail spectrum following ACE's real voice as it speaks, both still wait on a speech-engine release. And get.flowforgesoft.com/ on its own still answers an access-denied page; the redirect to the releases page is written and waits on its own infrastructure change.

How this letter reaches you

This letter comes out of FlowForge's own release pack — the same tooling that keeps the release notes, the deck and this letter itself derived from one committed source. The same pipeline — render, export to .eml, send at promote — is now in your own Settings, opt-in and off by default.

Unsubscribe from release letters · Manage preferences · Privacy

FlowForge · v1.2.23 · sheet 1/1