saberbud/PocketFlow-Tutorial-Codebase-Knowledge
1
0
Fork 0
mirror of https://github.com/The-Pocket/PocketFlow-Tutorial-Codebase-Knowledge.git synced 2026-08-29 08:34:31 +08:00
Code Issues Packages Projects Releases Wiki Activity

update the header

Browse Source
This commit is contained in:
zachary62
2025-05-10 10:51:29 -04:00
parent 138c103240
commit 894fe3334b
10 changed files with 61 additions and 23 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/PocketFlow/04_flow___flow____asyncflow___.md
+7
View File
@@ -1,3 +1,10 @@
---
layout: default
title: "Flow (Flow, AsyncFlow)"
parent: "PocketFlow"
nav_order: 4
---
# Chapter 4: Flow (`Flow`, `AsyncFlow`)
In [Chapter 3: Actions / Transitions](03_actions___transitions__.md), we saw how individual [Nodes (`BaseNode`, `Node`, `AsyncNode`)](02_node___basenode____node____asyncnode__.md) can decide what should happen next by returning "action" strings, and how these actions lead to "transitions" between Nodes. But what actually manages this sequence? What's the conductor of this orchestra of Nodes? That's where **Flows** come in!