A public inventory reader splits a reviewed identifier list into two concurrent service RPC batches. Each response must contain exactly the requested identifiers in input order. Returning the first successful batch when the other fails would publish an incomplete inventory as a successful result. How should complete-result assembly, identity validation and shared cancellation be structured so a slow or malformed batch fails the whole read without mixing records or returning partial data?