Buzz vs BAND
Public record

Corrections

Last verified: 2026-08-23

3 corrections are on the record, newest first. A correction is anything this site published and later changed: a moved verdict, a wrong figure, a restated claim. Product changes that move a score are not corrections and live in the changelog.

What gets a correction?

Three kinds, printed on every entry. A verdict change moves which product leads. A figure correction moves a number, a price, a limit, or a date. A wording correction fixes a claim that was true but stated badly. Every entry names the old value, the new value, the reason, and the routes it touched. Nothing is edited silently.

FIGURE CORRECTED2026-08-23

Verification dates are now per item, not one site-wide date

Was
Every cell and source displayed the site verification date of 2026-08-19, which overstated how recently some sources had been read.
Now
Each score cell and each source carries its own date. Anything past 90 days renders amber and appears in the recheck queue on the evidence log.
Why
A single date implied a sweep that did not happen. Three cells rest on sources last read in April, May, and June, and readers should see that on the cell.

Routes touched: /evidence, /buzz-vs-band, /reviews/buzz, /reviews/band ยท Cells: Buzz Model flexibility, Buzz Community and docs, BAND Community and docs

WORDING2026-08-23

Publisher entity and contact address published

Was
The footer, about page, and disclosures carried placeholder publisher and contact values.
Now
Signalbox Bench is named as the publisher and corrections@buzzvsband.com is the contact address on every page.
Why
Scored claims need a named publisher and a working address, or they are opinions with a table around them.

Routes touched: /about, /disclosures, /corrections

VERDICT CHANGE2026-08-19

Default weights moved to a fleet-operator profile, and the verdict changed with them

Was
Repo-operator weights were the published default and Buzz led 6.8 to 6.4.
Now
Fleet-operator weights are the published default and BAND leads 6.9 to 6.4. The retired profile stays published on the methodology page and in the weight console.
Why
The reader this site is written for already runs agents in more than one framework and is buying an interaction layer on purpose. Weighting a git-native loop and self-hosting first described a different reader. No score cell moved: only the weights.

Routes touched: /, /buzz-vs-band, /best-agent-workspace, /how-we-test

How do I report an error?

Write to corrections@buzzvsband.com with the route, the sentence, and the source that contradicts it. Signalbox Bench answers inside five working days. If the source wins, the entry appears here the same day the page changes, and the score cell carries a fresh verification date on the evidence log.