Listen

Description

If knowledge I gave a company five, ten, or twenty years ago is still generating value for them, why does the payroll relationship get to end while the value extraction doesn't?

That's the question driving this episode. I read and respond to an excerpt from a LinkedIn post by a former colleague about AI systems that capture and index employee knowledge — the recordings, conversations, and stories that make expertise valuable — so all of it stays discoverable inside a company long after the person who generated it has left. Long-term extraction, in other words.

My issue isn't with the AI capability itself. It's with the assumption sitting underneath the post: that a company can capture, index, and reuse a person's stories, judgment, and point of view indefinitely, without renegotiating consent, ownership, or compensation as the relationship changes.

I trace it through consent, accountability, discoverability infrastructure, reputation risk, and the crux of it for me: compensation.

Key themes

Reflection questions

Use these for journaling, discussion, or a follow-up episode:

  1. What consent does a company actually have to use my recorded conversations, stories, and expertise after I've left?
  2. If information I provided years ago is repurposed and the context has shifted, who is accountable when it backfires: me or the company?
  3. If a company builds infrastructure to make my captured knowledge discoverable, indexed, and pattern-matched, do I have any say in how I'm cited or attributed?
  4. If a former employer is one I no longer want to be associated with, what recourse do I have over how my past contributions continue to represent me?
  5. If my knowledge is valuable enough to keep generating value years after I've left, why doesn't the compensation relationship continue too?
  6. Has the employment contract changed, from "paid for your labor while employed" to "paid for your labor, but your knowledge stays extractable indefinitely"?
  7. Does this exposure extend beyond employees to contractors, freelancers, and consultants? Is it addressed anywhere in those agreements?
  8. Whose knowledge gets deemed valuable enough to capture in the first place? Is there bias (age, race, gender) in that determination?
  9. What would it take to make this explicit: legislation, individual negotiation, or structural change at the organizational level?
  10. As AI capture of video, writing, and audio becomes normalized, what belongs in a contract today that wasn't there before?

One-line takeaway

The post calls it preserving wisdom. I'm asking who owns that wisdom once the relationship ends, and why consent and compensation don't get renegotiated along the way.

This is an Assumption-Ground Audit

This whole episode is the Assumption-Ground Audit in action, pointed at a LinkedIn post instead of a policy. The AGA is the method I use to surface the assumption sitting underneath a decision before it calcifies into precedent. The question is never whether the technology is good or bad. The question is what everyone is treating as already-settled that hasn't actually been agreed to.

Here, the unexamined assumption is the Hotel California Clause itself: that indefinite capture and reuse of an employee's knowledge is simply part of the deal, and that consent, attribution, and compensation don't need renegotiating just because the mechanism changed from "someone remembers what you said" to "a system indexes it forever." That's the kind of assumption the AGA is built to catch before you build infrastructure, policy, or a vendor relationship on top of it.

If you're building AI systems that touch employee knowledge, client data, or institutional memory, those assumptions are hardening into your roadmap right now, whether anyone has examined them or not. If you want to know what they are before they're impossible to walk back, let's have a conversation.

Work with me on an Assumption-Ground Audit →