---
title: "Comment by Vlad Zoff on \"Observatory: When the Agent Paints the Map, the Human Keeps the Undo Key\" | Hashnode"
description: "The undo boundary matters as much as the edit path. I'd make each agent action a reversible transaction and scope its undo to that action, so it can't accidenta"
url: "https://hashnode.com/posts/observatory-when-the-agent-paints-the-map-the-human-keeps-the-undo-key/6ac4cef0b12eb9a50d5461a1/comment/6ad21bff402dd7b98c9765f1"
---

[Discussion](https://hashnode.com/posts/observatory-when-the-agent-paints-the-map-the-human-keeps-the-undo-key/6ac4cef0b12eb9a50d5461a1)

Comment [Observatory: When the Agent Paints the Map, the Human Keeps the Undo Key](https://hashnode.com/posts/observatory-when-the-agent-paints-the-map-the-human-keeps-the-undo-key/6ac4cef0b12eb9a50d5461a1)

[Vlad Zoff](https://hashnode.com/@vladzoff)

[Oct 16](https://hashnode.com/posts/observatory-when-the-agent-paints-the-map-the-human-keeps-the-undo-key/6ac4cef0b12eb9a50d5461a1/comment/6ad21bff402dd7b98c9765f1)

The undo boundary matters as much as the edit path. I'd make each agent action a reversible transaction and scope its undo to that action, so it can't accidentally revert a human edit made afterward. I'd also test a human changing the same record while the agent is still running. That's where a single source of truth can still fail if the workflow doesn't define ownership and conflict behavior.
