---
title: "A Suggestion Is Not an Assignment"
canonical: https://dxdev.com/blog/2026-04-28_suggestion-is-not-approval/
datePublished: 2026-04-28
---
A recommendation becomes risky when it can be mistaken for work that someone has already approved or accepted.

## Keep the work states separate

The important chain is simple: suggested, reviewed, approved, assigned or actionable. These are different states, even when the words appear close together in a task list.

A recommendation should never become work for someone merely because it was written clearly or generated by a system that appears confident.

## Where AI fits

AI can create the suggested state and help prepare the review state by separating evidence, uncertainty, and the next human decision.

## The human decision

People review, approve, assign, or reject work. AI must not silently jump an item from suggestion into an actionable state.

## The lesson

A suggestion is not an assignment. The handoff between those states needs a visible human decision.

The Build Log companion shows how a constrained suggestion state protected a downstream queue from being flooded with unvetted work.