What ensure would withdraw

A product runs as one process per host, and every other unit there that runs its program is its predecessor (lifecycle).

stado service predecessors <product> --host <target> [--json] reads, by the same rule and without changing anything, every unit ensure of the product would withdraw there: replaced (taken down whole), obsolete (a host Stado unit invoking a root verb this build no longer has), roles (units doing a role of com.wisent.stado, with flag, readiness and handed_over for a listener the reconciler hands over), kept (one-pass units read and left, with why), withdrawn (every unit of the first three) and running (the product's declared unit there, whose live role paths the read takes in, or null). A product the catalogue declares no service for answers "catalogued": false and withdraws nothing. A host whose units, home or live process cannot be read refuses with <target>: the units \stado service ensure ` would withdraw could not be read and the cause. The real journeys that load units into an account's own launchd read it before every command they run (tests/release_common/launchd_hold.mjs`), so what the product would take down is the product's answer, not a second copy of its rule.