The idea in practice

A good correction names the obsolete detail, its replacement and the scope of the change. This helps prevent two incompatible notes from influencing later work.

Try the distinction on a real task

This is an illustrative request, not a customer result or a promise that every connected service supports every step.

Replace my old preference for afternoon calls with mornings for work calls only.

How to apply it

  • Name the old and new details
  • State whether the change is general or task-specific
  • Check a later relevant answer

What to check

Verify the new detail while confirming unrelated preferences still make sense.

A mistake to avoid

Do not bundle several ambiguous corrections into one message and assume every distinction was understood.

Using Bris for this work

Bris is designed to carry useful preferences into later work. Tell it what should stay relevant, correct details when they change, and ask what it remembers before relying on an important constraint. A remembered preference is context; it is not permission to send, book or buy.