Document M0 walking skeleton

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

README.md

@@ -1,24 +1,29 @@
 # AntiDrift
 
-Just my personal productivity tool.
+A personal focus operating system: treat each work session as an explicit
+commitment (next action, success condition, timebox), and make drift visible.
 
-## Commitment OS Stage 1
+This is the Go reimagining. The original Rust implementation is preserved under
+`legacy/` for reference. See `docs/superpowers/specs/` for the design.
 
-AntiDrift treats a work session as a commitment: next action, success
+## Run
-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
+```bash
-commitment creation, policy snapshots, runtime transitions, evidence health,
+go run ./cmd/antidriftd
-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.
+The daemon serves a local web UI at http://localhost:7777 and opens your
-Wayland is degraded unless a compositor-specific adapter is added later.
+browser. State is persisted to `~/.antidrift/state.json`.
 
-To use AntiDrift, run `cargo run --release` directly, or `cargo build --release`
+## Test
-and copy the binary into your `PATH`.
 
-Under Windows, AntiDrift uses the package `winapi` for window titles and window
+```bash
-minimization.
+go test ./...
+```
+
+## Status
+
+M0 (walking skeleton): manual commitment lifecycle over a local web UI with
+snapshot persistence. AI integration, active-window tracking, and the
+tamper-evident audit log arrive in later milestones (see the roadmap in
+`docs/superpowers/specs/2026-05-31-go-focus-os-design.md`).