Clara Vella, MaltaMGA editor. Licensing and compliance specialist. Independent, non-commercial source-reading notes. Corrections: clara@maltamga.com
2 stories
·
0 followers

Clara Vella: editor and source-reading notes

1 Comment

Clara Vella

I am Clara Vella, editor of MaltaMGA and a Malta-based licensing and compliance specialist. This notebook is a place for short explanations about reading regulatory records and keeping a clear trail from a statement to its source.

Editorial work

My subject areas include MGA B2C and B2B licensing, regulatory approvals, corporate governance, AML, KYC and responsible gambling. I have worked in legal and regulatory roles since 2011, moved into iGaming licensing and compliance in 2014, and have worked independently as a senior licensing and compliance consultant since 2022.

At MaltaMGA I maintain the guide, check licence and enforcement information against original records, and review corrections. The guide is independent of the Malta Gaming Authority and gambling operators. It is non-commercial public information and does not recommend where to gamble.

What this notebook adds

A short answer can hide a long chain of assumptions. I use these notes to make that chain visible: what was searched, which record was read, which exact entity or website it concerned, and when it was checked. A source can support a specific finding without supporting every broader conclusion someone might draw from it.

My editorial method explains the main guide's approach. Other selected writing is available in my regulatory reading notebook, and my detailed public profile brings together my background and work references.

Contact and corrections

Email clara@maltamga.com for an editorial question or factual correction. Include the page, the statement in question and an original source where possible. These explanations are public information, rather than advice for an individual legal matter.


Clara Vella edits the independent, non-commercial MaltaMGA guide. Contact and corrections: clara@maltamga.com.

Read the whole story
claravellamga
4 hours ago
reply
About this reading list: I am Clara Vella, editor of MaltaMGA and a Malta-based licensing and compliance specialist. I have worked in legal and regulatory roles since 2011 and independently as a senior licensing and compliance consultant since 2022. My subjects include MGA licensing, AML, KYC, responsible gambling and corporate governance.

I use this public notebook to explain source-reading decisions. MaltaMGA is independent, non-commercial public information, separate from the Malta Gaming Authority and operators. I check original records and review corrections; I do not recommend where to gamble.

Full biography and selected work: https://maltamga.com/about/#editor . Other editorial notes: https://claravella.mataroa.blog/ . Corrections: clara@maltamga.com — include the statement, page and primary source.
Malta
Share this story
Delete

A source note needs two dates

1 Comment

When I read a regulatory record, I keep the date of my observation separate from any date stated in the record. Those dates answer different questions. The source might describe a decision made earlier; my note records when I actually saw that source.

This is a small data-design choice with a practical effect. If a reader returns later and finds a changed entry, the note still says what was checked and when. It does not pretend that an old observation is a live check.

A deliberately incomplete example

The following JSON is an illustrative record design. It is not a real licence, operator, domain check or regulatory finding. The reserved domain and conspicuous placeholder reference help keep examples separate from evidence.

{
  "legal_entity": "ILLUSTRATIVE ENTITY — NOT A REAL OPERATOR",
  "licence_reference": "ILLUSTRATIVE-NOT-A-LICENCE",
  "domain": "example.invalid",
  "status": "not_checked",
  "source_url": "https://www.mga.org.mt/licensee-hub/licensee-register/",
  "source_stated_date": null,
  "observed_at": null,
  "notes": "Example structure only; no check has been performed."
}

The source link identifies a place to begin a real check. Its presence does not turn the other fields into verified facts. In particular, a source URL and an empty observation date should not produce a reassuring green badge in a user interface.

Preserve uncertainty explicitly

I use null for a date I have not established, rather than substituting today's date. I also keep not_checked distinct from a negative finding. “I have not checked this” and “I checked this and found no matching entry” are different observations.

The same care applies to identity. A legal entity, a licence reference and an exact website should be separate fields. If the names differ, that is something to investigate and explain, rather than something to erase by putting all three into a single title field.

Make the note useful to another reader

A good record should let another person understand the scope of the observation. That means retaining the original source, the actual check time and a short explanation of what was compared. It also means keeping an illustrative example visibly separate from production data.

The MGA's own register page links to its licensee register and URL checker. My editorial method describes how I approach source reading for MaltaMGA. Neither an example schema nor an old note replaces a fresh check of the relevant original record.


Clara Vella edits the independent, non-commercial MaltaMGA guide. Contact and corrections: clara@maltamga.com.

Read the whole story
claravellamga
4 hours ago
reply
Reading note: the date stated in a source and the time I observed it answer different questions. A record can have no established source date without borrowing today's date. The illustrative JSON in my notebook deliberately leaves both dates null and keeps not_checked distinct from a negative finding. This is a data-literacy example, not a live licence check. Before drawing a conclusion, compare the legal entity, licence reference and exact domain against the current original record. Method: https://maltamga.com/#method
Malta
Share this story
Delete