Non-production environment: development. Nothing shown here is live market data.
Skip to main content
Staff console

Coverage and freshness

Note: What this screen can and cannot tell you about freshness

Every row states the period the source itself covers, the source version the provider names, and where that answer came from. There is no ingestion time here on purpose: loading data today does not make it recent, and a screen that showed the load time would answer a different question than the one an operator is asking. The freshness SLO and the actual last source update DAT-005 asks for are not part of what staffCoverageGet returns in this build, so they are stated as missing rather than approximated.

Query coverage

Separate with commas. Leave empty for every unit the service will return; it bounds the answer, this screen does not.

The source period is the period the source COVERS, not when this deployment loaded it — a unit can be freshly loaded and still cover an old period. The source version is shortened to its first twelve characters; the whole digest is on the cell.

Separate with commas. Leave empty for all domains.
The purpose you state is recorded with the read and echoed back on every row. It does not widen what you may see.
Updating…
Coverage units with the period their source covers, its version and provenance, and the purpose this read was made for.
Coverage unitDomainsStatusSource periodCompletenessVerified against LDGSource versionAllowed purpose
Reading…

Freshness fields DAT-005 requires that this build does not return

The contract asks this screen for a freshness SLO and the actual last source update alongside the period and version. staffCoverageGet returns neither, so neither is shown. No substitute is displayed in their place: an ingestion timestamp presented as freshness is exactly the failure DAT-005's first acceptance criterion names.

Not implemented in this build: staffDataIssueUpdate has no handler and no client wrapper. Nothing is sent. Assigning an upstream gap owner is not available here.
The preview mechanism exists and is used — every decision on the Approvals screen is previewed through staffOperationPreview. What is missing is anything on THIS screen to preview: the protected action a coverage gap would raise is staffDataIssueUpdate, which is not registered, so there is nothing here for a reviewer to be shown.