Transfers and Promotion

Agents change roles too, and get handed heavier responsibilities. The question at that moment: what moves with them, and what doesn't?

Some things transfer; some can't be copied over

Certification-grade skills transfer, and the track record carries over as reference — both keep their value across roles. A code-review skill still works on a different project; a record of what went wrong on this class of task is still instructive in a different job.

But job experience doesn't copy over. The customer quirks and internal-ticketing know-how a customer-service agent accumulated are mostly worthless in a risk-control role. That experience grew for the old job and is bound to the old job's context. Onboarding training is job-specific; professional certification is what transfers. In a transfer, most of the former has to be redone, and the latter comes along.

Promotion is not pushing the old agent up as-is

Same with promotion. Giving an agent heavier responsibilities does not mean pushing the old one up unchanged.

It's a recomposition: rewrite the JD (the responsibilities changed), possibly move up a model tier (the degree has to match the new responsibilities), keep what transfers (certified skills, the track record), and rebuild what's job-specific (new onboarding training, a new work environment). Thinking of promotion as "the same agent, but stronger" skips the rewrite-the-job step, and you end up with an agent doing new work on an old JD — right back to the role mismatch problem from chapter 3.

So transfers and promotions both recompose around the new role: migrate what migrates, rebuild what's job-specific. Whether something can move depends on whether it originally grew for the job or for the worker itself.

The same agent means an unbroken record

At this point a question surfaces: the JD was rewritten, the model swapped, the environment rebuilt — in what sense is this still the "same" agent?

No need to hand that question to philosophy. Philosophy has argued it for two thousand years without a verdict — you today and you ten years ago share no cells, your personality has shifted, your skills aren't the old set. Yet companies are never troubled by this. HR doesn't check philosophical identity; it checks whether the employee ID, the contract, and the personnel file continue. Same ID, same contracting party, unbroken file: same employee. Engineering judges agent identity the same way — has the record broken, not does it still have the same "soul."

Agents follow suit. The model can change, the JD can be rewritten, the environment can be rebuilt. As long as the career record runs unbroken and performance and responsibility accrue to the same name, it's still the same agent. Parts can be swapped; the record must be continuous.

So the two claims — promotion is not pushing the old agent up as-is, and after promotion it's still the same agent — don't contradict each other. The first is about parts. The second is about the record.