Observability Starts With Naming Events Consistently

Dashboards and alerts inherit their quality from event names, and inconsistent naming quietly caps how good any downstream tooling can become.

No query can join events that disagree about what they are called. Naming discipline is unglamorous, and it decides whether observability compounds or decays.

Naming rules that pay off

• One verb vocabulary shared by every agent and adapter.
• Identifiers that survive across handoffs instead of resetting.
• Names that encode outcome, so denied and failed are never conflated.

Use the audit schema, architecture guide, and contributing guide to keep one event vocabulary across every component.