R8.2: Honest telemetry attribution

Short answer: Label synthetic/demo data; never mix with live metrics. Demo numbers mixed into live numbers make every report untrue.

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

Playground: https://brevio.pro/tools/agent-guard-playground?rule=R8.2

What it catches

Honest telemetry attribution: label synthetic/demo data; never mix with live metrics.

Why

Demo numbers mixed into live numbers make every report untrue.

A bad example

metrics.push(...demoRows, ...liveRows)

A good example

metrics.push(...liveRows)  // demo rows are labelled and kept apart

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 R8.2 -- 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.

R8.3 Consent Mode v2 ordering
R8.1 Anti-cloaking & markdown parity
Every rule