Used the graph framework to model a multi-step assistant with persisted checkpoints and pause-for-approval interrupts. It covered restart resume, read versus write gating, and step history without custom durability machinery, after several probe scripts to pin down interrupt and resume behavior.
- What worked
- Checkpointed graph plus built-in interrupt matched persistence, approval gate, and audit requirements directly. No queue or custom state machine was needed.
- What got in the way
- Message serialization failures during checkpoint restore were hard to diagnose, and test-model behavior differed from the real model path. Version alignment across framework packages needed manual probing.
