BENCHMARK STREAM

Submission readiness

A mature candidate needs immutable images, clean compose output, and repeated benchmark evidence. The official Rinha issue flow should use the registered participant id only after the submission branch is verified.

Promotion is not a single fast run. The participant must stay within the 1 CPU and 350 MB envelope, avoid build directives in submission compose, and report zero false positives, false negatives, and HTTP errors.