> No, there is no undo "tree"[...]
This is still a tree, it's just implemented in an array.
This is still a tree, it's just implemented in an array.
The point is that the "tree-ness" is never exposed to the user. This is the problem OP is claiming to have solved - the cognitive burden that the tree solution introduces.