Tip2026-04-03#reliability

Design abstention as a first-class output

Abstention fails when it feels like an error. It works when it is a designed branch with a reason, missing evidence, and next action. The user should know what changed from answerable to not answerable.

Use explicit output states: answered, partial, unknown, blocked, protected-required, and needs-review. Each state should carry what evidence exists and what evidence is missing.

This is how you prevent graceful prose from hiding a dead end. The model can stop without leaving the user stuck.

Aha moment

A model fills blanks when the product has no respected way to stop.

Try this

Make unknown, partial, blocked, protected-required, and needs-review states valid outputs with next actions.

Open NotesEntry JSON

Watch for

  • Schemas where every field must be filled even when evidence is absent
  • Refusals that leave the user without a useful next step
  • Unknown states treated as errors instead of designed outcomes