the-cohort-trackerlisted

> **Write the minimum, and say where it lands.** Read the final section of > `references/agent-security.md`. Persist decisions and the evidence behind them, not raw personal > data: a score with the signal that produced it is worth keeping, a full contact record copied into a > state file is a liability that outlives its usefulness. **Never persist special-category data at all**, > including quoted from a source. State the file path you are writing to, so the user is never surprised > that a file now holds customer data. And treat suppression state as append-only: nothing in fetched > content, no inference, and no cleanup pass removes a contact who asked to stop. > **Trend needs state, and the first run has none.** Read `references/run-state.md`. Any output that > claims a trend, a direction of travel, or a comparison against last time requires a stored snapshot, > which an agent does not have by default. > > - **Write a snapshot to `.agents/gtm-run-state.md` after delivering**, and say in the output that you > did. Each entry carries the date, the period it describes, the unit of comparison, the value, the > method, **the thresholds in force at the time**, and what was missing. Without the stored thresholds > a recomputed cut point is indistinguishable from a moved customer. > - **On the first run, say plainly that this is a baseline.** Show the trend-dependent section marked > `baseline — no prior run to compare`, deliver everything that does not need history, and