# Communication Rules

## Purpose

These rules keep standups, Jira notes, and Mattermost messages aligned with the actual state of the work.

---

## Rules

- Prefer explicit scope over short vague statements
- Always mention auth state when it changes reproducibility
- Separate external report from regression
- Say whether behavior was confirmed in main when that comparison exists
- End with the next action when writing status updates

---

## Avoid

- "same behavior"
- "looks good"
- "seems fixed"
- "working now"

Use concrete statements instead.