All tasks

Deployment Batch Planner

GoHardClorvin Labs original task

The rollout planner needs predictable batches without placing too many instances from one zone together. Implement batching so capacity and per-zone limits both hold throughout the rollout.

Build the implementation in Go under /app, with /app/run.sh as its entry point. Read one JSON request from standard input and write one JSON result to standard output. Input has positive integer max_batch and per_zone, and hosts with unique name and zone. For each batch scan remaining hosts in original order, selecting a host if batch size and that zone count allow; deferred hosts remain for later batches in original order. Return host-name batches until none remain. Reject duplicate host names or invalid limits.

Reject inputs that violate an explicit validation rule with exit status 2, no standard output, and {"error":"invalid_input"} on standard error. For valid input, exit with status 0. Keep the implementation reusable for new inputs; it must work offline and must not depend on the example data being the only data it receives.

Repair or replace the unfinished /app/run.sh and add source files under /app. Malformed JSON must use the same invalid-input response. Do not read /tests or /oracle from the application.

Inspect the checks. Explore the results.

9 recorded reference checks

Review the checks and explore the evaluation view for deployment batch planner.

Example dataExplore the controls with illustrative values. These are not recorded GPT-5.5 or Opus 4.8 results.
Read the example values
Illustrative reward values, not model test results
AttemptGPT-5.5 (demo)Opus 4.8 (demo)
100.25
20.250.5
30.50.5
40.751
50.50.75
610.75
70.751
811

Tell us what needs doing.

Share the scope, the expected volume and your timeline.
We’ll work out where our team can help.