DEMO TENANTOperator-side data (staff, contacts, calendar, training, grants, complaints, SAR, four-eyes reviews) is illustrative — not a real Greentube record. Connector output, evidence-ledger anchors, RFC 3161 timestamps, Postgres RLS, regulator-source ingestion and LLM extractions are the real machine. Rows marked demo are seeded fixtures.
Georg Gubo
MGA · UKGC · ADM · RO-ONJN · SK-MFSR · DGOJ · GGL · SPI · NJ-DGE · MI-MGCB · PA-PGCB

Complaints

LCCP 6.1 register · 24h ack / 14d first / 8w final · OP-GREENTUBE
Total
12
Open
7
24h ack overdue
3
14d first overdue
5
8w final overdue
1
ADR escalated
2
Resolved (30d)
4
Show:AllOpenOverdueResolvedADR-escalated

Register (2)

RefReceivedJurisdictionCategory24h ack14d first8w finalStatusOutcome
GT-2026-01192026-05-11dgojGame outcome✓ done✓ done✓ doneResolvedrejected
GT-2026-00422026-03-16ukgcBonus terms✓ done✓ donelateADRescalated adr

How this works

Every state-change anchors a player_complaint_attested claim in the evidence ledger — chain-hash linked to your tenant's posture root. The worker tick scans every 30 minutes and raises a Finding on COMPLAINTS.HANDLING when any of the three SLA clocks breach. Severity escalates: medium at 24h ack, high at 14d first response, critical at 8w final response. Findings auto-route via your org-units and never replace the MLRO's substantive decision — KURAL is the workflow rail, not the decision-maker.