This summary is private. Enter the password to continue.
TableMaster / September 26
Development only. Testing, rehearsal, staff training and setup are all still required, and are covered separately. Scoped to the hybrid we settled on 25 August, in which our software runs registration, the clock and the floor while PokerAtlas stays the room's system of record.
Most of it is already built. The tournament clock, blind levels, registration, seating, table moves, settlement and payouts all shipped months ago, and the live clock already reaches the room screen, the dealer tablets and players' phones.
What remains is six required items, down from ten, and a handful of optional ones. None of them is a new capability any more. Every one is a fault, a gap, or a version number in something that already works.
The list halved because the kiosk got built. On the last edition the check-in kiosk was the one genuinely new thing the plan asked for and nobody had written it. It is now a deployed application serving publicly at kiosk.tblmaster.app, with check-in, new-player capture, the live tournament schedule and the room's leaderboard all working against real data. Its remaining work is an hour on the actual touchscreen, which is not a build.
The sharpest item is not a feature at all, and it has not moved. The room screen and the dealer tablet are both 24 minor versions behind on the shared database package, and a caret range cannot cross a minor, so neither picks the fix up by reinstalling. This was true on 26 August and it is still true, verified on 3 September. Each range has to be raised deliberately and typechecked. Both surfaces carry real work on the night, which is now 23 days away rather than 31.
Printing entry tickets is no longer the hard item it looked like. The receipt is built and prints today, and silent printing on the night is a browser launch flag rather than the Windows build this page previously assumed. Whether we print at all is still an open choice, not a build problem.
Marked Required where the event genuinely depends on it.
Was the weakest surface, and is now one of the stronger ones. Every fault on the first edition of this list is fixed, the visual pass shipped, and it has since gained a capability the room already pays someone to track by hand.
Only relevant if players are using the app during the event. The surface that moved most since the first edition.
The display showing the clock and standings. Since 25 August it runs on One-Eyed Jack's own AV system, which makes it both the truest test we have and the surface carrying the most uncertainty.
The layer every surface depends on.
Was the only genuinely new surface the September plan added, and the one thing nobody had written. Built, deployed and publicly serving since 27 August. It is now a permanent RoomDirector module rather than an event fixture, with September as its first configured event.
The tournament director's surface.
Nothing required. Creating the tournament, taking registrations, running the clock and blind levels, seating players, moving tables, and settling payouts are all built and shipped.
More is already built here than the list above might suggest.
The receipt itself exists and works today. There is a print page in the app with the correct thermal-printer layout, a scannable code, and a print button that produces a real ticket. It currently sits behind developer mode and prints a fixed sample rather than a real player.
So the question is not whether to build printing. It is how far to take it.
Recommendation: Level 2 for September. It keeps printed tickets on the table without putting the Windows build on the critical path, and costs a few seconds per player at the desk. The Windows version stays available afterwards, when there is time to do it properly rather than against a date.
Development only, as requested. Still required and not listed here: rehearsing a full event end to end, training the room's staff, choosing a scoring style so results award points, and confirming the screen reads well on the actual television. Those sit in the September options document, alongside the lighter alternatives to running the whole event on our software.
Items marked Done were on an earlier edition of this list, the first dated 16 August, and have shipped since. They are kept visible rather than deleted so the list can be read against the versions already circulated. Refreshed 3 September against the live issue tracker and a direct read of the version files behind every drift claim.