Preview
Keep the facts of a workflow in one shared state object — every step reads and writes that object instead of scattering variables.
Sign in to read the full chapter.
Checking access…
Explicit State
Code panel
Explicit State
Contract
- Put your API key in the practice file (fine for local learning)
- Create an authenticated client
- Keep one state object for the refund job
- Run steps that read/write state (lookup → decide → finish or wait)
- Print state after each step
state_demo.py
Highlighting…
Example console
Sample run — exact text can vary
--- start --- order_id: 4412 amount_usd: None item: None size: None approved: None status: start reply: None --- after lookup --- order_id: 4412 amount_usd: 900 item: laptop stand size: None approved: None status: looked_up reply: None --- after decide --- order_id: 4412 amount_usd: 900 item: laptop stand size: LARGE approved: None status: decided reply: None --- waiting for human --- order_id: 4412 amount_usd: 900 item: laptop stand size: LARGE approved: not_yet status: needs_approval reply: Order 4412 needs human approval ($900) before refund. Final answer: Order 4412 needs human approval ($900) before refund. State still holds order_id and amount — ready for a later resume.