R13.3: Trace context propagation

Short answer: Distributed calls forward traceparent / correlation IDs. Without the trace id you cannot follow one request across services.

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

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

What it catches

Trace context propagation: distributed calls forward traceparent / correlation IDs.

Why

Without the trace id you cannot follow one request across services.

A bad example

await fetch(url);

A good example

await fetch(url, { headers: { traceparent } });

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

R13.4 Metric label cardinality bounding
R13.5 Standard log severity
R13.6 Audit event journaling
R13.7 Health check hermeticity
Every rule