How much work is left

The operator product, and the one a poker room pays for. Live. The first outside operator signed in on 2 October, and One Eyed Jacks is being set up, starting with its leaderboard and its tables.

• A first tournament run from start to finish. Registration through payouts and points has been verified in testing but never run for real. Running one in production, then one at One Eyed Jacks, is the next milestone. Not started.
• The multi-device simulation: RoomDirector at the desk, a dealer tablet, the TV and two players' phones running one small tournament together. Not started as a planned run. The one-second tests of 8 October did put four screens on one live event in our demonstration room. Two more alert types, break ending and registration closing, have now fired for real, the last time on 26 September, when our clock mirrored the One Eyed Jacks event level by level.
• One Eyed Jacks' schedule moved into RoomDirector. Its 104 upcoming events are copies from PokerAtlas, which RoomDirector deliberately does not list, so its staff would open an empty schedule. The fix is planned: a switch that makes RoomDirector the room's only schedule and stops the copy. Not started, with three questions to settle first.
• The room's own setup. Its 32 tables were entered on 8 October. Its templates, weekly events, points style and payout curve are not.
• The receipt printer at the room's desk. Automatic ticket printing shipped on 22 September, straight from the browser to a network receipt printer. What is left is a printer on the room's own network, and a test with a first entry and a rebuy.
• Turning on tournament scoring. As of 8 October two of the 37 rooms have a scoring style selected: our own demonstration room and the first outside operator's. See the note below.
• A place for a series and for special events, such as the DirtyStack Poker Tour, with standings across events. New. It starts with mockups.
• The Players page lists none of a room's imported players. One Eyed Jacks has 709 on its board and the page shows none. Found on 8 October. In progress.
• Two gaps a competitor covers and we do not: must-move, the rule that consolidates short tables, and a player sitting on more than one waiting list at once.
• Operational completeness: editing a whole series at once, a cash seating defect, two half-finished money features, and what a room has bought. Two more are new: a public page at roomdirector.com, and a size review of the whole product.
• Shipped since the last edition: players keep their points when they sign up, because staff can join a player on the room's board to the player's app account by phone number, with an undo. Players sign for a tournament payout on a tablet, tested on a real one on 4 October. Late entry closes at a level the room picks, registration can open and close by itself, and desk staff can register players. Each room sets what its ticket shows and sees it before it prints. One page answers who may do what in a room. Staff find any page by a word, and the same search finds players and tournaments. The activity log gaps are closed, and a colour fault in 297 places is fixed.

A touchscreen for the room's front door, live at kiosk.tblmaster.app since 27 August. A permanent RoomDirector module, planned first for One Eyed Jacks. No kiosk is paired in a room yet.

• What it does today. A player types a phone number and is checked in, and anyone new gives a name and a phone number on an on-screen keyboard. It carries the tournament schedule and the room's leaderboard, from the same feeds as the website and our embeddable card. Between players it rests on a rotating idle screen.
• An hour on the real hardware. Full-screen mode on the touchscreen, the idle reset and the return from a finished check-in, on real glass and not a developer's browser. No kiosk has been paired in production, and no check-in has been recorded.
• Leaderboard search past the top 50. One Eyed Jacks' board has 709 players, and search reaches only the top 50 today. The feed behind it can search the whole board, so the fix is small.
• Check-ins seen at the desk. Nothing in RoomDirector shows kiosk check-ins yet, and the room's name, time zone and featured event are still written into the code.
• Shipped since the last edition: pairing a kiosk now needs a manager. Before 23 September any staff account in the room could pair one.

iOS and Android. Live on Google Play since 15 September and on the App Store since 30 September, with version 1.28.0 on both. The first release is free: purchases and ads are switched off and return together in a later release.

• The next version, 1.29.0. In test builds and in neither store. It carries the live tournament updates, which are the app's half of the one-second work, and the fixes found since launch. The app stores page carries the detail.
• The clean-up after launch: what a real player sees, from demonstration players to the store text. In progress.
• Password reset, one check left. A second cause was found on a real phone on 5 October and fixed. The fix is live in 1.28.0, and one check on an iPhone is left.
• Notifications: the two digests default to off, so as written almost no player receives one, and a cold start still needs a test on a real phone.
• Also open: the admin switch for room logo permissions; the winner's trophy from the first Tour event; a prompt to rate the app; region pickers by state; and carry-over polish, a featured slot on the home screen and error-reporting rules.
• Shipped since the last edition: live on the App Store, with two updates through both stores since. Report and Block for players, and terms a player agrees to before signing in. Notes rebuilt around one form. Leaderboards, and a Watchlist page the player puts in order. The sign-in kept on the phone is sealed. On Android, the keyboard no longer covers the sign-up screens.

The automated nightly capture of poker room schedules and attendance nationwide. Running unattended every night; this is accuracy work, not build work.

• A recoverable data-loss item: several attendance figures were stored empty despite being legible in the saved screenshots. The oldest urgent item on the list.
• Same-day schedule changes are captured three times a day but reach the website only overnight. The step that publishes a change during the day is not built.
• A single-source dependency. Florida schedules come from one public source. If it changes or blocks us, coverage stops. Adding a second source is the one item here that is a build and not a correction.
• A grading fault: an entry-fee mismatch is currently graded as players being fine, so a wrong price on a live page shows green.
• New since the last edition: an event is stored twice when a later capture reports a different buy-in, so it lists twice. And on 20 September the morning check used its whole monthly allowance and could not check 11 rooms.
• Pipeline hygiene: a true result for every job run, alerting that repeats already-fixed findings, a loss that stays invisible until someone reads the morning email, shell scripts outside automated checks, and diagnostics that write into a dead session's scratch space.
• Shipped since the last edition: a "Day 2" event is no longer published at the full buy-in. A stall that cost the 4 AM attendance read on 23 September was fixed the same morning. Since 4 October the capture jobs sign in with their own database account and not the owner's.

In-room TV screens. The Windows version shipped on 20 September and has run on a real TV. What remains is the one-second requirement, the last checks, and putting the PCs in the room.

• Every change on every screen within one second. Set as a requirement on 25 September. The live signal is in the database, and RoomDirector, the TVs and the dealer tablets have used it since 7 October: a new player, a knockout or a seat move shows with no reload, where a TV could take 30 seconds before. The player app half is in a test build. The first timed runs, on 8 October, came close and did not pass.
• The last of the real TV check. The first PC passed four checks on 25 September: a stream assigned, the clock showing, a network drop and a power cut. Still to see: the rolling numbers and the break countdown while a clock runs on it.
• The PC behind each TV. Windows set so an update cannot restart a TV in the middle of a night, done on the first PC, and a written setup guide, not started.
• Also open: a walk through a whole event for the new final table screen, the screen's stored credential, and the high-hand signage.
• Shipped since the last edition: the Windows app. It starts by itself, restarts after a crash, comes back after a power cut and updates itself overnight. It ran for almost two days on a test PC with no fault, and a scaling fault on 4K TVs was found and fixed. The desk can reload a stuck TV. The clock shows the ante, sounds one pip a second for the last ten seconds of a level, and since 6 October has a new layout with the room's branding. The PC is chosen: about $360 in place of about $900.

The public consumer site. Complete and live. What remains is being found on Google by name, reach into more states, and the paid features, which wait on real sponsors.

• Paid plans and ads, held on purpose. The site serves no ads; a site-wide switch has kept them off since 8 August, and no sponsor is signed. The coach plan is still in test mode, and live payments for the ad-free plan wait for the app's own purchases release.
• Getting found on Google as DirtyStack Poker. In progress. On 3 October two faults were fixed: Google could not find the room pages, and finished tournaments never left its results.
• Regions for every state. About 70 regions under the 50 states and DC. The plan is no longer paused, and the database side is in progress.
• After the first Tour event: the site still advertises The $250 DirtyStack. In progress.
• Also open: brand record follow-ups, two small freshness bugs, and a speed score that counts robots as visitors.
• Shipped since the last edition: a page for each store, and one QR link that sends each phone to its own store. The App Store badge is on. The web framework's security update went out on 2 October. Sections not ready for players can no longer be found through Google.

Embeddable widgets that put live room data on a poker room's own website. Shipped, with two of the four card types live, serving on our own showcase site. Not yet on a partner room's website.

• Keeping the first partner room's board current. Its results are loaded from January to early August, and nothing later. Its staff can enter each night's points in RoomDirector, or send the months as a spreadsheet. Neither has happened yet.
• A series points race for that same room. Its summer series ended on 30 August without a decision on the working model we built. The durable version is a variation of the leaderboard card that already exists, and the room's next series is in November.
• Two further card types are planned and not outstanding. Tournament Schedule and Tournament Clock are not yet built. The schedule card matters commercially: it is the intended way to put our product on the website of a room that has not bought anything yet.

Internal back-office administration. Not customer-facing, and the highest-capability surface we run: it can read and change every record in the business.

• A follow-up to two-step sign-in: extending the same requirement down into the database's own access rules, so the protection holds even for a request that never passes through the app.
• Design system alignment with RoomDirector, regions by state, and one new fault: a sign-in page that failed to draw once on the server.
• Shipped since the last edition: a full page for each room, with a setup list and its TV streams. A full page for each user, and a Users list that shows real accounts first. Dashboards that show only real data. An Awards page to give and remove chips and trophies. An editor for Tour events. A new room can be outside the United States, and the first one is in the Dominican Republic. An admin can set which room a staff member runs.

The per-table tablet. Shipped, and so far used on our demonstration tables.

• An end-to-end cash demo on real hardware.
• The rest of the shared-package gap. The tablet now runs the current database package; on 18 September it was thirty versions behind. Its error-reporting package is still thirteen versions behind. Nothing a table sees is affected; it governs how safely the code can be changed.
• One open defect, counted under roadmap by priority and not here: a dealer pressing for the floor again inside five minutes reaches nobody, because the repeat is treated as a duplicate. Once a room runs live tables on the tablet, that repeat press is exactly the escalation that matters.
• Shipped since the last edition: the tablet takes the live signal since 7 October, so a change at another table no longer waits for the four-second refresh, and its badge says whether the connection is live. Pairing a tablet now needs a manager. A colour fault in 14 places is fixed.

The shared sign-in service behind every application.

• Email links that open in the wrong app on a phone. A phone with the DirtyStack Poker app opens a RoomDirector or admin link in that app, which uses the link up. RoomDirector links are fixed on the server, and the app's own guard is in its next version. In progress.
• One log check on the sign-in hub: confirming from its logs that no real sign-in link is refused.
• Shipped since the last edition: the staff invite email names the room, and its link lasts 24 hours. A link that was already used now says so and offers Sign in, where before it could hold a person on the password page.

The site for the DirtyStack Poker Tour. The first event, The $250 DirtyStack, ran at One Eyed Jacks on 26 September. Two days later the site was rebuilt for a tour of more than one stop.

• Finish the rebuild, and open the second stop for sign-ups. Both in progress.
• Re-read the visitor data. The first week showed that roughly three in four visitors, all of them on phones, never saw the film the page is built around. Both causes were fixed, and the numbers still need re-reading to confirm the fix worked. It was due on 15 September and is not done.
• Shipped since the last edition: the new site, live on 28 September, with a Tour home page and one page for each event. Sign-ups work for each event, and people who signed up get an email when a stop moves or is cancelled. Events are edited in the admin app. A dark look for every page followed on 7 October.

Cross-cutting and not tied to one application. Details held privately and not published here.

• The review is still three phases of five through. The known gaps and the June re-test finished on 3 September, and the live attack pass on 6 September. Two phases are open: the fresh review of everything built since June, and the last one, which fixes what was found and locks it in.
• What was fixed since the last edition. Four permission holes were found, and each was closed within an hour of being written down. Since 5 October the nightly capture and the backup sign in with their own small accounts, and the database owner's password was changed. The app's sign-in is sealed on the phone. The security updates held back during Apple's review went out on 2 and 6 October.
• Where the findings stand. On 6 October 27 findings were open: 2 high, 13 medium and 12 low.
• What remains: the last set of dependency alerts, on the consumer website; the rest of the permanent checks; encryption of the remaining sensitive player fields; and limits against abuse and overspending, now that sign-ups are public on both stores.
• Also open: email authentication on the consumer domain, a picture format in one storage area that can carry a script, and a warning the database check raises after every change.

Shared infrastructure consumed by every surface.

• Live-update failure warnings beyond the TVs and the tablets: RoomDirector's own clock and floor calls, and an alert when live updates fail for everyone.
• The database side of regions for every state. In progress.
• After the first Tour event: give out the tour chip, record the points, and start a tour leaderboard. In progress.
• A chip count for each player through a tournament. Moved up from the roadmap on 7 October. Bagging and multi-day events need it.
• Shipped since the last edition: the live signal behind the one-second work, in the database since 7 October. The record behind payout signatures. Rooms outside the United States. An hourly watch that turns each new app error into a tracked item, since 8 October. A new chip design no longer needs a store build of the app.

Not a product surface, but it governs how safely everything else ships. A five-phase automated testing rollout has completed four of its five phases.

• Mobile smoke tests for the player app, the last phase outstanding.
• One build-pipeline blocker left: a branch in one repository cannot merge until the main line is merged into it, because that repository has no automated check for its required gate to run.
• The player app's own logic is still outside the automated tests. The type checks cover it, but the tests deliberately skip the app directory.
• Shipped since the last edition: browser tests of whole journeys are a required check on RoomDirector since 29 September. An automated test proves the live signal: three changes must each arrive within one second, or the check fails.

The production database holds 37 poker rooms and 5,035 tournaments, read on 8 October. Of those, 4,580 were captured automatically from public sources nationwide. The other 455 were created in RoomDirector, nearly all of them in our own demonstration and test rooms. The first outside operator's room created its first event on 6 October, and no real room has run an event in RoomDirector yet. Since 18 September the capture added 1,021 events. The largest day was 1 October, when the schedule horizon rolled forward a month and 335 arrived; a normal day adds between a handful and a hundred. The capture runs unattended, and it has run every night through everything else on this page.

• Multi-day tournaments with starting flights. The design is written and waits on four decisions. The main format gap for larger rooms and series events.
• Bagging at the end of a day. The chip count it needs moved up to the launch list on 7 October.
• Operator-adjustable rake, add-ons during play, and mid-event economic controls.

• Purchasable modules beyond the per-room switches that now exist: what a room has bought, plans and billing.
• Staff scheduling, table transfer requests, food service, announcements and configurable alerts.
• Gaps from the competitor comparison: non-poker tables on the floor map, employee badges, player tiers on the waitlist, and a floor map that switches between game colour and occupancy.
• Rules at the table: a player on penalty, a surrender to re-enter, and the button and blind rules after a move.
• In-room screens: telling two events apart on the TVs, one exit PIN for a room's TVs, a sign line tied to a live number such as a jackpot, and a diagnostics panel.
• New since the last edition: poker leagues, a print station, and a worksheet for the monthly state report a Florida cardroom files.

• Social posting, comments and moderation on the consumer site.
• Player levels and tiers, followed-player alerts, saved-interest discovery, and a personal plan for the week.
• Cross-room ranking, a normalised tour-level score and not a sum of individual room points.
• From the competitor comparison: relative times such as "in 3 hours", whether a room's cash games are running, the player's balance at the room, and ordering food from a seat.
• Found after launch: screen-reader support on about twenty panels, the Android Back button on alert boxes, and the back swipe on iPhone.

• Two further Live Cards types: a tournament schedule widget and a live tournament clock widget, joining the two already shipped. The schedule card doubles as a way to appear on a prospective room's website before they are a customer.
• More languages in the mobile app. The consumer site and the shared translation package already run in English and Spanish; the app is English only.
• Tournaments nationwide, state by state, after the regions for every state.
• Programmatic advertising, alongside direct-sold sponsors once there are any.

• Framework version upgrades, including the one Apple requires for the app by April 2027, and app updates that reach phones without a store build.
• The security review's medium and low findings, recorded so they cannot be forgotten and not because anything is on fire.
• Tournament intelligence depth: results nine Florida rooms publish on their own sites, reading attendance from a room's own clock feed, and telling a dark room from a dead page.
• Shared design system convergence and accumulated technical debt recorded during the build.

The measure is One Eyed Jacks running its own tournaments on RoomDirector. Most of a tournament night is built: 14 of its 17 steps work today. Of the 11 items that stand before the first tournament, two are code, and one of those two is already live on three of its four screens. The rest is the room's setup, hardware, training and rehearsal. The room's tables went in on 8 October. Its templates, points style and payout curve are not entered, and every one of its 104 upcoming events is still a copy from PokerAtlas. No real tournament has run through RoomDirector yet. The first one, in production and then in the room, is the proof this product has not had. The One Eyed Jacks page carries the detail.

Since 2 October a room run by an outside operator is on RoomDirector, the first whose staff are not ours. It has its scoring and payouts set and its first event created. Its admin was stuck once on the way in, on a used invite link, and that fault was fixed the same evening. One Eyed Jacks is coming on in stages, and its manager has not yet accepted the invite of 5 September. Billing for rooms is not built, and no room has bought a plan through the product. The one thing already worth protecting is One Eyed Jacks' points history, 709 players from its own records. Since 8 October that history can follow a player onto their account, and the first four players are joined. One thing here needs flagging and not just reporting. The same room asked for a points race across its two-week summer series, the first time a partner pulled a feature and did not only review one. A working model was built, and the series ended on 30 August with no version chosen. It still needs a decision: build the durable version, a variation of a card we already ship, for the room's next series in November, or close it.

On 18 September the one outside wait was Apple. It ended on 30 September, and the two updates since passed both stores on the first try. The Windows code-signing certificate, the other item that could not be hurried, is no longer needed for launch. What is left is ours to do or the room's to decide. The one-second test needs a phone, a TV and a tablet side by side. The rehearsal tournament needs the same. The room needs its setup, and One Eyed Jacks has a handful of decisions to make and a date to agree. Purchases and ads stay switched off on purpose, and come back together when there are sponsors.