---
title: "Comment by Steven Mock on \"Stateful AI Workflows: Routing, Checkpoints, and Human Review\" | Hashnode"
description: "The checkpoint idea is the part I would steal first. I am building Homeowner HQ for realtors and lenders, launching December 4 on Amazon AWS, and the hardest mo"
url: "https://hashnode.com/posts/stateful-workflows-and-review/6afeffa9c927dfeaaf726e95/comment/6aff39242ba2db8fedf287b0"
---

[Discussion](https://hashnode.com/posts/stateful-workflows-and-review/6afeffa9c927dfeaaf726e95)

Comment [Stateful AI Workflows: Routing, Checkpoints, and Human Review](https://hashnode.com/posts/stateful-workflows-and-review/6afeffa9c927dfeaaf726e95)

[Steven Mock](https://hashnode.com/@stevenmock)

[2h ago](https://hashnode.com/posts/stateful-workflows-and-review/6afeffa9c927dfeaaf726e95/comment/6aff39242ba2db8fedf287b0)

The checkpoint idea is the part I would steal first. I am building Homeowner HQ for realtors and lenders, launching December 4 on Amazon AWS, and the hardest moments are exactly the ones you describe: a long-running step that should be resumable, and a message between a homeowner, their realtor and their lender that should be reviewable before it goes out. A revision-bound approval check — one approval, one revision, no silent retries — is how a small team keeps that honest. The routing taxonomy helps too: most of my "bugs" have been a step routed to the wrong next action, not a bad model answer. Great guide.

[Santosh](https://hashnode.com/@sant-sh)

[2h ago](https://hashnode.com/posts/stateful-workflows-and-review/6afeffa9c927dfeaaf726e95/comment/6aff39242ba2db8fedf287b0#reply-6aff3a742ba2db8fedf28ec5)

Glad you found it useful! I would really interesting to hear how these patterns apply to what you're building with Homeowner HQ.

Wishing you the best for the launch.
