Skip to main content

Drift UX

This spec explains the user experience changes that need to be made to incorporate drift intelligence.

Drift signals appear in two UX layers: the Authority Path, where evidence is shown, and the Cluster, where drift is summarized as a governance instability driver.

Authority Path Level Drift

  • Drift is path specific
  • Drift is surfaced as a governance condition, not as a historical event log.
  • The evidence is tied to this authority chain
  • The change must be explainable with execution evidence

Changes to make to the Authority Path UX:

  1. Rename “Active risk conditions” to “Active Governance Conditions”
  2. Improve the Scope Drift Card: change the current card to
  3. Status: “Since 30d”
  4. Condition: “This authority path gained an additional role. The automation now executes with broader privileges than previously observed on this authority path.”
  5. Evidence:
    1. Privilege added: sql_admin_reader
    2. Previously observed roles: sql_clinical_reader
    3. Detected: 1d ago
  6. Remove the “intervals” part.

Cluster Level Drift

This specifically links to Section C — Governance Condition (why this is unstable)

Cluster level will never show drift explanations or evidence. It only displays the presence of drift as a governance driver (e.g., “Scope drift present across 3 authority paths”).