Role Transfer

1 min read

Definition #

The complete handoff of a role — its domain, its authority, and its identity — from operator to hire. The operator vacates the role; the hire occupies it. Distinct from delegation, which is task-level and leaves the operator owning the role.

Family #

Canon — LOCKED. Parent concept for the Rung 2 IP set: failure modes ([Control Snapback], [The Four Override Patterns], [Role Drift]) and completing artifacts ([The Scope Handoff Document], [The Ten-Minute Close], [The Labor Re-Classification]).

Why Behind the Thinking #

Three layers have to move together for a transfer to be real — Domain (the scope the role covers), Authority (the [Authority To Execute] within that domain without returning to the operator for permission), and Identity (the operator’s internal release of the role and the hire’s internal claim of it). The signature failure is transferring the title and salary but not the domain: the operator still walks in on the hire’s prep, adjusts decisions in real time, and overrules calls in front of cast — because the internal decision to vacate the role was never made. At Rung 1 the operator owns every role by default; Rung 2 is the first time they are asked to release one, and without a deliberate Role Transfer the hire becomes supervised task execution wearing a manager’s title — the operator’s hours go up, not down ([master_ip_compiled.txt]).

Pairs With #

[Accountability Demand], [The Real Accountability Model], [Authority To Execute], [Each Rung Is Its Own Verb], [The Rungs], [Control Snapback], [The Four Override Patterns], [Role Drift]