AntiDrift treats a work session as a commitment: next action, success condition, timebox, evidence, transition prompts, and review. Stage 1 is user-space friction, not privileged enforcement.

The local event log is written to ~/.antidrift_events.jsonl. It records commitment creation, policy snapshots, runtime transitions, evidence health, transition starts, and violation dismissals. The log is append-only and hash-chained for tamper evidence, but it is not yet protected by a privileged guardian.

Linux active-window evidence depends on xdotool and is strongest on X11. Wayland is degraded unless a compositor-specific adapter is added later.

To use AntiDrift, run cargo run --release directly, or cargo build --release and copy the binary into your PATH.

Under Windows, AntiDrift uses the package winapi for window titles and window minimization.