Align event and property names to one convention
Three naming styles across one event set, aligned with a rule that blocks the next divergence.
The ticket
Rename events and properties onto one convention and enforce it.
Acceptance criteria
- The convention is documented
- Renamed events keep working for existing dashboards during a transition
- A rule or schema check blocks a non-conforming event
- Every dashboard reading the old names is updated
What lands as proof
A check that rejects a non-conforming event, which is what stops the convention decaying again.
Why teams defer it
- Renaming events breaks dashboards, so it needs a transition period nobody wants to manage.
- Every style had a reason at the time, which makes the choice political rather than technical.
Questions
- What does the agent actually change?
- The ticket is scoped to one outcome: rename events and properties onto one convention and enforce it. Work that serves that outcome is in scope, and anything outside it is left for a separate ticket, so the pull request stays reviewable.
- How do I know the work is done?
- The pull request carries the evidence, not only the diff. Here that means convention documented, a rule blocks the next divergence, so a reviewer can confirm the result without reproducing the work locally.
- How much oversight does this need?
- The run stops once the plan is written. Somebody reads the approach and approves it before any code exists, which is the cheapest moment to redirect the work.