Align the cloud ATU

The account owner becomes explicit

This is where a correctly routed registration turns into a named seller: the cloud's account or territory owner is pre-wired with the buyer, workload, expected usage, services role, and a proposed next meeting. The seller then has to explicitly accept the role and the next action — silence or a decline routes the pursuit into repair, not into a dead end.

A pursuit can sit in a correctly registered state and still fail here if the seller never confirms ownership of the next action. That confirmation, not the registration record, is what unlocks joint discovery.

When acceptance doesn't happen

Declined or silent responses get diagnosed by reason — wrong owner, duplicate record, weak evidence, weak economics, an incumbent, or bad timing — and routed to reroute, strengthen, nurture, or exit rather than left unresolved in the pipeline.