the-account-blueprintlisted

> **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 it.** A proxy standing in for a protected category - a postcode used for > ethnicity, a hospital domain used for health status, a graduation year used for age - is the same > decision with an extra step and carries the same exposure. > **Ask whether this is a new logo or an expansion.** The plan differs substantially: an expansion > inherits relationships, a support history, and a reference-able internal result, and its committee map > starts from who already knows you rather than from zero. Applying a new-logo committee benchmark to an > expansion overstates how much threading is missing and sends the rep to build relationships that > already exist. ## Context