Interface selection and the permission gate

How the surface for each piece of work is chosen, and how to be asked before it commits.

Part-way through a run, the system decides what to build: which surfaces the answer needs, and how many.

Why you would want to see it

Left alone it decides and proceeds, which is usually what you want. But it is also the moment where a task can widen more than you intended, and the one point where a small correction saves the whole run.

Asking to be asked

Turn on Ask for permission at interface selection in directory settings. The run then pauses at that point and shows you what it intends to build before it builds it.

You can let it proceed, or stop it.

Note

The gate offers a "Continue, don't ask again" action. Taking it turns the setting off for the directory — that is the same switch, not a one-off.

Why it chose what it chose

The choice is driven by the shape of the answer, not by your phrasing. A comparison becomes a table or cards; a sequence becomes a timeline or board; a model becomes a sheet.

If it picked badly, you can move a result to another surface afterwards — see Reviewing an interface.

Next