A dated register of rule, product and policy news
The News hub is a dated register. Each entry records the source date, the desk’s verification status and a link to the relevant editorial chapter. The desk does not publish live-data fabrication. If a story has not been verified against a published primary source, the entry is held back from the register until verification completes.
How the desk verifies a news entry
Each entry on the register is read against a primary source before publication. The desk does not run a wire-feed. Where a story has not been verified, the entry is held back from the register until the desk can name a published source. The desk flags corrections explicitly when a published source has been amended.
The primary source is named in the entry footer. The source date is the publication date on the primary source, not the date the desk first saw the story. The desk’s verification status is recorded as Verified (the desk has read the primary source), Pending (the desk has not yet read the primary source) or Disputed (the primary source has been amended and the desk is recording the correction).
The register does not include a story the desk has not verified. The desk flags a wire-feed-style "may be published soon" pattern as a red flag for editorial distance. A dated register that publishes a story the desk has not read is a red flag in the desk’s editorial-distance record. The reader verifies the primary source before relying on any entry listed in the register.
The three categories the desk records
Rules entries record a published change to a rules table. A change to the drop ladder, the card values, the meld grouping, the show validity or the chip stack is a Rules entry. The Rules entries on the register are limited to changes the desk has read against a published primary source. The desk does not record a Rules entry that has not been verified.
Product entries record a published change to a platform’s product surface. A change to the published sign-in flow, the published table lobby, the published in-game UI, the published wallet UI or the published history UI is a Product entry. The Product entries on the register are limited to changes the desk has read against a published primary source.
Policy entries record a published change to a regulator or government policy. A change to a state gaming act, a federal gaming rule, a published responsible-play standard or a published consumer-protection rule is a Policy entry. The Policy entries on the register are limited to changes the desk has read against a published primary source.
How to subscribe to the desk’s feed
The dated register is published as RSS. Adult readers who want a single feed of rule, product and policy news can subscribe at /feed.xml. The feed carries the same source date and verification status as the on-page register. The feed is updated when a new entry is published, when an existing entry is corrected, and when an entry is retracted.
The feed is not a wire-feed. The feed is the desk’s own dated register, filtered for adult readers who want a single source of rule, product and policy news. The feed does not include a story the desk has not verified. The feed is the same content the on-page register displays, in RSS 2.0 format with the published source URL and the desk’s verification status.
The feed is published at /feed.xml. The feed is updated when a new entry is published, when an existing entry is corrected, and when an entry is retracted. The feed is not a wire-feed; the feed is the desk’s own dated register. The reader subscribes to the feed to receive a single source of rule, product and policy news without visiting the desk’s page for each entry.
The on-page register and the feed are kept in sync. The desk does not publish an entry on the feed that is not on the on-page register. The desk does not publish an entry on the on-page register that is not on the feed. The reader verifies the sync by reading the most recent entry on the feed against the most recent entry on the on-page register; the source date and the desk’s verification status should match.
Operational reference for this page
The pages on boltfantasy.com are written by the editorial desk. Each page walks through the published material on a single topic; the operator-specific UI is the source of truth and must be verified on the operator’s own published material before the reader commits a rupee. The pages are not legal or financial advice; the pages are editorial guidance on the published rules, the published drop ladder, the published chip math, the published safety surface and the published comparison dimensions. The reader verifies the operator’s current page before relying on any figure listed here.
A published number is a number the operator has published on the operator’s own page. The desk has read the published numbers on a small set of operators; the desk does not synthesise or extrapolate. Where the operator publishes a number, a window or a document list, the desk records it; where the operator does not, the desk records the gap. The reader uses the desk’s record to make their own comparison; the desk does not publish a winner.
A published window is a period the operator has published on the operator’s own page. The desk has read the published windows on a small set of operators; the desk does not synthesise or extrapolate. The reader verifies the operator’s own page before relying on any window listed in the editorial chapter. The comparison ledger records the windows the desk has read against a published primary source.
A published document list is a list the operator has published on the operator’s own page. The desk has read the published document lists on a small set of operators; the desk does not synthesise or extrapolate. The reader verifies the operator’s own page before relying on any document list listed in the editorial chapter. The comparison ledger records the document lists the desk has read against a published primary source.
A restricted-state list is a list the desk has read against a published primary source. The restricted states for real-money rummy, as of the desk’s last review (Edition 342, 06 Aug 2026), include Telangana, Andhra Pradesh, Assam, Odisha, Sikkim, Nagaland, Meghalaya and Tamil Nadu. The desk’s list is a desk record, not a legal interpretation. The reader verifies the local state gaming act before playing. A state change to the restricted list is recorded in the news register with the source date and the desk’s verification status.
A support line is a contact the desk has read against a published primary source. The desk does not operate a support line; the desk links to the published support lines operated by recognised public-health bodies. The reader is encouraged to contact a support line if the play has stopped being a leisure activity. The chapter’s last review date is recorded on the page footer.
A review cadence is the desk’s published review window. The desk reviews each chapter on a quarterly cadence. The chapter’s last review date is recorded on the page footer; the reader verifies the local rule before relying on the chapter’s published figures. A chapter that has not been reviewed in the last quarter is flagged in the chapter’s footer; the reader verifies the operator’s current page before relying on the chapter’s published figures.
A red flag is a published signal the desk has read against a primary source. The desk flags any operator that does not publish a deposit cap, a session timeout or a self-exclusion switch. The desk flags any operator that publishes a dispute window shorter than the desk’s published baseline. The desk flags any sign-in surface that does not match the operator’s published domain. The comparison ledger records the red flags the desk has read against a published primary source.
A primary source is a document the operator or regulator has published on its own page. The desk reads the primary source and records the desk’s own test ticket where the operator publishes a verifiable flow. The desk does not synthesise or extrapolate. The reader verifies the operator’s own page before relying on any figure listed in the editorial chapter.
A chapter cross-reference is the link between chapters on a single topic. The format-split chapter is referenced from the games hub, the strategy hub and the reviews hub. The drop-vs-show chapter is referenced from the strategy hub and the games hub. The dispute-handling chapter is referenced from the reviews hub and the safety hub. The reader uses the cross-references to navigate to the chapter that matches the decision they are facing. The cross-references are not commercial links; the cross-references are the desk’s own editorial navigation.
A reading order is the desk’s recommended sequence for a reader who is new to the chapter. The reader starts with the chapter’s first section, walks through the published material, and finishes with the operational reference. The reading order is not a personal recommendation; the reading order is the desk’s own editorial sequence. The reader may skip sections they are already familiar with; the reader verifies the operator’s current page before relying on any figure listed in the chapter.
A glossary entry is the desk’s published definition of a term used in the chapter. The glossary entries are linked from the chapter’s operational reference; the reader uses the glossary to look up an unfamiliar term without leaving the chapter. The glossary is not exhaustive; the glossary covers the terms the chapter uses most often. The reader uses the desk’s broader editorial chapters to look up terms the chapter does not define.