The note said one game takes about 19 pastes and one human syncing money to names. Here is that claim with receipts: the five jobs that make up a game night today, then the four ways they break. Every message is verbatim from the export. On the right, one real game re-pasting itself. Watch spot 9.
I traced one game from announcement to kickoff and it splits into five distinct jobs. All of them currently run on one phone. It repeats up to three times a day, seven days a week.
Trisha drafts the template, format, time, price, payment link, and posts it. Sometimes a poll first, to guess demand.
Players copy the newest version of the message, type their name into a numbered slot, and re-send the whole thing. ~19 times per game.
The list and the payments live in two different systems. Trisha is the sync engine, 195 chase messages in ten weeks.
Paid players add ✅ next to their own names, self-reported. Trisha cross-checks against the backend and re-posts the corrected list.
If the list stalls: beg, downgrade the format, or cancel and refund everyone by hand. Roughly one game in five wobbles like this. Then, at the turf: "which ground?", asked in chat, answered in chat, every night.
Five jobs, all running on copy paste. What follows is not people being careless, it is the physics of running a concurrent database inside a chat message. Exhibit A happened on 22 July:
Anyone with the link can pay without ever touching the list, silently taking a spot from someone mid-typing.
The checkout takes exactly one payment per phone. Bringing two friends means three separate people doing three separate checkouts, coordinated by you, over calls.
When demand overflows, priority goes to whoever pays fastest, not whoever queued first. The waitlist is a scramble, not a system.
A late dropout has no way to release a paid spot, and the next person has no way to grab it. The game absorbs the hole, or dies from it.