R7.4: Acyclic module layering

Short answer: Domain -> application -> adapters; no circular imports. A cycle between layers means none of them can be tested or changed alone.

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.4

What it catches

Acyclic module layering: domain -> application -> adapters; no circular imports.

Why

A cycle between layers means none of them can be tested or changed alone.

A bad example

adapters/db.ts imports domain/order.ts, and domain/order.ts imports adapters/db.ts

A good example

adapters/db.ts imports domain/order.ts only

How it is checked

Nothing yet. No scanner and no slice card checks it: it is a standing rule for authors and reviewers.

How to silence it

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

R7.5 Universal contracts purity
R7.1 Contract-first monorepo changes
R7.2 Granular field validation
R7.3 Single canonical route per path
Every rule