A new service has the same familiar failure modes with different request patterns. Admission, cancellation, retries and acknowledgments each have their own boundary. Choose the contract named in the prompt rather than applying one generic error handler to everything.
This set mixes deterministic reasoning with actual coroutine execution. A sliding-window check differs from the fixed-window project; its left boundary expires old accepted requests. Retry decisions use supplied statuses and never contact a real endpoint. Queue work must preserve data and finish its owned tasks. The examples include exact limits, zero values and empty batches. No new concept is introduced, but the combination requires you to keep several earlier invariants separate while producing one precise result per task.