Three Interpretations

A client gives an AI agent one brief. Three agents build it. Nobody mishears anybody.

You say — the whole brief

“Make a tool that helps people split bills.”

Eight words. You know exactly which product you mean. Read on.

Even Split Valid

How it read your eight words: “split” = divide equally · “bills” = tonight’s one bill · “people” = whoever’s at the table.

House Ledger Valid

How it read your eight words: “split” = share ongoing costs · “bills” = rent, wifi, power · “people” = named housemates with a history.

Item-by-Item Valid

How it read your eight words: “split” = pay for what you had · “bills” = an itemised receipt · “people” = whoever ordered what.

Now say what you meant — add the words you thought were obvious

Each line is plain language. Watch what your words do to the agent’s freedom to guess.

The lesson: a vague brief doesn’t produce a wrong product — it produces a space of right ones, and the agent picks from it without telling you it picked. Writing down what you meant, precisely enough that a stranger builds the right thing, is programming’s newest notation. It’s called a spec, and you just wrote one with six clicks.