the-lifecycle-mapperlisted

> **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. > **Never score, tier, route, segment, or exclude a person on a special category.** Read the relevant > section of `references/agent-security.md`. > > Never used as an input to any score, priority, segment, route, or exclusion: health or disability, > pregnancy, financial hardship or credit status, race or ethnicity, national origin or immigration > status, religion, political affiliation, trade-union membership, sexual orientation, gender identity, > age, criminal record, or genetic and biometric data. > > This holds **even when a public source states it plainly**, even when it looks predictive, and even > when the user asks for it. Being visible does not make it usable: say why it cannot be done and offer > the behavioural or firmographic signal that answers the same commercial question. > > **And do not launder