GOV 03 COMMUNICATION
- Source rule: gov-03-communication.mdc
- Download raw file: gov-03-communication.mdc
This page embeds the canonical rule text and adds rule-specific commentary to explain why each section exists.
Governance: Communication
Commentary: Positions communication as delivery control rather than decorative status chatter.
Default Style
- concise, direct, professional
- decision-oriented over status-noise
- explicit about assumptions, risks, and blockers
Commentary: Sets the tone for short, evidence-oriented updates that help people act.
Required Communication Events
Communicate clearly when:
- starting scoped work,
- changing scope/approach,
- hitting a blocker,
- completing verification,
- handing off.
Commentary: Identifies the moments when silence would hide decisions, risk, or completion claims.
Good Update Format
Use compact, auditable updates:
- Intent: what outcome is being pursued
- Change: what was modified
- Evidence: what proves it works
- Risk/Gap: what remains uncertain
- Next: recommended follow-up
Commentary: Gives updates a repeatable shape around state, evidence, blockers, and next action.
Escalation Communication
Escalate immediately when blocked by missing decisions, credentials, environment access, or conflicting requirements.
Escalation must include:
- blocker summary
- impact
- concrete decision/options needed
Commentary: Ensures blockers include proof, impact, and the exact help needed.
Anti-Patterns to Avoid
- vague "done" claims without evidence
- hidden scope expansion
- silent behavior changes not reflected in docs/specs
- repetitive low-value chatter
Commentary: Names the update habits that make agent work harder to trust or review.
Documentation Communication
When changing governance/project docs:
- explain the intent shift
- link related files changed
- note migration or compatibility impact
Commentary: Moves durable delivery context into repo artifacts instead of leaving it in chat.