Naming rules that survive a handoff

Event dictionaries die when the next squad invents near-duplicates. A short rule set keeps automation reporting readable.

Laptop with code on a wooden desk

Most automation estates grow event names organically: pipeline_done, job_complete, flow_finished. Each looks fine until a quarterly report tries to join them.

A workable dictionary is short. Prefer verb_object_status patterns, ban synonyms for the same exit state, and require an owner for every new signal before it ships.

We keep the first draft under forty events for mid-size estates. Expansion comes later, after the weekly review proves the language holds.

All notes