What the implementation covers
Hostile rejection values, late settlement, legacy callback behavior, dynamic job arrays, invalid null options, and abort/timeout ties.
Evidence Lab
One local Codex Hyper case reached the completion bar: accepted task, frozen baseline, implementation patch, strict checks, a fresh verifier, and a clean replay. It is a case study, not a benchmark.
Completed case · Node.js scheduler
Outcome replay PASS Workflow provenance PARTIAL Exact local build recordedThe task added bounded logical concurrency, retries, per-attempt timeouts, caller cancellation, ordered results, and deterministic tests while preserving the legacy two-argument API.
Hostile rejection values, late settlement, legacy callback behavior, dynamic job arrays, invalid null options, and abort/timeout ties.
The saved patch applies to the frozen baseline and passes its published checks. It does not prove that Hyper is generally better than another workflow.
AbortSignal. The accepted contract requires cooperative
workers and consumes late settlement to avoid unhandled rejections.
Publication bar
A featured run needs a dated task, frozen input, resulting patch, commands, a verifier verdict, and a replayable outcome. This record meets that bar.
The baseline, task, patch, checks, hashes, and final verifier summary are public and linked above.
Raw agent transcripts, runtime model ID, token usage, and end-to-end duration were not retained. The code outcome can be replayed; the complete orchestration conversation cannot.
1.0.0+codex.20260716085645 and the frozen source commit recorded in the
manifest. Hyper ships with Codex Council 1.1.0; this evidence supports this case only,
not a general performance claim.