Dashboards accrete
Every incident adds a tile. Within a year the wall cannot be read in a stand-up. The ledger forces a weekly edit.
Method
Five figures. One caveat. Dated in ink.
The Signal Ledger is how Broker Kernelhub expects App Analytics to leave a meeting: not as a gallery of charts, but as a short publication with a clock.
A ledger has five lines. Activation for the chosen window. Retention for a named cohort, not “all users”. Crash-free sessions on the same clock as activation. A funnel step you are willing to cancel a sprint over. Revenue or a proxy only if the event that earns it is named in the dictionary.
The sixth line is not a number. It is the limitation: a known hole in identity, a store outage, a taxonomy change mid-week. If you cannot write the limitation, you are not finished — you are decorating.
Why App Analytics needs a ritual
Clocks disagree
Store consoles, SDK servers, and warehouse jobs rarely share midnight. Publishing the clock beside the figure stops false alarms.
Vanity finds a home
If a metric cannot occupy one of five slots, it waits in an appendix. Most wait forever, which is the point.
How it is taught
Cohort Signal Studio spends the last three weeks producing ledgers from live-feeling UK datasets. Pulse Reading Saturday produces one ledger from a dashboard the student brings. Neither is a software product; Kernelhub does not sell a tracker.