What's Left to Build

44things left to build before the product is launch-complete

Sixty-four items stand between here and a complete, sellable product. Twenty of them are not development work at all: rehearsals, hardware testing, store paperwork, a certificate to purchase, accounts to configure. Strip those out and the engineering queue is the 44 below.

The queue grew while the hardest thing on it was finished. The check-in kiosk was two of the forty items on the last edition and is now written, deployed and publicly serving, which should have taken the queue to 38. It stands at 44 instead, because a deliberate bug sweep of the mobile app found four faults nobody had reported, shipping high hands promoted the screen-signage work that follows it, two gaps a competitor covers were written down for the first time, and two half-finished money features were separated out from the features that already work. None of that is drift. It is what happens when you go looking.

Beyond launch there are a further 132 items in the backlog. They are summarised at the bottom of this page, collapsed, because none of them block launch.

The build queue

Forty-four items, grouped by the application they land in. Ordered by how much is outstanding, not by priority.

Tournament intelligence pipeline

10 items

A second source for Florida schedules. Everything currently comes from one public site. If it changes or blocks us, coverage stops.
Correct a schedule that changes during the day. Nothing currently does.
Recover attendance figures stored as empty when the screenshot was perfectly readable.
Stop grading a wrong entry fee as green. An entry-fee mismatch is currently reported as players being fine, so a wrong price on a live page passes its own check. A wrong number that reports itself correct is worse than a missing one.
Widen the name check beyond today. The check that compares a published event name against its source only covers events running today, so a rewritten title on a future date stays unseen until the day it runs.
Make a same-day data loss visible without someone having to read the morning email.
Stop the afternoon alert replaying findings that were already fixed in the morning.
Tell an operator what is actually wrong when a live event looks stale.
Bring the production scripts under the same automated checks as the rest of the code.
Stop two diagnostics writing into a dead session's scratch space, one of which destroys the evidence it was run to inspect.

RoomDirector

10 items

Must-move. The rule that consolidates short tables as a field shrinks. It does not exist in our product at all, and a competitor has it. Newly written down, not newly missing.
One player, one waiting list. Today a player can sit on several game lists at once, which is not how a floor runs a room.
A Windows desktop version, so an entry ticket prints the moment a player registers. A browser cannot do that.
Printed registration receipts themselves, wired to real player, table and seat data rather than the fixed sample they print today.
Open and close registration automatically, plus the enforcement gaps around it.
Editing a recurring series after it is created, rather than only at creation.
Activity and event logging brought up to what an operator would expect to be able to audit.
Two half-finished money features. A satellite ticket can be won and spent but no screen can hand one out by hand, and a promotion paid "from the rake" records the intent and pays nothing, because there is no pool or balance behind it.
A colour-rendering defect affecting roughly 300 places. Cosmetic, but wide.
Off this list since the last edition: high-hand promotions, which went from a gap to a working two-phase feature, and the demo caches behind two live screens.

DirtyStackPoker.com

5 items

Turn on the coach subscription. Built in test mode; needs live payments. The site's only direct revenue switch.
Finish the advertising rollout on top of the inventory already serving.
Let a visitor pick more than one region when browsing.
Two freshness bugs: a day label and an opening-hours badge that are correct when a page is built and then stop moving.
Off this list since the last edition: Spanish, which is now live across the site and the shared translation package.

Platform and shared services

2 items

Make live-data failures visible instead of quietly degrading, so a room notices when a screen stops updating rather than trusting stale numbers.
Encrypt the remaining sensitive player fields at the column level. The first tranche, covering player notes, shipped on 31 August.

Player mobile app

7 items

Four faults from the September bug sweep. An Android confirmation email opens a browser instead of the app, because the small file that lets the website vouch for the app is missing. The two digest notifications default to off, so as written no player would ever get one. The nine o'clock alert routes to a screen that cannot answer it. Room logos are shown without a per-room permission, which has to be gated before the app is public.
Remaining fixes from the pre-launch review.
A featured slot on the home screen, hard-coded first and operator-controlled later.
Error-reporting rules that currently file ordinary user actions as faults, and development noise as production events.

Display app

6 items

Raise the shared packages the screen is pinned to. Twenty-four minor versions behind on the database package and three on its own renderer, confirmed again on 3 September and unchanged in nine days. Version ranges of this kind cannot cross a minor by themselves, so nothing picks this up by reinstalling. This is the sharpest item on the page, because the clock goes on One-Eyed Jack's own screens in 23 days.
Read the screen app for the sleep fault already found and fixed on the dealer tablet. Hours of work, still not done nine days after it was identified.
High-hand signage on the screen, now that the rest of that feature has shipped.
A Windows desktop version for true kiosk behaviour. A screen in a poker room has to survive a power cut unattended and come back into the clock, with no desktop or browser prompts over it. Not needed for September.
Harden how a screen is paired to a room, and stop storing its credential in plain text.
Replace the three temporary caches in the shared renderer.

Admin app

1 item

Extend two-step sign-in into the database's own access rules, so the protection holds even for a request that never passes through the app.
Off this list since the last edition: the sign-in redirect hole, and the framework upgrade that carried baseline security headers with it. The interface alignment moved out of the build queue while a third design system is evaluated.

Live Cards

2 items

Put the leaderboard card on real data for the first partner room, including the monthly results import.
Build the series points race that same room has asked for. A variation on the card that already exists rather than something new.

Build and release pipeline

1 item

One 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.

What is deliberately not on that list

The other twenty launch items. Real work, still required, but nobody writes code for them. Recorded here so it is clear they were removed on purpose rather than missed. With 23 days to the event, this list now matters more than the one above it.

Proving it works (9), and none of it has started. A full event rehearsal, the five-surface simulation on one machine, TV hardware and resolution testing, mobile smoke tests, a dealer hardware demo, one pre-cutover sign-in check, proving the clock on One-Eyed Jack's own AV chain rather than a monitor, rehearsing a level change with both clocks moving together, and the external staff pass that is at least under way. Nine days ago this bucket held eleven items and had not started. Two came off it by shipping. The rest have not moved, and there are now 23 days rather than 31.
Configuration and accounts (5). Choosing a scoring style for each room, email authentication records, abuse and spend limits including a challenge on the sign-up form, naming the person who owns clock sync on the night, and picking the ten players who get the app at the event. The scoring one is worth naming twice: as of 3 September, zero of 32 rooms has a profile set, so a real tournament settles today and awards nothing.
Paperwork and purchasing (3). The app store listing package with both privacy questionnaires, a Windows code-signing certificate, and the special-edition chip for the event, which is a physical order with a lead time.
Housekeeping, research and design (3). Brand system follow-ups, a design-system evaluation covering the back office and the operator product together, and two competitor side-by-sides. The credential rotation that stood here was completed on 3 September.

One purchase worth naming separately. The Windows code-signing certificate above is not development work, so it is not in the queue. It nevertheless gates both Windows builds that are, so the two most substantial items on this page cannot ship until someone buys it. Identity vetting for a company certificate can run weeks, which makes it calendar time rather than build time, and the only item here where starting late cannot be recovered by working harder.

Everything else

The backlog beyond launch. None of it blocks a sellable product.

The 132 items past launch-complete grouped by theme

Platform, security and maintenance

41 items

Framework upgrades on two applications, shared packages to extract, and accumulated cleanups recorded during the build.
A broad security sweep: permissive read rules, an API abuse and rate-limit audit, redirect allowlists, and locking down the private schema.
Passkey sign-in, a shared design-system package, and a shared identity layer.
A read-only login for a state regulator. Signature capture on a tablet used to sit beside it here; it shipped on 31 August, complete with a room being able to set the wording its players sign, so a prize award is now something a room can evidence.

Player engagement and app depth

28 items

Player levels and tiers, alerts for followed players, and saved-interest discovery.
An analytics layer over sessions and notes for subscribers, and two features built on Apple's on-device models.
Android purchase verification, waiting on Google rather than on us, plus a set of smaller app fixes and polish items.
Correcting fabricated points and chips sitting on real accounts from tournaments that never ran.

Operator capability

23 items

Multi-day tournaments with starting flights. Designed and documented, awaiting sign-off. The main format gap for larger rooms and series events.
Purchasable modules, so a room buys the capabilities it needs rather than one fixed product.
Table transfer requests raised at the table, staff scheduling, food service, announcements and configurable alerts.
Operator-adjustable rake, room onboarding defaults, and a richer table renderer.

Reach and distribution

14 items

Two further embeddable card types: a tournament schedule and a live clock. The schedule card doubles as a way to appear on a prospective room's website before they are a customer.
Spanish in the mobile app. The consumer site and the shared translation package shipped on 31 August; the app is the remaining half.
Social posting, comments and moderation on the consumer site.
Programmatic advertising alongside the direct-sold inventory already running.

In-room screens and hardware

14 items

Graceful reconnection, a diagnostics panel, and an audible countdown in the last seconds of a level.
Longer-run hardware questions: cheaper streaming sticks, an audible countdown in the last seconds of a level, and a diagnostics panel. Graceful reconnection came off this list on 31 August, and the screen's sleep-fault check has been promoted out of here into the launch queue above.
Testing on cheaper hardware, and reviewing the shipped clock design against real data for the first time.

Tournament intelligence depth

12 items

Reading results that nine Florida rooms publish on their own sites and we currently ignore.
Distinguishing a genuinely dark room from a dead page, and capturing one large room whose site actively blocks us.
Directory corrections and a local dashboard over the audit history.

Compiled 3 September 2026 from the live issue tracker. Every item is tracked, so the figures can be reproduced rather than taken on trust.

How the split was made. Launch-complete is everything in progress or queued, plus every backlog item marked urgent or high priority, plus anything labelled for launch or pilot readiness. From that set, an item counts as a build if an engineer writes code for it. Rehearsals, testing, configuration, paperwork, purchasing and account work do not, and are listed separately above rather than dropped. The 132 backlog items are grouped by theme and are not filtered the same way, because at that distance the distinction is not yet meaningful.

Companion documents: the portfolio summary for what is built and running today, and Full Stack for the narrower question of what the September event alone would need.