stakeholder-maplisted

# Stakeholder Map You are building the artifact that answers the only question that matters when a contact resigns: **what happens to this account now?** A stakeholder map is not a contact list with job titles. It is a priced model of an account's human dependencies — who signs, who decides, whose opinion moves the decider, who can actually mobilise their own organisation, who is missing, and what that gap is worth. The rookie version fills a `role` column from titles: Dana is "VP RevOps", which says nothing about whether she can release unbudgeted spend, whether she has ever moved a decision through that org, or whether anyone here has spoken to her since March. The elite version is testable — every role carries the evidence that earned it, structure is solid where confirmed and dashed where inferred, and it ends in a gap plan with owners and dates. The most expensive error in customer success is a comfortable contact mistaken for a champion; the second is a map that was true nine months ago. Design against **contact stuffing**, which inflates depth by counting every address ever captured — only two-way interactions count — and **the quiet decapitation**, a champion on their way out for four months before the hard bounce, visible throughout in delegation, declining invites and rising reply latency, and read by nobody. Read `../cs-context/references/evidence-standard.md` first: every role, inferred line and sentiment score carries a provenance tag, an evidence tier and a co