b.akery
The thirteenth loaf for software you didn’t write.
Your agent’s confidence is testimony. The commit history is evidence.
The thirteenth loaf.
Under the Assize of Bread, 1266, English bakers were fined, beaten or worse for selling a short dozen. The old story goes that they started adding a thirteenth loaf — not generosity, just standing proof they had not cheated.
b.akery is the thirteenth loaf for software you didn’t write.
Your agent tells you it fixed the bug, shipped the feature, wrote the tests. That is testimony, not evidence. b.akery reads your repository’s own history and reports where the same thing got fixed over and over — what the agent’s confidence actually cost you.
Every finding comes with one command you can run yourself. If you can’t reproduce it, it isn’t a finding.
Who it’s for.
Owners of software they did not write.
Where this is today.
On its first full audit the owner confirmed 17 of 20 assessable findings as real defects — 85%, on a repository the tool’s builder already knew, which is why that number comes with its caveat attached. It is one version of one detector reading one repository’s whole history. It is not a general accuracy rate, and no later version inherits it. Audits are run personally, three a week.
That 85% is bound to what produced it: detector v0.2.0, window
full history, dismissal state sha256:152929fa8e1c637c.
A precision figure quoted loose from the instrument that earned it is the kind of claim
this exists to catch, so ours is not quoted loose either.