Drift watch and production outcomes
Drift watch re-audits one pinned version on a schedule (daily, weekly, or monthly) and reports when its score leaves the range measured at calibration. The artifact never changes, so a move outside that range means the model or the rubric shifted, not your prompt. Create one from the Drift panel or POST /artifact-bundles/{id}/drift-monitors.
A Check now control and POST /drift-monitors/{id}/check to run a check immediately instead of waiting for the schedule. The first check on a new monitor measures the version's own noise band before it can report anything as drift.
Send real production results back with POST /artifact-bundles/{id}/outcomes (or the rubrkit_record_outcome MCP tool) to unlock two signals the offline rubric cannot give: input drift, which compares recent traffic against your reference window, and validity drift, which measures whether the rubric score still tracks the real outcome. Both stay blank until there is enough data to answer them honestly.
The background job drainer now runs every ten minutes instead of every minute, so a queued job may take a few minutes longer to start but the database is no longer held awake around the clock.