R7.1: Contract-first monorepo changes

Short answer: Update shared Zod/OpenAPI schema before consumers. If a consumer changes first, the contract and the code disagree until the next release.

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

What it catches

Contract-first monorepo changes: update shared Zod/OpenAPI schema before consumers.

Why

If a consumer changes first, the contract and the code disagree until the next release.

A bad example

change the API handler, then edit the shared schema later

A good example

edit the shared schema, then the handler and the client in the same change

How it is checked

• A one-line card in the prompt of a slice that touches matching files (dev_rules.slice_micro_rules).

How to silence it

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

Related rules

• R7.2 Granular field validation
• R7.3 Single canonical route per path
• R7.4 Acyclic module layering
• R7.5 Universal contracts purity
• Every rule