Hi brains trust.

When a Publish node is replaced with another for same resultant geometry I understand this is kind of like changing a something in the GSD realm and need to repair the children of that feature is a given.

What tips do people have to make this as easy as possible?

In the case below, 'Translate.2' takes Publish.1, but if I connect (replace it) with Publish.2, Translate.2 will error due to a missing parent.

Now obviously I'm familiar with the parts' design logic and know what was feeding what, but if someone else were to come in and edit the VS and break things, in a model with several Published objects, it's going to difficult to trace what was happening.

Questions

1. What are people doing to 'help' prevent & fix these sorts of issues?
2. Can some kind of mapping protection be implemented, a little like what GSD/Part design does to 'guess' and ghost highlight what was the parent?
3. I think is important to use something like a translate of the Publish to feed downstream features, this gives a persistent buffer feature that errors before things like Boolean, fillet etc. Thoughts?
4. Maybe some sort of warning or VS 're-map' of Published nodes that have been connected to VS built geometry and have child features outside the VS is needed?

Thanks