Rummy rules, products and policy — dated updates.
The register lists rule amendments, product changes and policy updates as they are verified. Each entry links to the affected chapter. Use the horizontal scroll on small screens, or the arrow keys for desktop.
What changed recently.
Each entry in the dated register is a single rule, product or policy note with a verification date. Entries link to the affected chapter. The register is updated when the editorial desk verifies a public change.
Online Gaming Act 2025 references refreshed
Statutory language and rule references across the rulebook chapter refreshed against the public framework.
Wrong-show penalty notation re-checked
Worked scoring worksheet now labels the wrong-show penalty as a common-rule variation rather than a rule value.
State-by-state carve-out list updated
Andhra Pradesh, Telangana, Odisha, Assam, Sikkim, Tamil Nadu, Karnataka, Kerala status checked against latest MeitY notifications.
KYC document-set note expanded
The verification field note now lists PAN, Aadhaar (or V-ID) and address proof, with the typical 24 to 72-hour turnaround.
History of 13-card rummy added to glossary
A short glossary entry added at the bottom of the formats chapter, summarising the history of 13-card rummy.
Fairness-audit citation cleared
The usability rubric's fairness-audit note now cites public RNG audit references rather than operator-specific language.
Colophon publication cadence added
Editorial disclosure now lists review frequency and corrections-handling cadence alongside the source list.
Responsible-play map merged into one chapter
Three previously-separate boundaries pages now live as one chapter to reduce duplication.
Editorial methods, applied to the dated register.
A short note on the editorial methods applied to the dated register. The principles below apply to every entry.
Each entry cites the public source of the change. Where the source is a primary regulator (MeitY, the Online Gaming Act 2025, a state-level notification), the citation names the regulator. Where the source is a public rulebook, the citation names the rulebook.
Each entry describes the change in plain language, then identifies the affected chapter. Material corrections follow the same pattern but are flagged in the dated register alongside the original entry.
Each entry uses a verifiable date format (YYYY-MM-DD). Where the source publication date differs from the verification date, both are listed.
The register is opinion-free. Editorial commentary appears in the rulebook chapter, not in the register.
How to read the dated entries.
Each dated entry in the dated update register is a single rule, product or policy note. The entry does not include interpretive commentary; the commentary lives in the affected chapter. The entry is short, dated, and cites the public source of the change.
The register is opinion-free; it is a ledger of verified changes. Editorial commentary is described in the affected chapter, not in the register. Where the commentary is wrong, the corrections-handling cadence is described in the disclosure page; corrections are also noted in the dated register.
Where to find the full register
The RSS feed at /feed.xml delivers each entry to feed readers. The horizontal story rail on the homepage surfaces the latest five entries above the news list. The dated register in this register is the canonical surface; the RSS feed and the homepage rail are derived from it.
What changes are not described here
Operator-specific promotional changes (welcome bonus values, limited-time offers, referral values) are not described in this register. Operator-specific changes are platform-defined and frequently-changing; they are not part of the editorial scope.
Why a dated register, in plain language.
The dated update register exists because adult readers deserve a running record of what changed, when it changed and why. A reader who re-opens the news chapter after a month away should be able to scan the register and know which chapters have been touched since they last visited. The register is not editorial commentary; the commentary lives in the affected chapter. The register is a ledger.
How the entries are sourced
Each entry cites the public source of the change. Where the source is a primary regulator (MeitY, the Online Gaming Act 2025, a state-level notification), the entry names the regulator. Where the source is a public rulebook, the entry names the rulebook. Where the source is a platform-side change, the entry notes it but does not adopt operator-specific language.
What the register covers
The register covers rule amendments, product changes and policy updates as they are verified. The register does not cover operator-specific promotional changes (welcome bonus values, limited-time offers, referral values) because those are platform-defined and frequently-changing.
The corrections path
Corrections to the register are sent to the editorial email. Material corrections are noted in the register itself alongside the original entry. The corrections-handling cadence is described in the disclosure; the cadence is 5 working days for editorial corrections and 30 days for material corrections.
The published feed
The published feed at /feed.xml delivers each register entry as an RSS item. Feed readers can subscribe to the feed to receive new entries automatically. The feed is regenerated whenever a new entry is published; the feed-discovery link is included in every HTML page's <head>.
Editorial opinions
The register is opinion-free. Editorial commentary appears in the rulebook chapter, not in the register. The commentary is always backed by the public source; the commentary does not adopt operator-specific language where the operator disagrees with the public source.
How to read the entries without re-reading everything.
A reader who already knows the rulebook can read the dated update register without re-reading the rulebook chapter. Each entry is self-contained and cites the public source. The reader who has the time to re-read the affected chapter will get the full context; the reader who does not have the time can rely on the entry alone.
The entry versus the chapter
The entry is the short note; the chapter is the long-form content. The entry describes what changed and why; the chapter explains the broader rule pattern. The two reading layers serve different purposes: the entry is the alert, the chapter is the deep-dive.
Why the editorial desk keeps a register
The register exists so readers can track material corrections and rule amendments without scanning each chapter. The register is published in plain language; the register's cadence is described in the disclosure.
What the register covers
The register covers rule amendments, product changes and policy updates as they are verified. The register does not cover operator-specific promotional changes (welcome bonus values, limited-time offers, referral values) because those are platform-defined and frequently-changing.
What the register does not cover
The register does not cover editorial opinions; the opinions appear in the affected chapter. The register does not cover the publication's financial relationships; the relationships are described in the disclosure. The register does not cover the responsible-play map; the map is described in the responsible-play chapter.
How to subscribe
Subscribe to the /feed.xml feed in any RSS reader. The feed delivers each new register entry as an RSS item. Feed readers refresh automatically; the reader who relies on the feed does not have to revisit the register page to see new entries.
Where the dated register ends and the rulebook begins.
The dated register ends at the bottom of this page; the rulebook begins at the affected chapters. The reader who has caught up on the dated register and the affected chapters has the publication's full context for the period covered by the register.
How to use the register during a slow news week
During a slow news week, the register may have no new entries. The reader can use the gap to revisit older entries and read the affected chapters. The revisit is the cleanest way to confirm the publication's coverage of the period.
How to use the register during a fast news week
During a fast news week, the register may have several new entries. The reader can prioritise by date: the most recent entries are the most likely to require action. The older entries can wait until the immediate work is processed.
Reading the register as part of the publication's reading experience.
The register is part of the publication's reading experience; the register exists because readers deserve a running record of what changed, when it changed and why. A reader who has caught up on the register has caught up on the publication; a reader who has not caught up on the register has not caught up on the publication.
How the register complements the chapters
The register complements the chapters: the register is the ledger of changes; the chapters are the long-form content. The two reading layers are designed to work together: the register announces a change, the chapter describes the change in detail, the next register entry confirms the change has been applied.
Why the cadence is monthly
The cadence is monthly because the public sources (MeitY notifications, state-level notifications, the platform's own release notes) update on roughly that timescale. A faster cadence would produce empty entries; a slower cadence would miss material changes. The monthly cadence is the sweet spot for the publication's editorial scope.
What the register excludes
The register excludes operator-specific promotional changes (welcome bonus values, limited-time offers, referral values) because those are platform-defined and frequently-changing. The register excludes minor wording changes that do not affect the rulebook reading. The register excludes routine corrections that are surfaced on the affected page within the corrections-handling cadence.