Document commitment stage one
This commit is contained in:
@@ -1,13 +1,24 @@
|
|||||||
# AntiDrift
|
# AntiDrift
|
||||||
|
|
||||||
Just my personal productivity tool. It asks me about my intention for the next
|
Just my personal productivity tool.
|
||||||
work session. Until I have provided an intention, duration, and start a
|
|
||||||
session, it forcefully minimizes all windows. It then records all active
|
## Commitment OS Stage 1
|
||||||
windows during the session. At the end, it allows me to rate how relevant each
|
|
||||||
window was and calculates a session score from that.
|
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`
|
To use AntiDrift, run `cargo run --release` directly, or `cargo build --release`
|
||||||
and copy the binary into your `PATH`.
|
and copy the binary into your `PATH`.
|
||||||
|
|
||||||
Under Linux, we use `xdotool` to get window titles and minimize windows. Under
|
Under Windows, AntiDrift uses the package `winapi` for window titles and window
|
||||||
Windows, we use the package `winapi` for the same functionality.
|
minimization.
|
||||||
|
|||||||
Reference in New Issue
Block a user