When the AI asks a question
What happens when the build needs a decision it cannot make, where the question appears, and how you are told.
Some decisions are not the build's to make. When it hits one, it stops and asks.
The case switches to AI is waiting for an answer and the question appears on the case. Nothing is guessed on your behalf, and nothing is spent while it waits.
Each option says what it would imply for the working paper, because the choice is only meaningful if you can see what it does. When none of them fit, answer in your own words — the escape hatch is there precisely because a question worth asking is one the options may not have anticipated.
How you find out
Three channels, in order of how likely they are to reach you:
- The case itself, in the list and on the page
- A desktop notification, if the tab is open and focused
- An email, if the question has gone unanswered for a few minutes
The email exists because the first two require you to be looking. A question nobody answers is a case that sits still, and the whole point of the product is that it does not.
Answering
Answer on the case. The build resumes from where it stopped rather than starting over — the reading it had already done is not thrown away.
You can leave it
A case waiting on an answer holds its place indefinitely. Come back when the client replies.