Compare
Four checks. Four different questions.
Bracel does not replace what you already run. It makes an approved business rule an explicit execution contract, with observations and scope attached to the result. Other tools may detect the same defect; compare actual findings under matched conditions.
| Question | Code review | Tests you write | Static analysis | |
|---|---|---|---|---|
| The question it answers | Does this change look right? | Do the cases someone wrote still pass? | Does the code match a known pattern? | Does the business rule still hold on this change? |
| Runs your application | Depends on the review workflow and tools | Yes, for the cases written | Usually analyzes code without starting the application | Yes, within its admitted execution profile |
| Knows your business rule | When supplied as review context | When encoded in a test | When encoded in a supported rule | The explicitly approved execution contract |
| Where the rule lives | In people’s heads | Next to the code it tests | In the tool’s rule set | In a rules file on your default branch |
| Can the change edit its own judge? | — | Yes, tests change in the same pull request | Configuration can change with the code | No. Rules are read from the base commit |
| When it cannot tell | Workflow-dependent; review may be inconclusive | Depends on assertions, skip and failure handling | Depends on analyzer coverage | Explicit UNKNOWN for missing required verification |
| What it leaves behind | Comments | A pass count | Findings | Evidence: expected, observed, why, provenance |
Categories, not products. Many teams use all four; each is good at its own question.
Together
Add a check. Remove nothing.
Bracel runs as one more check on the pull request, next to what you have. It changes no merge settings.
- 01
Keep your reviews
A review catches design, naming and intent. Bracel does not read for style; it executes the rules that must hold.
- 02
Keep your tests
Tests establish the behavior of the cases they execute. Bracel adds approved scenarios and an evaluator the application patch cannot weaken; both remain limited to their tested scope.
- 03
Keep your scanners
Static analysis finds known patterns. A refund cap or an access rule is specific to your product, so it has to be executed.