METHODOLOGY & CORPUS GOVERNANCE
What “verified” means here.
Precision is the product. This page defines exactly what our verification claims mean, where their limits are, and — jurisdiction by jurisdiction — what our monitoring actually covers today. The table below renders live from the same registry the platform itself relies on; it is never edited by hand.
Citations and verification
A citation is a reference from a claim in Qanun output to a specific provision in our corpus — a rulebook section, article or regulation, carried with the rulebook version and effective date of the text relied upon.
When we state that a citation is “verified”, we mean it has been resolved to a provision and version present in our corpus at the stated time. It is not a warranty that the corpus is complete, that the provision has not changed since the last successful check, or that the provision legally supports any particular conclusion. That judgement remains the practitioner's.
A claim whose citation cannot be resolved is not silently kept: it is flagged, downgraded below the verified tier, and gaps are shown as gaps.
Versions, repeal and commencement
Every document in the corpus is versioned. Superseded versions are retained and marked as such — they remain available for point-in- time work but are never presented as current. Public statistics distinguish documents in force from the total including superseded versions. Where a repeal or a commencement date is recorded in the source material, the affected provision carries it, and output citing a provision pins the version relied upon so you can see exactly which text an answer used.
Binding rules are distinguished from non-binding material: corpus documents carry tier labels separating rulebooks and regulations from guidance, consultation papers and enforcement material, and research output surfaces those labels rather than flattening everything into “the rules”.
Confidence tiers
Every claim in a research note carries a written tier: VERIFIED (citation resolved as defined above), SUPPORTED (grounded in corpus material that supports but does not settle the point), INFERRED (reasoned from the material, stated as inference), and SPECULATIVE (flagged as conjecture). A claim without a resolved citation is never presented above INFERRED.
Coverage, live
Per jurisdiction: what is in the corpus and whether automated version-change detection is currently operating. This renders from the version-check registry at request time. Corpus as of 2026-07-23.
| Jurisdiction | Documents | Provisions | Version checks | Last successful check |
|---|---|---|---|---|
ADGM FSRA | 1,098 | 12,641 | partially monitored Version checks operate for only some instruments (9/13 checks working) — version checks error against the registered portal URL | 2026-07-21T02:22:56.655408+00:00 |
DIFC DFSA | 1,095 | 9,579 | monitored Automated version checks are operating (21/21 checks working) | 2026-07-21T02:24:27.904984+00:00 |
VARA — Dubai VARA | 20 | 2,483 | partially monitored Version checks operate for only some instruments (0/12 checks working) — version resolution works but no corpus-grounded baseline exists to compare against | none recorded |
El Salvador CNAD | 17 | 2,370 | not monitored No working automated version check (0/5 checks working) — no checker implemented for portal type(s): cnad_el_salvador | none recorded |
BVI FSC | 28 | 1,273 | not monitored No working automated version check (0/6 checks working) — source blocks automated access (Cloudflare) | none recorded |
Panama SMV | 7 | 1,108 | not monitored No working automated version check (0/3 checks working) — no checker implemented for portal type(s): panama_smv | none recorded |
Other / unregistered sources Context material | 13 | 0 | Mondaq (commentary): 2 · UAE Federal: 11 — counted in the corpus totals but not presented as a monitored jurisdiction. | |
The Documents column above sums to the 2,278 in-force headline exactly.
Version-change detection operates for jurisdictions marked 'monitored' only; for others, absence of alerts is not evidence of no change.
When coverage degrades, we say so
Where automated version-change detection is not operating for a jurisdiction, the platform does not pretend otherwise: monitoring snapshots for that jurisdiction carry an explicit caveat that the absence of change records is not evidence of no regulatory change, and the same status appears in the table above. A jurisdiction whose checker cannot be confirmed as working is reported as “unknown” — unknown is treated exactly like not-monitored, never like healthy.
The same rule applies to this website: every corpus statistic on every public page renders from one live endpoint. If that endpoint is unreachable, pages show “—” and a note that statistics are temporarily unavailable — never a stale number.
Our Terms of Service incorporate this page by reference once published. Terms status
← Back to qanun.io