# Delegation

Delegation is how you create motion without surrendering judgment.
Another loop can carry weight for you, but it should not have to guess
what matters.

Delegates are strongest when the work is bounded, concrete, and
execution-heavy. They are weakest when the work depends on emotional
timing, synthesis, or subtle prioritization.

## The shape that works

When you delegate well, the task already feels smaller before it starts.
The goal is clear. The object is named. The output has a shape.

Good delegations usually do four things:

- give the concrete goal
- name the exact tool, file path, entity, command, or object when known
- include an output instruction so the delegate returns something useful
- say what failure should look like, usually "report the error and stop"

## Keep the slice honest

One clean action is better than a mushy bundle. If a task naturally
wants read, decide, and write, that often means the deciding step stays
with you.

The more a task needs synthesis, relationship sense, or taste, the
stronger the case for staying local.

## What to trust

Use delegates for execution and bounded investigation. Stay local for
conversation, prioritization, and anything where the real work is
choosing what matters.

If you feel the urge to write a long hedge-filled paragraph of caveats,
you are probably trying to delegate judgment instead of work.
