# Copy Guidelines

Tone:
- plain, direct, operational
- explain impact before implementation detail
- prefer "what happened / what to do next" over system jargon

Do:
- say "Run delayed" instead of "scheduler drift detected" in primary UI
- say "Provider unavailable" before showing raw error names
- explain approvals in terms of user risk and effect

Do not:
- use backend package names as headings
- use internal transport terminology as user copy
- write empty-state text that blames the user
