brevio-core

Catches the mistakes coding agents repeat before they merge: a pull-request gate with no model call and no API key.

View the Project on GitHub Brevio-Ventures/brevio-core

R3.5: Transactional outbox

Short answer: Persist DB state before enqueuing external side effects. If the process dies between the queue and the database, the outside world and your data disagree.

Group: Billing and money. Status: stable. Generated from the rule definitions; do not edit by hand.

Playground: https://brevio.pro/tools/agent-guard-playground?rule=R3.5

What it catches

Transactional outbox: persist DB state before enqueuing external side effects.

Why

If the process dies between the queue and the database, the outside world and your data disagree.

A bad example

await queue.send(msg);
await db.insert(row);

A good example

await db.insert(row);
await queue.send(msg);

How it is checked

How to silence it

A person can silence one finding with brevio-core: ignore R3.5 -- reason on the line or the line above. Without the reason it does not count. An agent cannot silence it: the agent hook and the MCP tools never honour the comment, and a pull request that adds one is reported until a reviewer allows it. Fixing the code is still the better answer.

To change what the rule flags, edit its definition in dev_rules.py or code_rules/__init__.py. That is a code change and is reviewed like one.