Lobby update: 973 titles across eight providers, one filtered view

What changed since the last count, and which providers moved.

What changed in the crawl

The pipeline ran a full re-crawl overnight and surfaced 973 distinct titles across the eight configured providers. The headline number is up from the previous crawl because two providers onboarded new slot batches during the cycle. The crawl also revalidated 11 provider IDs that were stale in the previous index; those IDs are now confirmed and the matching room cards carry the fresh last-crawled stamp.

The most material change is the addition of a new Fachai room batch covering fishing titles. Fishing titles sit under the regional arcade room; the room card on the homepage now shows a higher count than the previous crawl, and the news desk is flagging this delta because it is the kind of change that shifts the topic matrix at the bottom of the homepage.

Stale entries were pruned: any title that failed the daily HTTP-200 check for three consecutive cycles is dropped from the index until the provider confirms a return date. Three titles were dropped in this cycle; the room cards reflect the drop and the news desk is linking the operator-side status pages in case the titles come back during the next crawl.

What did not change

The operator route status for the eight configured rooms is unchanged from the previous crawl. All eight rooms show ROUTE OK on the homepage, the status flag is green, and the news desk has no delta to publish for routes.

Promotional terms on the cards under /promos/ are unchanged. The operator has not published a new promo feed entry during the cycle, and the cards continue to carry the previous headline plus the link to the operator's reward page. If a new promo lands mid-cycle, the news desk will publish a delta post and link it from the relevant card.

Editorial line is unchanged. The lobby's writing team continues to prefer the operator's published number to a lobby estimate, prefer a recent observation to an older one, and prefer honest incomplete to flattering complete. The lobby update you are reading is published under the same editorial line as the rest of the catalogue.

Editorial line on this update

The desk's editorial line on lobby updates: the headline number is the count after the latest crawl, the last-crawled stamp is the freshness signal you should rely on, and the deltas section is where you can see what moved during the cycle. If a delta is missing, the desk missed it; the contact form is the right channel to flag it.

The desk does not auto-publish lobby updates. Each update is hand-verified against the crawl output, and the headline number is the count after the verification step, not the raw pipeline output. Raw pipeline output tends to over-count during a crawl window because it includes titles that have since been delisted; the verification step prunes those.

What the desk will not do on a lobby update. The desk will not include titles the operator has not confirmed are currently live. The desk will not surface promotional terms on a lobby update; promotional terms live under /promos/. The desk will not run a "trending" label; the lobby's editorial line is that recency is a fact, not a marketing angle.

How the count is computed

The headline number is the count after the verification step, not the raw pipeline output. Raw pipeline output tends to over-count during a crawl window because it includes titles that have since been delisted; the verification step prunes those and the headline is the post-prune count.

A title is counted if three conditions are met at the verification step: the provider confirms the title is currently live, the operator route for the title returns HTTP 200, and the title ID matches the lobby's catalogue of provider-side IDs. If any of the three fails, the title is dropped from the headline count and flagged for the next cycle.

The last-crawled stamp is the timestamp of the verification step, not the timestamp of the raw crawl. The two can diverge by up to one cycle because the verification step runs after the crawl window closes. The desk uses the verification timestamp as the freshness signal because the raw crawl timestamp tends to mislead users into thinking a number is more recent than it is.

Why the count fluctuates. The count moves when the provider onboards new titles, when the operator delists titles, and when the crawl pipeline fails for a provider mid-cycle. The desk publishes a delta post on the lobby when the count moves by more than a stated threshold; smaller deltas are absorbed into the next headline update without a dedicated post.