RiskMandate — the business case for LangGraph and LangChain human-in-the-loop
LangGraph and LangChain human-in-the-loop (LangChain (company-maintained)), by the risk it changes: the register for a stated agent deployment without it and with it, computed from a public model, from the operator to the board.
Source: https://riskmandate.ai/business-case-langgraph-hitl.html↗
LangGraph and LangChain human-in-the-loop, by the risk it changes
Middleware that checks each tool call against a policy and, when intervention is needed, interrupts execution until a person responds. Written as an answer, the agent changes things with a person approving each change, for the tools configured.
Open source: MIT · LangChain (company-maintained) · get involved ↗
The deployment: The model's typical deployment, with the answers this project addresses stated as they are without it: it changes things on its own.
The model: the RiskGraph Explorer's 49 facts, 49 risks and 10 roles, copied into this site with its provenance; the register below is computed, not written. How↗.
In its own words, and nothing more.
- An interrupt that halts execution until a person responds. “If intervention is needed, the middleware issues an interrupt that halts execution.” · docs.langchain.com ↗, read 24 September 2026
Same deployment, different answers.
The model asks sixteen questions about an agent deployment. A product’s effect is written as the answers it changes, and each change says what kind of change it is: a statement of what is true, an expectation the agent is asked to meet, a setting, or a boundary enforced by something the agent’s grant does not include.
1 retired, 22 unchanged.
Computed from the model for the deployment above: every risk that holds without it, and every risk that holds with it.
Retired
Who carries less, and who carries the same.
Each risk is assigned to the roles it belongs to, and each role reports to another until the board. The count beside each role is the entries it holds without the product and with it.
Operators
Owners
Executives
The board
At the board: the corporate register
Corporate risks have no facts of their own. They hold while any risk that leads into them holds, so a single product rarely retires one. What it changes is how many reasons the board is being given.
Every product is also a new thing in the estate.
Its interrupts page says the runtime restarts the entire node from the beginning when it resumes, so any code that ran before the interrupt runs again, which matters if that code changed something.
What adopting it takes, before any of this is true.
An open-source project costs nothing to download and something to adopt. Every change above depends on the work below, and most of it is customisation to your own deployment.
- Choose the tools that must wait, and show the person what the call will do.
- Make the code before an interrupt safe to run twice.
The limits of the case, stated by the case.
- That it was tested. Nothing was installed or run; every change rests on the documentation quoted beside it.
- That the register is complete. It is one model, for one stated deployment. A different deployment changes the answers, and so the case.
Next. Published, and sent to the project's maintainers at the same time. If a change is wrong, or another answer should move, the case changes with the date they said so.
Make the case in the register’s own terms.
If you build a security product for agents, the case for it can be written the same way: what it does in your own words, the answers it changes, and the register before and after. If a case here is wrong about you, tell us and it changes with a date.