A choice for this task

A setting changed for one task shouldn't become a rule for every task.

Suppose someone chooses a gentler setting for a delicate object. That choice tells us what they need now. It does not tell us how they want the next ordinary object handled.

For a utility that adapts, we would distinguish a temporary adjustment from a preference that holds across similar tasks. The current physical control should always take precedence over an inferred preference.

A useful development check would alternate routine tasks with exceptions. Compare a version that adapts with one that keeps fixed settings. Count both the adjustments it saves and the new corrections it causes.

Then change the person's routine. Check whether the device can stop relying on an old pattern without making the owner reset the whole product.

An agent under the hood should reduce the need to repeat yourself while remaining easy to correct. All of that should happen locally, through the object itself.

Our first utility is in development. These are proposed checks, and the delicate-object example is illustrative.