Bracel Fix · a separate product

A rule failed. Review a repair backed by evidence.

Fix explains a FAIL, writes one patch, and hands it to Verify, which judges it in a clean environment with values the fix never saw. Only then does it reach you, as a draft pull request.

  • Draft pull requests only
  • Judged by Verify
  • Hold-out values
  • Claude, your key
  • Consent and bounded budgets
Session replay bracel fix · PR #482 · refund.amount-cap@2 00:19 / 00:20

Session

  1. Verify · PR #482 · refund.amount-cap@2FAIL · a 50.01 refund after 50.00 of 100.00 was accepted
  2. Fix job startedattempt 1 of 3 · estimate shown before start
  3. Reading the failing behaviourrule, scenario, observed response

Why it failed

The refund adds the amount to the refunded total without looking at the capture. The update now applies only while the new total stays within the capture, in one atomic statement, so concurrent refunds cannot both pass.

  1. Changed: src/payments/refunds.tsapplication code
  2. Tests, fixtures, rules and workflowsuntouched

src/payments/refunds.ts

  1. 41export async function refund(id: string, amount: number) {
  2. 42 const updated = await db.affected(
  3. 43 'UPDATE payments SET refunded = refunded + $2' +
  4. 44 ' WHERE id = $1 AND refunded + $2 <= captured', [id, amount]);
  5. 45 if (updated === 0) throw new RefundExceedsCapture(id);
  6. 46 return payments.get(id);
  7. 47}

Verify · clean environment · rules from the base commit · hold-out values

  1. POST /payments · 74.00201
  2. POST refund · 37.00 (control)201
  3. POST refund · 37.01422
  4. GET refunded total37.00
  5. 2 concurrent refunds · 37.00 each201 · 422
  6. Other approved rule · admin-authholds

PASS · the listed behaviours were executed and held

Draft pull request #483 bracel-fix/482-refund-cap → the branch of #482

Fix: refunds never exceed the captured amount

Proposed by AI. AI can be wrong. Review it like any other change.

Merge · your decision Bracel never merges and never writes to main.
Example repair · independently verified before human review

Two products, one referee

Fix never grades its own work.

Verify and Fix are separate engines with separate jobs. Verify is the referee: it executes and reports, and it does not need Fix. Fix is the engineer: it proposes, and every proposal goes back to the referee.

Bracel Verifythe referee

Bracel Fixthe engineer

Its job

Executes your rules on the pull request and reports what it observed

Proposes one patch for one failing rule

What it writes

A check result on the pull request. Nothing else.

A draft pull request on its own branch

Uses an AI model

No. Verdicts come from executed requests.

Yes: Claude, through Anthropic’s API under your own key

Works without the other

Yes. Verify is the product on its own.

No. Every proposal is judged by Verify.

How it is priced

Per organization. Verify never stops at a quota.

Customer-owned model key; explicit job budgets

The job

One failure in. One verified proposal out.

  1. 01Input

    One FAIL

    Fix starts from what Verify executed and observed: one rule, one scenario, one pull request. Not from a guess about your codebase.

    refund.amount-cap@2 · FAIL · 50.01 accepted

  2. 02Proposal

    One patch

    A bounded job: a few attempts at most, a token budget and a time limit, with an estimate before it starts and a running total while it works.

    src/payments/refunds.ts · +1 −1

  3. 03Judgement

    Verify, without favours

    The patched head runs in a clean environment, from the rules on your base commit, with hold-out values the fix never saw. Every other approved rule runs again and must still hold.

    74.00 · 37.00 · 37.01 → 422 · PASS

  4. 04Output

    A draft pull request

    On its own branch, with the patch, a plain explanation, what was verified and what was not. Merging stays with you.

    PR #483 · bracel-fix/482-refund-cap

Attempts, tokens, runtime and cost have hard ceilings. New commits or rebases require independent revalidation. A PASS is necessary, never sufficient.

What lands in your repository

Anatomy of a proposal.

Every Fix pull request has the same shape, so a reviewer knows where to look and what was, and was not, proven.

Draft

Fix: refunds never exceed the captured amount #483

1bracel-fix/482-refund-cap → the branch of #482

2The refund added the amount to the refunded total without looking at the capture. The update now applies only while the new total stays within the capture, in one atomic statement, so concurrent refunds cannot both pass.

3
  • Application codesrc/payments/refunds.ts · +1 −1
  • Tests, fixtures, rules, workflowsuntouched
4

Verify PASS · refund.amount-cap@2 · hold-out values 74.00 / 37.00 / 37.01 · admin-auth still holds

5Behaviours outside your approved rules were not checked by Bracel.

Proposed by AI. AI can be wrong. Review it like any other change.

6Merge · your decision
Example draft pull request
  1. 1

    Its own branch

    Never your default branch. One branch per job, proposed into the pull request that failed.

  2. 2

    A plain explanation

    Why the rule failed and what the patch changes, in a few sentences.

  3. 3

    Changed files by category

    Application code, tests, configuration: visible before you open the diff.

  4. 4

    What was verified

    The rule, the scenario, the hold-out values and your other approved rules, with the result and a sealed evidence bundle you can replay.

  5. 5

    What was not

    Behaviours outside your approved rules were not checked by Bracel, and the pull request says so.

  6. 6

    Your decision

    A draft. Bracel never merges and never enables auto-merge.

Guardrails

Proposes. Never decides.

The verdict on a fix comes from the same engine that judged the failure, never from the model’s own account of what it did.

  • Never writes to your default branch

    Every proposal is a draft pull request on its own branch, opened against the branch of the pull request that failed.

  • Never merges, never enables auto-merge

    Merging stays a human decision, or your own GitHub automation.

  • Stops at protected paths

    The patch cannot change the approved policy, mandatory tests, expected values, required workflow or evaluator. Policy edits follow a separate approval path.

  • Stops when it cannot prove itself

    A patch that exceeds the size limit, or gets UNKNOWN from Verify twice, ends the job.

  • Spending you control

    An organization limit set by you is a hard stop. Nothing is charged beyond it without new consent.

  • Never trades one rule for another

    A patch that repairs the failing rule but weakens another approved rule, such as an authorization check, is rejected.

  • States what was not checked

    “Verify PASS for this rule and your other approved rules. Other behaviours were not checked by Bracel.”

Protected paths, by default

  • Your rules file
  • Policies
  • Workflows
  • Lockfiles
  • Tests and fixtures

Your model, your key

The code goes where you send it.

Fix calls Claude through Anthropic’s API, under your own API key and your own contract with Anthropic. Bracel does not see the code that goes to it.

Inference
Claude, on your Anthropic account and key
Data path
From your environment to Anthropic
Bracel
Receives no source code
Verdict
From the Verify engine, never from the model’s text

Fair by construction

Validation is a gate. Your review is the decision.

Independent checks establish only the tested scope. Review the diff, adjacent behavior and residual risks before approving a repository write or merge.

Validation requires

  1. Verify passes the target rule on the patched head, including hold-out values the fix never saw.
  2. Every other approved rule still holds on the patched head.
  3. A final evaluation on fresh samples, fixed before the model was called, passes.
  4. The patch changes no protected path.
  5. Your own required checks pass on the draft pull request.
  6. The draft pull request carries exactly the verified tree.

Not validated when

  • The job ends in FAIL, UNKNOWN, a timeout or an exhausted budget.
  • The patch was stopped at a protected path.
  • Another approved rule fails or cannot be established.
  • A Bracel defect caused the failure.
  • The target revision changed and the patch has not been revalidated.
Access, provider costs and job budgets →

Verify tells you it broke. Fix shows you how to mend it.