Companion page

The House Taxonomy

A public sketch of how Compute Nodepoint groups App Analytics events before anyone opens a vendor. It is a starting ledger, not a religion.

Open planner and notes suggesting a structured taxonomy

A

Birth

Install, first open, account created. One of these is the cohort parent. The others are supporting facts. Mixing them is how retention becomes fiction.

B

Job

The verbs the app claims: ticket bought, lesson finished, claim filed. If a job cannot be named in six words, it is not ready to be counted.

C

Friction

Errors, empty states, permission denials. Collected only when someone will read them in the same week they fire.

D

Commerce

Price shown, tender chosen, receipt issued. Keep these aligned with finance, or the two rooms will spend a year reconciling ghosts.

E

Identity

Sign-in, sign-out, restore, merge. Rare events, high cost if wrong. Never inferred from a screen view.

F

Silence

The events we refuse: hover, every keystroke, decorative impressions. Absence is part of the taxonomy.

How a cohort uses it

Students map their live dictionary onto these six drawers, then argue. Most apps arrive with a seventh drawer called Miscellaneous; we empty it. What cannot find a home is either a job in disguise or a candidate for deletion.

The full practice — ownership, retirement notes, and the spoken test — sits inside Signal Architecture. The shorter salon, Event Taxonomy for Product Rooms, is offered by letter.

If you only steal one habit from this page, steal the last drawer. A list of events you will not collect is a measurement plan. A list of everything you might collect is a wish.