Externalize

Move state or structure into a durable artifact while you still do the acting and deciding.

Running a product launch, you carry the whole state in your head: which approvals are in, which vendor is slipping, what you decided about pricing and why. You have not given up any control, but every conversation starts with you reconstructing the situation from memory, and twice this week you have contradicted your own earlier decision because the earlier reasoning was gone.

EXTERNALIZE is the relationship mode where you move state or structure into a durable artifact while you still do all the acting and deciding. Nothing is delegated and nothing runs automatically; the artifact is a reliable memory, not an actor. The cue is exactly this: you remain the right owner of the work, but holding its state internally is producing drift, contradictions, and reconstruction overhead. The operation: choose one artifact as the canonical home (a single launch document with current status, open decisions, and the rationale behind closed ones), write state into it at the moment it changes, and consult it before deciding rather than trusting recall. What changes is consistency: your decisions stop contradicting each other because the reasoning is on the page, and your head is freed for the thinking only you can do. The boundary: an externalized artifact that stops being updated becomes a confident lie, and externalizing is the wrong mode when the task needs an actor, not a record; a to-do list does not do the to-dos.