Milestone 4.D.4 — Drift Alerts & Directive Management

Status: Planned
Goal: Track D — Operator Dashboard
Phase: 4 — Operator Platform & Multi-Provider
Estimated effort: 4 days
Track: Track D — Operator Dashboard

Why This Milestone Exists

The UX spec fully specifies the drift alerts screen (severity, impacted agent/timeframe, z-scores, suggested actions) and directive management (version timeline, diff viewer, regression scenarios, promotion workflow). These were never built in the original phase plan despite the backing schema already existing. This milestone closes that gap.

Drift Alerts

Grouped list by agent then time window (anti-fatigue rule)
Each row: severity badge, agent, top-3 drifted features, ack/resolve actions
Detail view: full feature drift table, small-multiples line chart per feature
Actions: acknowledge / resolve with notes / reset baseline (admin-gated) / pause agent (high severity + MFA gate)

Directive Management

Version timeline (git-log style) with statuses: draft/review/active/deprecated/revoked
DiffViewer.tsx — unified + split mode, token delta shown
RegressionScenarioList.tsx — critical scenarios highlighted, last-run pass/fail
PromotionWorkflow.tsx — state machine: submit review → run regression → approve → promote
EmergencyRevoke.tsx — confirmation + MFA gate

Orientation (indicative)

Named paths, package layouts, libraries, schemas, env vars, and commands anywhere on this page are rough sketches for orientation — inspiration and a baseline, not a required change list.

During implementation, expect to:

open the live tree and follow existing patterns before inventing new ones
research current constraints (latency, tenancy, deploy shape, libraries) more deeply than this page can
advance the design beyond the sketch where measurement or code reality says so
land work in different filenames, merged packages, deferred docs, or new surfaces when the situation calls for it

Prefer outcomes over matching any particular file tree or command sequence.

Areas that may be involved (situational — not a checklist):

Operator dashboard
Management API

Success signals

Outcome-oriented signals that the milestone is in good shape. Exact filenames, package layouts, and commands may differ from any sketches above.

Drift alert grouping verified with >10 alerts across 3 agents — no per-alert-row fatigue
Small-multiples chart renders correctly for ≥5 simultaneously drifted features
Directive diff viewer highlights token delta for a real version pair
Promotion workflow rejects invalid transitions (cannot promote without passing regression)
Emergency revoke requires MFA re-entry, not just a confirm dialog

Prerequisites

Milestone 4.D.1 (Dashboard foundation)
Behavioral fingerprinting schema (Phase 4.5 Track A)
Directive versioning API (Track A)