Status
What version of the dashboard you're reading, when the data was last refreshed, and the health of the ingestion pipeline. This page is regenerated every nightly build; see "generated at" below.
System version
| Rubric version | v1.7.0 · changelog |
|---|---|
| Rubric frozen at | 2026-05-12 |
| DB schema version | v0 · envelope schema |
| Build commit | bb7685a |
| Coverage target | 13 categories · 184 factors · 20 critical ★ |
| Page generated at | 2026-08-07T00:00:00Z |
Coverage
Per-protocol freshness
0 protocolsNo protocols graded yet. Once M3a (E-18) lands, every protocol's slug, letter grade, last-graded-at, and data-as-of timestamps will appear here, sorted with the most stale rows first.
Color legend: green ≤7d · yellow 8–30d · red >30d · gray ungraded.
Cadence buckets
refresh scheduleEvery factor in the 184-factor taxonomy is annotated with a refresh cadence. Bucket counts are derived from the cadence column in the methodology template; run health below comes from the exported pipeline log.
| Code | Bucket | Factors | Refresh model | SLA | Last run | 30d OK | 30d Err | State |
|---|---|---|---|---|---|---|---|---|
| C | Continuous | 9 | Nightly cron: 4 fetchers | Refreshed every 24h. Stale flag fires above 7 days. | N/A | 0 | 0 | No runs |
| E | Episodic | 37 | Weekly event-checker: 7 fetchers, write only on diff | Re-checked weekly; underlying value only changes on a discrete event. | N/A | 0 | 0 | No runs |
| S | Static | 115 | On-trigger (upgrade event detected) + quarterly curator sweep | Re-graded only when the protocol redeploys or upgrades. | N/A | 0 | 0 | No runs |
| RT | Real-time | 24 | Deferred to v1.1: needs streaming infra, not a cron | Not graded at v1.0; surfaced once the signal-engine ships. | N/A | N/A | N/A | Deferred |
Examples and full per-factor mapping: see methodology.
Pipeline run history
unwiredRun history not yet wired. When E-30 Phase 3 lands, this section renders the last 30 invocations of refresh-continuous.py and refresh-events.py, with per-fetcher success/error counts, protocols touched, and duration.
Until then, freshness above is computed directly from per-protocol envelopes (graded_at / data_as_of), not from a separate run log.
Data freshness policy
- Green: last-updated within 7 days. Treat as current.
- Yellow: 8 to 30 days. Episodic factors expected to land here between weekly sweeps; static factors are normal at any age.
- Red: > 30 days for a continuous-cadence factor, or > 90 days for an episodic factor. Surface as a stale-data flag on the protocol page.
- Gray: never assessed. Pre-M3a state for new protocols.
Active incidents are surfaced via the per-protocol incident banner and do not change the structural letter grade (PD-033). The EVENT badge mechanism returns alongside the v1.1 streaming-signal engine.