Principles
Six rules we hold ourselves to.
They shape the product, this website, and what we will and will not say about either. A verification company should be the easiest company in its market to check.
- 01 / 06
No proof, no pass.
A PASS means at least one behaviour was executed and the approved rules held. When the evidence is not there, the answer is UNKNOWN, and UNKNOWN is never shown as a pass.
- 02 / 06
People approve the rules.
Rules change only through your normal review, and Bracel reads them from the base commit. The tool that judges a change does not let that change rewrite the judgement.
- 03 / 06
Your code stays where it runs.
In customer-CI mode, every check runs in your own GitHub Actions. We designed it so that we never need your source code, and we state data claims only for the configuration we tested.
- 04 / 06
Say what was checked, and what was not.
Every result names the rule, the scenario, what was expected and what was observed. A PASS covers only what it lists. NOT_APPLICABLE means nothing was checked, and it says so.
- 05 / 06
Claims follow evidence.
We label illustrative examples as illustrative. We do not publish customers, logos or numbers we cannot back. When we publish error rates, each will come with its numerator, denominator, cohort and period, and fewer than 20 cases will be reported as insufficient data.
- 06 / 06
An incorrect PASS is a security issue.
A defect that can produce an incorrect PASS gets a fixed release, direct notice to affected teams, and withdrawal of the affected rule template. A confirmed incorrect PASS pauses new sign-ups and promotion until the fix ships.