instrumentation taxonomy
Most application analytics programs break quietly. The first twenty events look tidy. By event two hundred, product managers invent synonyms, engineers abbreviate differently per platform, and the warehouse fills with near-duplicates nobody trusts.
We recommend a three-part pattern: object, action, and context qualifier. Example: `checkout_step_completed` with properties for step index, payment method, and plan tier. The verb stays past-tense and completed-state only—intent events belong in a separate family.
Document the pattern in a one-page standard before the next feature ships. Review new events in the same pull-request ritual you use for API changes. Growth does not have to mean taxonomy debt.