Fast path and step-boundary fan-out

The idea

At each step boundary, one call asks every relevant purpose. Low-risk reversible next steps can run without a model turn, and read-only steps run while the model thinks.

The problem
Obvious steps and separate decision calls cost full model turns and latency.
Why it matters
Turns are saved under the same gateway and guards, and the model can undo an auto-step.
Where it stands
In production as of

A step-by-step replay of this idea is not published yet. The library adds one when a recorded run shows it.

  • System One decision cascade

    Bounded choices (route, next action, failure class, done, risk, intent) are typed questions. A rule answers first, then a typed arm, then a small LLM, each with a confidence.

  • Run modes as presets over knobs

    Named presets set routing, review, verification, the fast path, prefetching and the other harness settings per run, item, person, project, team or organization. A preset never weakens a hard gate.

  • Action fusion: edit plus check

    An edit can carry its planned check. The runtime runs the check as its own gated call in the same model turn.

Turn the numbers into shipped work.

Crewshal runs these choices for you: a persistent AI worker with memory and rules, on your Claude and Codex subscriptions.