Choose one branch that can trigger spend or a real downstream action
The package starts with a single edge that already matters operationally or financially.
NORNR
Turn one consequential graph edge into a reviewable decision lane.
NORNR / LangGraph approval branch
Productized packageThis package is for teams already modeling state transitions in LangGraph. NORNR decides whether one graph edge may continue, must queue for review, or should stop before the graph reaches a consequential action.
The package is not “govern every node.” It is one approval lane: one edge that can lead to spend, vendor behavior or another consequential action.
Package shape
The graph remains the graph. NORNR only changes what happens when one edge reaches a real consequence.
The package starts with a single edge that already matters operationally or financially.
The point is not to slow the graph. The point is to make the consequential edge reviewable when the active mandate is no longer enough.
The best package outcome is a queue item with reason, threshold and owner already attached.
Approval branch only matters if the resulting path can still be defended outside NORNR later.
Install-first path
The starter, pack and proof outputs should all agree on what the branch is supposed to govern.
nornr init langgraph --owner graph-agent
One consequential edge, one threshold posture and one review owner before the branch reaches irreversible work.
What it proves
That is the buyer-safe story: keep the orchestrator, improve the control posture.
The edge is already close to paid API usage, vendor behavior or another real commitment.
Threshold, counterparty and mandate posture decide whether the branch may continue.
Low-risk paths continue inside the graph without extra operator drag.
The graph waits on one approval owner instead of inventing a side-channel review flow.
Decision, review and execution stay tied to the same governed branch.
The package is complete only when the branch still ends in one defended export path.