Upcoming regulatory changes
LLM-extracted from regulator announcement pages across 12 jurisdictions. Review each impact before pushing tickets to your team.
Upcoming changes detected
1
Impacts pending review
5
LLM-processed
1
Changes
| Regulator | Effective | Summary | Confidence | Impacts | |
|---|---|---|---|---|---|
| UKGC | 7/31/2026 | UKGC publishes amendments to RTS 14E (game-information display) requiring an in-session player-spend summary panel to be visible within two clicks at all times. Operators have 90 days from publication to comply. Existing RTS Annex A reporting requirement expanded to include the new panel-availability metric. | AI 92% | 6 5 pending | Open → |
How this works
KURAL watches official regulator announcement pages across all configured jurisdictions daily. When the page hash changes, the LLM extraction pipeline pulls the summary, effective date, and cited clauses out of the regulator's text via Claude Sonnet, then maps cited clauses to existing controls in your library via the source-citation index. Every extraction is logged with token cost + prompt hash in LlmCallLog.
AI-assessed fields show their confidence — anything below 85% waits in the per-impact review queue (open a change to triage). Once impacts are approved you can push them to Jira as future_compliance_gap findings — due date is set to the effective date minus 30 days.