Bernstein v3.23.0 makes artifact checks gate signed success receipts
GitHub's release record timestamps the update to October 24th at 18:29. The release enforces declared artifact criteria, adds audited administrative runs and flags an unresolved Python 3.12 test failure.
By Ryan Merket · Published
Primary source: Hacker News
Why it matters
As coding agents take on parallel work, teams need to decide what evidence should be required before machine-written changes merge. Bernstein makes that control layer inspectable and self-hostable. Its README describes the project as beta and solo-maintained, so teams weighing adoption also have to consider maintenance continuity.
Alex Chernysh's open-source Bernstein scheduler shipped v3.23.0 on October 24th at 18:29, according to the GitHub release record, which marks it as the latest release and lists 105 changes since v3.22.0. The release notes say its headline fix enforces criteria declared in 'artifact_spec' alongside completion signals: a failed criterion cannot produce a signed success receipt.…
When you purchase through links in our articles, we may earn a small commission. This doesn’t affect our editorial independence.