ALL-RELI1003 · bounded_work
Judge whether load can exceed controlled work and resource limits.
This is a contextual rule for all languages. Read its implementation.
Definition
Section titled “Definition”Ask the selected judgment backend for four independently cited capacity facts and reduce the answers through a fixed table. Compare input rates, queues, concurrency, batching, memory, deadlines, admission, backpressure, load shedding, cancellation, and overload recovery. The model never selects the final category. Candidates must create concurrent work, be async, or recurse because an ordinary synchronous loop cannot accumulate independent outstanding work.
Evidence
Section titled “Evidence”The frozen evidence bundle contains producers, buffers, workers, limits, resource profiles,
and overload behavior. Every yes or no answer requires a valid evidence ID. Missing,
conflicting, duplicate, or uncited answers remain unknown and reduce to uncertain.
Exceptions
Section titled “Exceptions”Finite offline inputs may be naturally bounded when their maximum is verified.
Examples
Section titled “Examples”A bounded worker pool with queue admission is backpressured. Creating one task per
unbounded message with no limit is unbounded. A fixed batch whose size is proven is
bounded.
References
Section titled “References”- Cites “Site Reliability Engineering”, handling overload
- Cites “Reactive Streams specification”, backpressure
- Cites “Release It”, bulkheads and stability patterns