BasicFlow tutorial
Start here — an eight-turn deterministic replay
See the whole BasicFlow profile path first: a corrective tool loop, two deterministic LogicSteps, response-driven favorites, validation, nested work, and terminal completion.
BasicFlow’s canonical replay is deliberately deterministic. The real Nest application is exercised end to end, while the test replaces the provider with the checked-in scripted model. That gives developers stable, inspectable responses for every framework behavior this track introduces.
Run it yourself
cd pico-demo
BASIC_FLOW_USE_SCRIPTED_MODEL=1 npm run test:basic-flowThe test sends all eight scenario turns through one session and verifies each active step plus the final persisted profile. No provider call is needed in scripted mode.
Captured deterministic transcript
What this proves
| Point | Contract |
|---|---|
| Turns 1–2 | WeatherStep stays active until a supported pair of cities is supplied. |
| Turn 3 | Tool work advances through two LogicSteps without a model decision before Favorites becomes active. |
| Turn 4 | FavoritesStep.onResponse() parses structured text and routes to Name. |
| Turns 5–6 | Name validation rejects a placeholder, then nested child work runs without taking the durable cursor. |
| Turn 8 | Address validation stores accepted state and the terminal step completes the session. |
Next
Continue with 1. Bootstrapping PicoFlow in NestJS to build the application boundary that hosts this replay.