What runs at each build scope

The stages a task moves through, and exactly which of them each build scope turns on.

The pipeline

A task is not one call to a model. It moves through stages, and build scope decides which of them run.

The first three always run — without them there is no answer at all. Everything after is what scope turns on.

What scope really changes

Connected and Entire system run the same stages. The difference is not which stages run — it is how much each one is made to produce. Connected follows the work your request actually triggers; Entire system materialises every stage of the organisation model whether the request touched it or not.

How many artefacts

Only this is capped on purpose: you asked a question, so you get the answer rather than a project around it.

Extra surfaces

Choosing

  • Only this — an answer, quickly. Selection, planning and building; nothing else.
  • Connected — the answer and its consequences. Almost always the right one for real work.
  • Entire system — a genuine reset. Slowest and most expensive; the right choice less often than people expect.