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
Updating…
| Coverage unit | Domains | Status | Source period | Completeness | Verified against LDG | Source version | Allowed purpose |
|---|---|---|---|---|---|---|---|
| Loading… | |||||||
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.
Not implemented in this build: staffOperationPreview answers 501. Nothing is sent. No screen in this console calls it, so the affordance most staff page contracts require is missing from the client as well as from the service.