The problem is that the granular permissions the SRU and Release teams have are based solely on the queue, and not the archive. Once a package is accepted, those queue permissions become irrelevant, and the archive admins own it.
I don't disagree with what would be the ultimate conclusion here, which is that finer-grained archive admin permissions per series and pocket would be desirable (though, there'd also need to be extra training/caution involved before handing people the ability to break things as spectacularly as incorrect deletions can), but I suspect it'd be quite an overhaul to retrofit that request into LP.
The problem is that the granular permissions the SRU and Release teams have are based solely on the queue, and not the archive. Once a package is accepted, those queue permissions become irrelevant, and the archive admins own it.
I don't disagree with what would be the ultimate conclusion here, which is that finer-grained archive admin permissions per series and pocket would be desirable (though, there'd also need to be extra training/caution involved before handing people the ability to break things as spectacularly as incorrect deletions can), but I suspect it'd be quite an overhaul to retrofit that request into LP.