Skip to Content

Glossary

Short definitions for the terms used across Using Snapshot, the Core concepts section, and the developer API, using the product’s own on-screen vocabulary. Entries tagged (API) are developer-facing.

A

TermDefinition
Affirmative nullThe Change Monitor’s honest empty state: when no confirmed event touched your instruments, the card lists what the regulators in your scope did publish in the window instead of showing an empty box — so “no change” is evidence, not silence. See What “changed” means.
Analysis (citation result)A sentence, or part of one, that is the briefing’s own reading of the facts — what they mean, require or signal. Not checked against a page, by design, and counted apart from checked claims. See Items, sources and citations.
Analyst BriefingThe dashboard tab that renders a snapshot’s executive narrative as readable prose, with numbered citation markers and an inline audio player. Present whenever the snapshot carries a narrative. See Briefing.
API key (API)The credential for the /v1 API — a regsn_live_… string created and revoked from the dashboard, sent as a bearer token in the Authorization header. Shown in full exactly once at creation. See Authentication.
AreaA broad policy domain (Capital Markets, AML / KYC, ESG / Sustainable Finance, …) — one of a scan’s three coordinates, alongside jurisdiction and horizon. Anything not built in can be added as a custom area. See Jurisdictions and topics.
ArtefactA generated output derived from a snapshot — document, slide deck, image, audio or video. Produced in Studio or via POST /v1/exports; the API spells the field artifact_type.
Audio dockThe mini-player that pins to the bottom of the window when audio artefacts are playing or queued — play/pause, a seekable waveform, a queue and volume — and follows you around the app. See Studio.

B

TermDefinition
Batch laneThe deferred, cheaper way to run work. On the order form, Batch — later today costs roughly half the Expedite price, with results typically arriving within a few hours (optionally announced by email); scheduled scans default to it, and Studio generation uses a batch lane unless Expedite is on. Not every engine or export route has one. See Your first scan.
Bottom lineThe one-line distillation of the scan — the thing to read if you read nothing else. Shown on the Overview hero and as the closing line of the Briefing, when the scan produced one.
BudgetThe account-level spending pool that all scans and exports draw on — the same pool whether the work is started from the app or the API. See Usage.

C

TermDefinition
Change MonitorThe What’s changed card on the Overview tab, comparing the loaded snapshot with your previous scan of the identical scope. Reports confirmed regulator events, coverage movements and unverified assertions as three separate strata, and recomputes on read — an older snapshot’s change view improves as event coverage does. See What “changed” means.
Citation auditThe post-generation pass that splits every cited sentence — in the narrative, the enforcement priorities and the item summaries — into claims and checks each factual claim against the pages the scan read, giving each a result: Verified, Source located. Check wording, No source found (plus Analysis for our own reading). It checks the briefing against those pages, not the pages against the world. See Items, sources and citations.
Citation audit statusThe audit’s own coverage report — Citation audit complete (with a quiet count such as 1 of 84 unchecked when a few sentences could not be checked), amber Citation audit partial (a whole section, or more than one cited sentence in ten, unchecked), failed (none could be checked) or timed out. None of these means the scan failed or that any finding is wrong. See Briefing.
Citation numberThe small number on a cited sentence. It opens the sentence’s claims, each with its result, the page’s own quoted words and the page’s tier. A sentence with no sourced claim carries none. On older snapshots, a numbered [N] marker that names the backing source without checking the claim. See Items, sources and citations.
Confirmed eventA Change Monitor entry backed by a dated regulator document — Consultation opened, Consultation closed, Rules adopted, Date set or moved, Guidance issued, Enforcement, or Regulator activity. The only stratum allowed to headline the card. See What “changed” means.
Coverage movementA Change Monitor entry recording how the composition of the report moved between runs — Newly observed and Not shown this run — as distinct from change in the world. See What “changed” means.
Custom areaA free-text area (often a specific topic — DORA Article 28, Pay-to-Play) added on the order form when no built-in area fits. Treated as a first-class category by the analysis. See Jurisdictions and topics.
Custom jurisdictionA free-text jurisdiction (South Africa, UAE, ASEAN, …) added when no built-in fits. See Jurisdictions and topics.

D

TermDefinition
Detail cardOne item’s full record — fields, badges and trust chips — shown as a card inside the slide-in Item Detail panel that opens from a heatmap cell, a map country or a timeline entry. See Overview.

E

TermDefinition
EngineOne of the product’s analysis engines, compared — with a live cost figure for each — in the order form’s Advanced section and shown on every ledger row in My Snapshots. Engines differ in verification support, batch availability and cost; the API lists their ids at GET /v1/meta/engines.
Entity typeThe who hint on a scan (Global Asset Manager, Hedge Fund, Payments / Fintech, …). Angles impact and priority judgements towards firms like yours without changing what is scanned. See Jurisdictions and topics.
Evidence chipThe chip on an item (and in the Sources list) naming the strongest tier among the pages that verified one of its claims — Verified on primary regulator pages, Verified on supranational pages, Verified on secondary sources only, or Not verified. A page that only located a claim does not count. Replaces the sourcing-confidence chip on new scans. See Items, sources and citations.
Executive narrativeThe long-form prose briefing in a snapshot, read on the Analyst Briefing tab. Distinct from the structured executive summary.
Executive summaryThe structured digest in a snapshot — a bottom line plus an ordered list of priorities. See Core concepts.
ExpediteThe full-price, real-time run lane. On the order form, Expedite — run now streams results into the dashboard as they arrive; in Studio, the Expedite toggle moves artefact generation from the batch lane to real time (at roughly double the cost) and persists as an account preference. See Studio and Settings.
ExportThe act (and result) of deriving an artefact from a snapshot. Runs as an asynchronous job: queued → processing → completed / failed / cancelled. See Studio and POST /v1/exports.

F

TermDefinition
FeedThe always-live wire of recent regulator announcements across all jurisdictions, independent of any scan — with a one-tap filter down to the loaded scan’s scope. See Feed.
FingerprintTwo distinct objects share the name. The scope hash — _meta.inputFingerprint to API callers — is derived from a scan’s jurisdictions, areas and custom topics, deliberately blind to engine and horizon; snapshots with the same scope hash group into a series. The cost-estimate fingerprint returned by POST /v1/scans/estimate is a separate, structured bucketing of the configuration that does include the engine and the date range. See Scans and snapshots.

G

TermDefinition
GraphThe dashboard’s relationship-graph reading of a snapshot, available under More when the loaded scan carries graph data.

H

TermDefinition
HeatmapThe Overview tab’s grid — areas × jurisdictions, each cell printing a pressure score out of 10 that weighs impact by likelihood; the item count lives in the cell’s tooltip. See Overview.
HorizonThe forward window a scan looks across — 3, 6, 12, 18, 24 or 36 months. Items need dates inside it. Not part of scope: lengthening the horizon extends a series rather than forking it. See Jurisdictions and topics.

I

TermDefinition
Idempotency key (API)A client-supplied header on POST /v1/scans and POST /v1/exports making retries safe — the same key with the same body replays the original response for 24 hours. See Idempotency.
IdentSee Scan ID (ident).
ImpactThe analysis’s call on how much an item matters — High · Medium · Low — angled by your entity type. One of the two inputs to heatmap colour. See Items, sources and citations.
InstrumentA named rule or regime the product tracks across scans. Items bind to instruments, and it is instruments whose confirmed events the Change Monitor reports. See What “changed” means.
ItemOne regulatory development inside a snapshot, at one jurisdiction × area coordinate, with status, likelihood, impact, dates, summary and sourcing. The atom of the data model. See Items, sources and citations.

J

TermDefinition
JurisdictionA country, region or supranational regulator-cluster — the where axis of a scan. Picking one directs coverage across its associated regulators. See Jurisdictions and topics.

K

TermDefinition
KickerThe short capitals label above a headline — the Briefing masthead’s kicker reads Analyst Briefing; Studio’s restates the loaded scan. See Briefing.

L

TermDefinition
LikelihoodHow firm an item is — Confirmed · Likely · Possible; items with no stated likelihood are treated as Uncertain in filters. Independent of status. See Items, sources and citations.
Located (citation result)Source located. Check wording — a page the scan read is about the claim but does not state all of it. Read the page before relying on the detail. See Items, sources and citations.

M

TermDefinition
MapThe dashboard’s geographic reading of the snapshot — jurisdictions on a world map, coloured by activity. Always present under More.
MastheadThe header block at the top of an article-styled tab — kicker, headline and standfirst on the Briefing; the scope and range lines on the Timeline and Snapshots tabs. See Briefing.
My SnapshotsThe ledger of your saved scans, day-grouped, with identical-scope re-runs collapsed into series rows and re-run affordances on each. See Snapshots.

N

TermDefinition
Newly observedA coverage movement: an instrument surfaced in this run that earlier runs did not show, sub-labelled honestly (e.g. in force before your window — newly shown, not new). See What “changed” means.
Not shown this runA coverage movement: an instrument earlier runs surfaced is absent from this one — usually editorial selection, not repeal, and annotated with its presence count. See What “changed” means.
No source found (citation result)None of the pages the scan read or found in its searches states or covers the claim. A result, not a failure: the audit ran and is telling you something. See Items, sources and citations.

O

TermDefinition
Order formThe scan configuration form, reached from New Scan: numbered sections 01–05 (who · where · what · when · output), an Advanced accordion for engine choice, and the live order ticket alongside. Every setting persists from your last scan. Sometimes called the scan wizard. See Your first scan.
Order ticketThe live summary rail beside the order form — it restates WHO / WHERE / WHAT / HORIZON, prices the scan as you build it (“Estimate, not a quote.”), carries the Expedite / Batch choice, and holds the Start scan button. See Your first scan.
OverviewThe dashboard’s first tab: the heatmap, headline stats, and the What’s changed card. The default reading of a loaded snapshot. See Overview.

P

TermDefinition
Page tierWho published a page the audit checked a claim on — Primary regulator, Supranational or Secondary — from our list of regulators, supranational bodies and their domains. It describes the page, not the claim. See Items, sources and citations.
PlannerThe calendar-first view on the Scheduled tab: a month grid of upcoming runs, a next-run hero, the schedule manager and a recent-activity feed. See Scheduled scans.
Primary documentOn an item card, the primary regulator’s page that verified the most of the item’s claims (Primary document ↗). When no primary regulator’s page verified one, the card says No primary document — see the evidence in each citation. See Items, sources and citations.
PriorityOne entry in the executive summary’s ordered list — the developments the analysis judges most worth your attention, walked in order by the Briefing. Priorities are our recommendations, so they carry no citation numbers.
Problem detail (API)The RFC 9457 error envelope on every non-2xx /v1 response — type, title, status, detail, code, request_id, and per-field errors. See Errors.
Provenance chipThe compact regulator · date · doc chip on every confirmed event in the Change Monitor, linking to the dated document behind it. See What “changed” means.

R

TermDefinition
Rate limit (API)The per-key request budget on /v1, bucketed by operation category and signalled in response headers. See Rate limits.
Region presetA one-click jurisdiction bundle on the order form — G7, EMEA, APAC, Americas, EU+, Global Major. Presets replace the current pill selection (hand-added custom jurisdictions excepted). See Jurisdictions and topics.
RegulatorThe authority behind an item (FCA, ESMA, MAS, …). Shown on every item; jurisdictions are shorthand for sets of regulators. See Jurisdictions and topics.
Request ID (API)The X-Request-Id header on every API response, for support correlation. See Errors.

S

TermDefinition
ScanOne run of the analysis over a configuration. Lifecycle: queued → running → complete (saving a snapshot), failed, or cancelled. See Scans and snapshots.
Scan ID (ident)The short mono identifier stamped on a scan when it runs — shown on ledger rows in My Snapshots and in Studio’s scan picker and artefact info cards, and appended to exported artefact filenames where present, so a file can be traced back to its scan. Unlike the fingerprint, a scan ID is unique to a single run. See Snapshots.
Scan ReadyThe green pill that appears in the header chrome when a finished scan is waiting to be loaded — one click loads it; with several waiting, it opens a picker. See The app at a glance.
Scan toastThe floating progress card shown while a scan runs — phase, percentage, cancel, and a View affordance on completion. Scans never block the dashboard. See Scans and snapshots.
Scheduled scanA saved configuration with a cadence and timezone (and optional email notification) that runs itself, extending its series with each run. See Scheduled scans.
ScopeThe identity-defining part of a scan’s configuration — its jurisdictions and areas (custom topics included). Identical scope is what groups snapshots into a series and enables change tracking; engine and horizon sit outside it and may differ between runs. See Jurisdictions and topics.
SDK (API)An official client library wrapping the /v1 surface. See Python SDK and JavaScript SDK.
SentimentThe scan’s overall posture read (for example Tightening.), shown as an aside on the Overview hero and as the attribution on the Briefing’s pull quote. Present only when the scan produced one. See Overview.
SeriesThe snapshots produced by re-running an identical scope, grouped into one ledger row in My Snapshots. The unit of change tracking. See Scans and snapshots.
SnapshotThe fixed, dated record saved by one completed scan — items, trends, executive summary and narrative, sources and audit. The central object; everything else reads from or derives from it. See Core concepts.
Source cross-referenceOn snapshots from before the evidence-based audit, the badge on an item’s source URL — ✓ verified, ≈ domain, ? unverified — recording whether the scan retrieved that URL. New scans report evidence per claim instead (see Citation audit).
Source tierSee Page tier.
Sourcing confidenceOn snapshots from before the evidence-based audit, the Analyst’s own rating of an item’s source — Primary regulator source, Supranational body, Secondary commentary. No longer produced; new scans carry an Evidence chip.
SSE stream (API)The Server-Sent Events channel for a running scan at GET /v1/scans/{id}/stream — progress, completion (with the snapshot envelope), or error. See Scans.
StandfirstThe one-sentence framing under a headline (“Three priorities for the quarter ahead — EU · UK.”) — newspaper vocabulary the Briefing masthead borrows. See Briefing.
StatusAn item’s lifecycle stage — Proposed · Consultation · Final Rule · Implementation Phase · Effective. Independent of impact and likelihood. See Items, sources and citations.
StudioThe surface where a snapshot becomes artefacts — documents, decks, images, podcasts, video — with generation queue, gallery and inline players. See Studio.

T

TermDefinition
TearsheetA two-page A4 PDF summarising a snapshot, generated in Studio in two variants — the clean Overview and the illustrated, style-led Detailed. See Studio.
Ticker stripThe mono readout under the tab bar — ITEMS · JUR · HIGH-IMPACT · DEADLINES · ● SCAN on most tabs — which re-tunes itself per tab: trust statistics on Sources (SOURCED · PRIMARY), archive counts on Snapshots, the next run time on Scheduled. See The app at a glance.
TimelineThe dashboard’s calendar reading — dated items laid out by expected date with a Today marker, one swimlane per jurisdiction. See Timeline.
TopicA theme narrower than an area (MiCA Title III, beneficial-ownership transparency). Injected into a scan as a custom area, where it becomes a first-class axis value. See Jurisdictions and topics.
TranslationAn additional-language rendering of the snapshot’s narrative and content, cached on the snapshot after first use. Covers the dashboard’s seven reading languages; the API additionally accepts pt. See Settings.
TrendA typed cross-item pattern in a snapshot — Convergence (jurisdictions moving towards a shared approach), Acceleration (pace increasing), Interconnected (obligations interlocking across regimes), Divergence (jurisdictions splitting), Emerging (early signals only). See Trends.
Trust ScorecardThe Sources-tab panel summarising the citation audit in two cards — Claims checked · every surface (how many claims are verified or located) and Verified claims by page tier (the share resting on a primary regulator’s own page). Older snapshots show their earlier cells. See Sources.
TunnellingOn snapshots from before the evidence-based audit, the Analyst’s swap of an aggregator link for a primary regulator’s page. Retired: the Analyst now cites the page it took each fact from, and the audit reports which pages stand behind each claim.

U

TermDefinition
UncheckedA cited sentence the citation audit could not check. It keeps the Analyst’s own source, drawn with a dashed underline, and its note says so; the audit status chip counts them. See Briefing.
Unverified assertionA Change Monitor entry the scan asserted but could not tie to a verifiable source document. Visible, marked source not verifiable, and never headline-grade. See What “changed” means.
Usage (API)Request, scan, export and cost telemetry at GET /v1/usage, groupable by day, endpoint or key. See Usage.

V

TermDefinition
Verified (citation result)A page the scan read states the claim; the popover quotes the page’s own words. See Items, sources and citations.
View sourceOn older snapshots and unchecked items, the link on an item’s detail card to the Analyst’s source. New scans show Primary document instead.

W

TermDefinition
What’s changedThe Change Monitor’s card on the Overview tab, and the comparison behind it. API callers can fetch a changes overlay, recorded at scan time, as a snapshot sub-resource. See What “changed” means and Snapshots.
WizardAn older name for the scan configuration form — see Order form.
Last updated on