Instrumental values are just subgoals that appear when you form plans to achieve your terminal values. They aren’t supposed to be reflected in your utility function. That is a type error plain and simple.
For agents with bounded computational resources, I’m not sure that’s the case. I don’t terminally value money at all, but I pretend I do as a computational approximation because it’d be too expensive for me to run an expected utility calculation over all things I could possibly buy whenever I’m consider gaining or losing money in exchange for something else.
That one is. Instrumental values do not go in utility function. You use instrumental values to shortcut complex utility calculations, but utility calculating shortcut != component of utility function.
Yes, and I’m arguing that it has instrumental value anyway. A well-thought-out utility function should reflect that sort of thing.
Instrumental values are just subgoals that appear when you form plans to achieve your terminal values. They aren’t supposed to be reflected in your utility function. That is a type error plain and simple.
For agents with bounded computational resources, I’m not sure that’s the case. I don’t terminally value money at all, but I pretend I do as a computational approximation because it’d be too expensive for me to run an expected utility calculation over all things I could possibly buy whenever I’m consider gaining or losing money in exchange for something else.
I thought that was what I just said...
An approximation is not necessarily a type error.
No, but mistaking your approximation for the thing you are approximating is.
That one is. Instrumental values do not go in utility function. You use instrumental values to shortcut complex utility calculations, but utility calculating shortcut != component of utility function.