- Shipped
- September 7, 2026 at 8:25 AM UTC
- Author
- Kamo
- Commit
- 79df2cd
The "have you tried this yet" half of the catalogue: one tier at a threshold of one, cheap on purpose, existing to make the product's own surface discoverable. AchievementTrigger is the load-bearing part. These thirty-five do not all reach the platform the same way, and leaving that implicit would mean one endpoint able to award anything: BASELINE granted for existing. Exactly one — JOIN_THE_TEAM. It has its own kind so the probe map's startup guard needs no special case, and a guard with an exception in it is a guard the next person edits around. DERIVED recomputed from rows the platform already stores. Twenty-six of the thirty-five, and the strongest kind: true exactly when the data says so, nothing to fire at the right moment, and every member who did the thing before the code existed is credited the first time they look. EVENT a service reports it. Three, and only where there is genuinely nothing to count: a status flipped and flipped back, a sign-in from a client a session does not record, a game whose world is in another database. CLIENT the browser claims it. Six actions no server can see — a floated note, a maximised window, a screen shared over WebRTC, a chat head thrown at a goal. THESE ARE FORGEABLE BY THE MEMBER THEY BELONG TO. That is accepted deliberately and bounded deliberately: the member comes from the session so nobody can claim for a colleague, the service refuses any other kind through that path, and every one is worth a shrug. AchievementCatalogTest fails the build if one exceeds thirty points. Every track stays DERIVED and a test enforces it — a level counted forward from events is wrong the first time an event is lost, with nothing to compare against. TOP_CORNER is the catalogue's only secret. Everything else here is a prompt, and a prompt withheld is not a prompt; this one is an easter egg, and an easter egg listed with instructions is a chore. Three catalogue guards caught real mistakes while this was being written: a level title reused across two achievements (twice), and a client-attested achievement priced at ninety points.