Public Data
A live page looks empty or stale
Check whether API health, source freshness, D1 storage, or cached/demo fallback explains the view before making claims.
Status
Check whether the site data is healthy.
Use Status when a page looks empty, stale, or surprising. It is a trust and release-health page, not a beginner starting point.
Runtime Overview
Health, storage, and upstream freshness in one operational view
Use Status When
You are checking trust and release health, not learning the basics
App Contract
The Android trainer needs verification
Confirm the app-facing endpoints for config, home, coach, packs, daily, scenarios, and progress before rebuilding or testing the app.
Release Health
A large batch just changed the site
Check static artifacts, cache policy, generated freshness, asset budgets, and public paths after broad content or UI work.
Lookup shortcuts
Lookup Tool Shortcuts
Show status details
Interpretation Guide
What to do when a live-derived page looks empty, stale, or surprising
Show interpretation guide
Live data loaded
Use it for prioritization
Counts and cards can guide triage, but still validate affected assets, source confidence, vendor guidance, and business impact before disruptive work.
Demo or cached data
Treat it as orientation
Demo-backed or cached views are useful for checking workflow and layout. They should not become current risk claims without source validation.
Filtered empty
Try broader context
An empty filtered view can mean the filter is narrow, not that risk is absent. Clear filters, use Search, or pivot to Site Map before concluding there is nothing to review.
Unavailable
Check health before action
If the API, news stream, or live-derived campaign view is unavailable, avoid urgent claims based on missing counts. Use Diagnostics and original sources first.
Degraded feed
Treat counts as partial
Degraded upstream sources, parser errors, or missing live endpoints can make queues look lighter than reality. Use Status details as a data-quality signal before reporting totals.
Parser yield
Know what was extracted
Parser yield explains how many structured records were extracted from upstream material. Low yield can mean format changes or quiet sources; it is not proof that no vulnerabilities exist.
App API Contract
Endpoints that feed the Android practice shell
Show app API contract
Start Here
Health and app-home contract
Use Health to confirm D1 binding state and app metadata. Use App Home to confirm daily, coach, packs, shortcuts, progress source, and local-first trust wording.
Coach
Recommendation contract
Coach exposes focus lanes, role tracks, packs, milestones, profile options, and local-state keys for the site and Android app.
Guided Practice
Guided route contract
Guided Practice returns hydrated scenario routes with `id`, `scenario`, and `pack` query parameters so the Player can preserve route context.
Progress
Device-scoped practice state
Progress returns lightweight D1 rows when a device id is available, otherwise a fallback summary. It is practice telemetry only, not identity or certification proof.
Static Site Health
Generated artifacts, cache policy, and release guardrails
Data Transparency
How to interpret live, cached, unavailable, and derived states
Vendor Advisory Connectors
Official vendor enrichment coverage and limitations
If status is degraded: treat live-derived counts as incomplete, check Diagnostics, and rely on saved or manually validated source links before making urgent decisions.
Live Advisory Stream