Read the rule.
Understand
the implications.

Gaming regulation meets technical practice. Clear, source-led research for the people turning policy into product decisions.

Annotated source record connecting a customer interaction clause to its scope and evidence status
01 / The annotated dossier · An original illustration of our reading method

The research desk

All briefs
Licensing

What does a licence actually cover?

A jurisdiction is a starting point. The useful question is which activity, entity and market an authorisation covers.

Sources checked · 6 min
Technical operations

Build a record you can explain

Connect a customer event to its source, decision and version. Keep access-to-history rules separate from retention policy.

Sources checked · 6 min
Software provenance

Trace the software. Keep the evidence.

Follow the documents that connect a software release to its origin, test scope and accountable parties.

Sources checked · 7 min
Reading regulatory sources

A document is not a duty

The publisher’s name is only the first check. Document type, legal status and a precise scope determine what a statement can support.

Sources checked · 8 min
Document control

Read the change, not just the date

An announcement date, a version label and an effective date answer different questions. Keep the trail and record the gaps.

Sources checked · 8 min

Three ways into the evidence

Our method ↗

Start with a question

What does an authorisation cover? What should an evidence trail explain? Our briefs begin with a practical product question and keep the source separate from the implementation advice.

Understand the scope →

Start with a jurisdiction

Malta and Great Britain have different authorities, document families and scopes. Use each dossier as a reading map, with explicit limits on what has been checked.

Read the dossiers →

Start with a document

Inspect a source, its review date and the narrow statement it supports. Contextual references stay visibly separate from verified source requirements.

Inspect the records →

Every conclusion needs a paper trail.

The document matrix connects eight source records to their jurisdiction and technical domain. Filter the collection, open a provenance note and take a CSV or TSV copy into your own research.

It is a bounded reading aid, not a complete list of obligations. A checked source is not a legal opinion on your product.

Use the document matrix
RL-001Account historyGreat Britain
RL-003Customer interactionGreat Britain
RL-006Critical gaming supplyMalta
Evidence workflow: read the source, establish scope, preserve evidence123Read the sourceEstablish scopePreserve evidence
An editorial workflow. Each transition needs a documented decision.

Useful distinctions, before decisions

We write for engineers, product compliance teams and operational reviewers who need to ask more precise questions. A licence is not a product test report. A document’s publication date is not necessarily its effective date. Access to account history is not a retention schedule for every log. These distinctions shape what evidence a team needs to collect.

Each brief includes original editorial analysis and a practical example. Examples are identified as synthetic; official sources support only the statements attributed to them. We do not assess individual businesses, offer legal services or promise that a design is compliant. Read our publication statement and source method before using this research in a decision.