- Shipped
- September 7, 2026 at 7:28 AM UTC
- Author
- Kamo
- Commit
- b62771d
**************** reads all six of a member's marketing counters in one row and settles all six tracks against them. Wired into /self and /self/pending beside the baseline and the Growth Hub recount. NO EVENT SEAM HERE, AND THAT IS DELIBERATE RATHER THAN UNFINISHED. Three of the six are driven by beaconed page views, so an award call per event would put a cross-service request on the marketing ingest hot path. Hooking only the three low-frequency conversions instead would make half the feature instant and half of it not, and a member who learns that some of their trophies arrive late stops trusting the rest. One recount, on every achievements read, treats all six alike. One query for six numbers, read at one instant: six sums would be six round trips on a page load, and would let ingest move between them — recording a member as having more organizations than signups, which is not a state the funnel can be in. The column-to-achievement mapping is one readable list, because getting it wrong files a member's page views as their paid accounts and nothing downstream could detect that. THE BACKFILL. `award` SETS the running total rather than counting forward from now, so the recount credits every level a member has already earned the first time it runs for them — the counters have been accumulating for months and the launch has to find people already holding levels. The read path does that for anyone who opens a page; **************** does it for everybody else, nightly, and its first run IS the backfill. There is no script to run. The sweep exists because of the LEADERBOARD: it publishes every colleague's points to everybody in the organization, so a member who has driven ten thousand visitors but has not opened the page would sit at zero on everyone else's board — a wrong statement about somebody else that they cannot fix by looking. Nightly rather than one-shot for the same reason: a one-shot has to be correct on the single night it runs and leaves the board drifting the next day. It is bounded by members who own a tracking code, skips a member whose standing has not moved without writing anything, runs at 04:40 (after MediaService's 03:15 counter reconcile, so it never awards a level off figures about to be corrected downwards), takes a SingletonTaskRunner lease so two pods cannot both publish an unlock frame for the same level, and logs at INFO even when nothing moved — "nothing moved" and "the sweep did not run" look identical from outside and only one of them is fine.