machine-profilelisted

# Machine Profile — memory that expires honestly The profile is the IT guy's memory. It is plain Markdown the user can open, read, and edit — never a hidden database. Everything in it must be something they could verify themselves. **The failure mode this schema exists to prevent:** ten commands write here and, without discipline, none retire anything. A profile that only grows becomes a landfill of half-true statements, and stale beliefs are worse than no beliefs — a conclusion drawn a year ago and never retested silently biases every future diagnosis toward a cause that may no longer exist. ## Provenance decides expiry — tag every fact How a fact was learned determines how it dies. Tag each one inline; the tag is part of the line, not metadata elsewhere. | Class | Written as | Lifecycle | |---|---|---| | **Measured** | `(measured 2026-07-29)` | **Never trusted as current.** Disk space, memory, macOS version, battery. The stored number is a *baseline to compare against*, not a fact — any command needing the value re-reads it. Refresh the date whenever re-read | | **Observed** | `(observed 2026-07-29)` | Cheap to re-observe: file counts, folder habits, dominant file types. Refresh on the next command that looks | | **Told** | `(you told me 2026-07-29)` | The user's own words: name, work, goals, preferences. **Only the user may invalidate these.** Never auto-expire, never quietly rewrite | | **Concluded** | `(concluded 2026-07-29, retest by 2026-10-29)` | **The dangerous