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

R7.3: Single canonical route per path

Short answer: No duplicate route group paths. Two route files for one path means one of them is never reached.

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

Playground: https://brevio.pro/tools/agent-guard-playground?rule=R7.3

What it catches

Single canonical route per path: no duplicate route group paths.

Why

Two route files for one path means one of them is never reached.

A bad example

app/(a)/pricing/page.tsx and app/(b)/pricing/page.tsx

A good example

app/(marketing)/pricing/page.tsx

How it is checked

How to silence it

A person can silence one finding with brevio-core: ignore R7.3 -- 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.