Clearer Slack cards and changelog provenance
Get the newsletter
What shipped and what we're learning building Ballad, in your inbox. Unsubscribe any time.
We changed how Ballad asks for your attention in Slack, and how it shows its work.
Slack cards now lead with the decision. A new "Built from" section on each changelog entry lists the commits and PRs behind it. A new plan proposal supersedes the old ones, and digests name the change. Onboarding now works on sites that block Ballad's reader. And when a site's firewall is blocking Ballad, we flag it once as a high-priority site-audit finding.
Slack cards and digests
If you approve from Slack, the cards now lead with the decision. Each Inbox notice asks a question, shows what changes (now vs. proposed), gives one plain sentence of why, and says what happens if you do nothing. Two buttons: the decision (or Open) and Not now.
Only items that can't wait arrive on their own. The rest stay in the digest.
One plan change: a new plan proposal now closes that plan's other open proposals as superseded, so stale ones stop piling up in the digest. We've already cleaned up existing piles, keeping the newest proposal for each plan. Digests also name the actual change instead of repeating generic lines.
There's nothing to turn on.

See what a changelog entry was built from
When you review a changelog entry from the Release pipeline, in the Inbox pane or on the full page, it now opens with a collapsed Built from section. Expand it to see the commits behind the entry, grouped by the pull requests they belong to, plus any direct pushes. Each commit links to the repo and shows its subject, author, date and full message.
That lets you check that the entry matches what you actually shipped. Entries recorded by hand have no commits, so they show their own notes instead. There's nothing to turn on.

Sites that block Ballad's reader
If your site sits behind a firewall or a security plugin, Ballad's servers may not be able to read your homepage. Onboarding no longer stops at "Couldn't read that site" when that happens. It falls back to reading your site's pages through web search.
When a firewall or security plugin refuses Ballad's reader, Ballad flags it once as a high-priority site-audit finding. The finding names the rule to add: a Cloudflare skip rule, a Vercel bypass or a plugin allowlist. It's shown again in Settings.
Add the rule the finding names.