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

Term	Definition
Affirmative null	The 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.
Analyst Briefing	The 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.
Area	A 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.
Artefact	A 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 dock	The 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

Term	Definition
Batch lane	The 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 line	The 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.
Budget	The 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

Term	Definition
Change Monitor	The 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 audit	The post-generation pass that attaches numbered citation markers to editorial sentences. Reports its own status — an amber Citation audit partial / failed / timed out chip means some markers may be missing, not that the scan failed. See Items, sources and citations.
Citation marker	A numbered [N] marker on the narrative or summary pointing at the source in this scan’s pool that backs the sentence. An attributor, not a fact-checker. See Items, sources and citations.
Confirmed event	A 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 movement	A 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 area	A 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 jurisdiction	A free-text jurisdiction (South Africa, UAE, ASEAN, …) added when no built-in fits. See Jurisdictions and topics.

D

Term	Definition
Detail card	One 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

Term	Definition
Engine	One 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 type	The 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.
Executive narrative	The long-form prose briefing in a snapshot, read on the Analyst Briefing tab. Distinct from the structured executive summary.
Executive summary	The structured digest in a snapshot — a bottom line plus an ordered list of priorities. See Core concepts.
Expedite	The 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.
Export	The 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

Term Definition

Feed The 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.

Fingerprint Two 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.

Term	Definition
Feed	The 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.
Fingerprint	Two 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

Term	Definition
Graph	The dashboard’s relationship-graph reading of a snapshot, available under More when the loaded scan carries graph data.

H

Term	Definition
Heatmap	The 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.
Horizon	The 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

Term	Definition
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.
Ident	See Scan ID (ident).
Impact	The 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.
Instrument	A 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.
Item	One 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

Term	Definition
Jurisdiction	A 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

Term	Definition
Kicker	The short capitals label above a headline — the Briefing masthead’s kicker reads Analyst Briefing; Studio’s restates the loaded scan. See Briefing.

L

Term	Definition
Likelihood	How 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.

M

Term	Definition
Map	The dashboard’s geographic reading of the snapshot — jurisdictions on a world map, coloured by activity. Always present under More.
Masthead	The 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 Snapshots	The 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

Term	Definition
Newly observed	A 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 run	A 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.

O

Term	Definition
Order form	The 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 ticket	The 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.
Overview	The dashboard’s first tab: the heatmap, headline stats, and the What’s changed card. The default reading of a loaded snapshot. See Overview.

P

Term	Definition
Planner	The 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.
Priority	One entry in the executive summary’s ordered list — the developments the analysis judges most worth your attention, walked in order by the Briefing.
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 chip	The 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

Term	Definition
Rate limit (API)	The per-key request budget on `/v1`, bucketed by operation category and signalled in response headers. See Rate limits.
Region preset	A 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.
Regulator	The 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

Term	Definition
Scan	One 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 Ready	The 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 toast	The 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 scan	A saved configuration with a cadence and timezone (and optional email notification) that runs itself, extending its series with each run. See Scheduled scans.
Scope	The 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.
Sentiment	The 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.
Series	The 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.
Snapshot	The 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-reference	The mechanical badge on an item’s source URL — ✓ verified (URL found in the scan’s retrieved corpus), ≈ domain (same domain, different page), ? unverified (neither). See Items, sources and citations.
Source tier	The classification of a surfaced source — Primary regulator · Supranational · Aggregator · Other source — totalled on the Sources tab. See Sources.
Sourcing confidence	The in-generation chip on an item — Primary regulator source (high), Supranational body (medium), Secondary commentary (low). See Items, sources and citations.
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.
Standfirst	The one-sentence framing under a headline (“Three priorities for the quarter ahead — EU · UK.”) — newspaper vocabulary the Briefing masthead borrows. See Briefing.
Status	An item’s lifecycle stage — Proposed · Consultation · Final Rule · Implementation Phase · Effective. Independent of impact and likelihood. See Items, sources and citations.
Studio	The surface where a snapshot becomes artefacts — documents, decks, images, podcasts, video — with generation queue, gallery and inline players. See Studio.

T

Term	Definition
Tearsheet	A 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 strip	The 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, archive counts on Snapshots, the next run time on Scheduled. See The app at a glance.
Timeline	The dashboard’s calendar reading — dated items laid out by expected date with a Today marker, one swimlane per jurisdiction. See Timeline.
Topic	A 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.
Translation	An 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.
Trend	A 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 Scorecard	The Sources-tab panel totalling the scan’s trust signals: editorial claim coverage, sourcing-confidence mix, cross-reference mix, source-tier mix and tunnelling count. See Sources.
Tunnelling	The silent upgrade of an aggregator link to the primary regulator’s own document, with the reason kept in the chip’s tooltip and the count on the Trust Scorecard. See Items, sources and citations.

U

Term	Definition
Unverified assertion	A 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

Term	Definition
View source	The link on an item’s detail card to the document behind it — the fastest route from a claim to its evidence. See Items, sources and citations.

W

Term	Definition
What’s changed	The 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.
Wizard	An older name for the scan configuration form — see Order form.