TLDR: When a client departs, "remove them from everything" is the wrong instruction to give your AI agent. The right move is surgical. I learned this when my client's operations contact called back the day after I'd scrubbed their company from Apollo (my AI agent with persistent memory).

The Setup

A crypto-education business was a retainer for my consulting practice. Engagement ended May 2026.

So I told Apollo to clean house.

Makes sense, right? Client's gone, get them out of the system. Except "remove them from everything" is genuinely ambiguous when your AI agent has memory wired into a dozen surfaces.

The Wrong Instinct (and Why It's Tempting)

The obvious move is to delete everything. Wipe the memory files, zero out the prompts, purge the scanner config.

That's over-scrubbing. And it's almost as bad as not scrubbing at all.

Under-scrub means Apollo's hourly scanner (the inbox/calendar sweep agent) is still treating the client as an active business, still polling for their emails, still surfacing their context in every precall brief. Embarrassing at best, creepy at worst.

Over-scrub means you've nuked historical context you'll actually want — past decisions, relationship notes, the quirks that made the engagement what it was. Gone.

The Touch/Leave Rule

What I actually built — and what I'll use for every future departure — is a Touch/Leave rule:

  • Touch: present-tense active claims, active-business enums, live polling lists
  • Leave: past-tense framing, historical examples, dated artifacts, illustrative context

Then there's the scrub order. It matters more than you'd think.

The sequence: memory → skills → arcade-business MCP (the multi-tenant business-routing tool) → scanner. That ordering means the scanner config lands before the MCP server reloads on the next Claude Code restart. No broken window where the scanner calls business=<client-code> against a server that now rejects it.

Sequencing is boring until it bites you.

The Twist

On May 27 I shipped the commits: chore(memory): archive client memories and scrub active inline refs and chore(scanner): remove client business code from active flow + prompts.

On May 28 — the NEXT DAY — my client's operations contact asked me for a cyber resilience overview to support their cyber-insurance application.

Which became a live re-engagement lead with a cybersecurity business, one of my other businesses.

If I'd over-scrubbed, Apollo would have had nothing to work with. Instead, the historical client context was right there — just not in the active polling loop.

Why This Matters to Me

Departed doesn't mean deleted.

Client relationships don't close — they pause. The scrub is about active polling hygiene, not relationship closure. Your AI agent's memory is not a CRM purge tool.

Scrub what's live. Leave what's true.