Eh, screw being clever.  The first principle of optimization is not to overcomplicate your problems; and the first question about inherent problem complexity is "Can I solve this problem simply by using an explosion?"  Often the moment you ask yourself, "Could I solve this problem using an explosion?", you can see it's not a complicated problem.

Nobody put Eriape under serious guard.  He'll just Dominate an adventurer and have them explode the lump of petrified stone, Eriape, and of course themselves.  Then Eriape resurrects from her phylactory, and then he shows up via Discern Location scroll.  It is definitionally not complicated.

But the first principle of optimization is not to overcomplicate your problems; and the first question to ask about inherent problem complexity is, "Can I solve this problem simply by using an explosion?"  Often the moment you ask yourself, "Could I solve this problem using an explosion?" you can see it's not a complicated problem.

Nobody put Eriape under serious guard.  He'll just Dominate an adventurer and have them explode the lump of petrified stone, Eriape, and of course themselves.  Then Eriape resurrects from her phylactory, and then he shows up via Discern Location scroll.  It is definitionally not complicated.

But the first principle of optimization is not to overcomplicate your problems; and the first question to ask about inherent problem complexity is, "Can I solve this problem simply by using an explosion?"  Often the moment you ask yourself, "Could I solve this problem using an explosion?" you can see it's not a complicated problem.

Nobody put Eriape under serious guard.  He'll just Dominate an adventurer and have them explode the lump of petrified stone, Eriape, and of course themselves.  Then Eriape resurrects from her phylactory.

It is definitionally not complicated.

But the first principle of optimization is not to overcomplicate your problems; and the first question to ask about inherent problem complexity is, "Can I solve this problem simply by using an explosion?"  Often the moment you ask yourself, "Could I solve this problem using an explosion?" you can see it's not a complicated problem.

Nobody put Eriape under serious guard.  He'll just Dominate an adventurer and have them explode the lump of petrified stone, Eriape, and of course themselves.  Then Eriape resurrects from her phylactory.

It is, definitionally, not complicated.

But the first principle of optimization is not to overcomplicate your problems; and the first question to ask about inherent problem complexity is, "Can I solve this problem simply by using an explosion?"  Often the moment you ask yourself, "Could I solve this problem using an explosion?" you can see it's not a complicated problem.

Nobody put Eriape under serious guard.  He'll just Dominate an adventurer and have them explode the lump of petrified stone, Eriape, and of course themselves.  Then Eriape resurrects from her phylactory -- which she has successfully kept hidden, or the mage wouldn't bother with the Dominate.

It is, definitionally, not complicated.

But the first principle of sanity is to not overcomplicate your problems; and the first question to ask about inherent problem complexity is, "Can I solve this problem just by using an explosion?"  Often the moment you ask yourself, "Could I solve this problem using an explosion?" you can see it's not a complicated problem.

Nobody put Eriape under serious guard.  He'll just Dominate an adventurer and have them explode the lump of petrified stone, Eriape, and of course themselves.  Then Eriape resurrects from her phylactory -- which she has successfully kept hidden, or the mage wouldn't bother with the Dominate.

It is, definitionally, not complicated.