Changelog
What is inside Bracel.
Seven verification areas, five language tracks, persistent-state observation and a controlled repair workflow. Each result stays connected to the code and rule that produced it.
-
AddedVerification
- Sequence & state: Only valid transitions may change a record.
- Concurrency & races: Competing requests must preserve the same invariant.
- Retries & duplicate effects: Repeating a request must not repeat its business effect.
- Authorization & tenancy: Access must respect ownership, roles and revoked permissions.
- Partial failure & recovery: A failed operation must not leave an invalid partial result.
- Evaluation integrity: The change under test must not redefine its own judge.
- Reproduction & diagnosis: A finding must include enough context to reproduce it.
AddedLanguage tracks
- Node / TypeScript
- Python
- Java / JVM
- Go
- C# / .NET
AddedPersistence
- PostgreSQL and MySQL per language track
- Defined Redis scenarios with explicit observation and fault capabilities
AddedEvidence
- Approved base-commit rules; execution ID and exact tested SHA
- Scenario inputs, observations, verdict reasons, trust class and replay context
AddedControlled Fix
- Explicit model-sharing consent and customer-owned model key
- Protected evaluator paths, independent held-out verification and customer checks
- Reviewable diff and human approval; no automatic merge
Support belongs to a declared execution profile. A passing scenario is never a claim that every possible behavior is correct.
How we announce
An incorrect PASS is a security issue.
- 01
Affected teams are notified directly, not only through this page.
- 02
A fixed release ships, listed here with what it fixes.
- 03
The affected template version is withdrawn. A check that still names it reports UNKNOWN with
template-withdrawn. - 04
New sign-ups and promotion pause until the fix ships. Principles