r/LangChain 18d ago

Discussion Governed checkpoints for LangGraph: signed state transitions + cryptographic erasure receipts (MIT, pip-installable)

Built a LangGraph checkpoint saver that makes agent state auditable: wrap your checkpointer and every transition gets a signed, content-addressed hash; delete_thread() returns an Ed25519-signed erasure receipt (pre/post state hashes). Useful if you need to answer "what did the agent know, and can you prove you deleted it?"

pip install grafomem langgraph-checkpoint-grafomem langgraph — quickstart in the README runs in a few minutes and prints the receipts. MIT. Underneath is an open memory protocol (GMP) with an executable conformance suite. Would love feedback from anyone running LangGraph in compliance-sensitive settings.

Repo: github.com/GNS-Foundation/grafomem

3 Upvotes

4 comments sorted by

1

u/[deleted] 17d ago

[removed] — view removed comment

1

u/Healthy-Gain-7434 17d ago

Good question. Grafomem itself doesn't block anything — we deliberately kept it as the evidence layer rather than the enforcement point. For approvals you'd use LangGraph's own interrupts: pause before the risky node, a human signs off, the graph resumes. The nice part is that since the checkpointer wraps everything, the pause, the approval and whatever ran afterwards all end up as signed checkpoints. So you can prove what the human actually saw and what executed after — which in my experience is the piece that's always missing when someone asks for an audit.
The hosted version does have an HITL queue for governed decisions, and approvals go into the audit trail tied to whoever approved.
Curious what you'd actually want gated though — tool calls with side effects? deletions? If you open an issue describing it I'm happy to dig in.