The envelope coverage dashboard shows how far along each catalog table is in adopting the APRS data envelope. Open it at Admin → Codex coverage (/admin/codex-coverage) to see, at a glance, which tables are fully compliant, which are in progress, and which haven’t started yet.
Why it matters
Every row in the Codex catalog needs a populated record_id to be traceable, deduplicated, and exportable in audit packages. The coverage dashboard gives you a single view into that progress so you can answer questions like:
- How close is my dataset to full APRS compliance?
- Which tables still have unpopulated records?
- Are nightly backfill jobs actually making progress?
What you’ll see
Summary cards
At the top of the dashboard, four summary cards show:
| Card | Description |
|---|
| Tables tracked | Total number of catalog tables with a record_id column. |
| Fully compliant | Tables where ≥ 99% of rows have a populated record_id. |
| Empty / 0% | Tables where no rows have been backfilled yet. |
| In progress | Everything in between — backfill has started but isn’t complete. |
Coverage table
Below the summary cards, a sortable table lists every catalog table, ordered worst-first by default. Each row shows:
| Column | Description |
|---|
| Table | The catalog table name and its source key (if available). |
| Category | The data category the table belongs to. |
| Rows | Total row count in the table. |
| Populated | Number of rows with a populated record_id. |
| % | Percentage of rows that are envelope-compliant, color-coded by bucket. |
| Last backfill | When the most recent backfill job ran for this table, plus how many rows it processed. |
Color-coded status buckets
The percentage column is color-coded so you can scan for problem areas quickly:
| Color | Range | Meaning |
|---|
| Gray | 0% | No rows backfilled yet. |
| Red | < 25% | Early stages — backfill has started but has a long way to go. |
| Amber | 25%–74% | In progress — backfill is underway. |
| Blue | 75%–98% | Almost there — most rows are compliant. |
| Green | ≥ 99% | Fully compliant. |
How data refreshes
Coverage statistics are refreshed automatically by a nightly job that runs at 05:00 UTC, after the backfill window finishes. The dashboard header shows when the last refresh occurred.
You don’t need to trigger refreshes manually. Each nightly run scans every catalog table that has a record_id column, counts total rows versus populated rows, and updates the dashboard.
If a table was recently added to the catalog, it will appear on the dashboard after the next nightly refresh.
When to use it
- During APRS rollout — monitor adoption as backfill jobs work through historical data.
- Before an audit — confirm that all evidence tables are fully envelope-compliant before generating an audit export.
- Troubleshooting stalled backfills — if a table’s percentage hasn’t changed in several days and the “Last backfill” timestamp is stale, the backfill job for that table may need attention.
