Read `BENCHMARK.md` carefully. Write a single, complete, plug-and-play Zig 0.17.0 theme file for Argus following all 8 Hard Harness Gates (`Allocs at Init == 1`, `Allocs after Init == 0`, `Watchdog 320x200: PASS`, `y * stride + x` indexing, `0xFF` alpha on every pixel, zero NaNs, `Temporal Motion >= 2000 animated pixels`, `< 16.6 ms/frame` at `1920x1200` on CPU). Prefer `sdk.addRGB`, `sdk.scaleRGB`, `sdk.lerpRGB`, and `sdk.Canvas` to avoid Zig 0.17 peer-type narrowing and unsigned subtraction underflow. Output the complete `.zig` source in one fenced zig code block, ready to save as `themes/<YourModel>_<ThemeName>.zig`, then one line telling the user to paste your whole answer at https://gke0op.github.io/argus/bench/ to watch it run and get graded.
2Grade a Zig theme
Zig 0.17.0, built to WebAssembly, compiles your theme in this page; nothing is uploaded.
How this differs from the native harness
Zig compiles in this page. Zig 0.17.0, built to WebAssembly, compiles your theme in the browser; nothing is uploaded. The first compile downloads 4.6 MB, cached after.
Two differences from the native harness: Gate 1 type-checks for wasm64 (64-bit usize, so the leaderboard’s common u32/usize error still fails), and Gate 8 times a build without LLVM or SIMD, so it runs slower. The official verdict is a pull request.
The pull request is the official verdict: it opens GitHub’s new-file page with your source on the clipboard, and CI runs the native harness and comments.
File name and a .wasm you built
.zig, saved as bench/submissions/Model_Theme.zig
A .wasm from make web-wasm THEME=themes/Model_Theme.zig (LLVM, SIMD128) runs the gates too; use its .st.wasm unless this page is cross-origin isolated.
Harness report and frame 120Frame 120 at 1920×1200, as the gates saw it.
Gate 8 here times this browser on this machine; leaderboard times are the native harness on an M3.
3Submissions, live
Every theme a pull request adds to bench/submissions/, by model, graded by the native harness.
How the board is checked
Every theme a pull request adds to bench/submissions/, by model, a few minutes after it is opened. The native harness on the pull request gives the official verdict. The reference is the same theme graded in CI by this page’s compiler; Re-grade here must reproduce its module (SHA-256) and gates 1–7 under the same ruler, so nobody has to take the board’s word for it.
loading the feed…
Model
Theme
Pull request
Status
Native
Reference
Your browser
1The prompt
The GPU track, written for this page. The full copy adds the WGSL contract, the prelude and Tutorial_Tides.wgsl as an example.
Write a single WGSL theme for Argus’s WebGPU runtime, following the contract below (the prelude is prepended to your file). The entry point is `@compute @workgroup_size(8, 8) fn argus_draw(@builtin(global_invocation_id) id: vec3u)`, writing every pixel with `textureStore(argus_out, gid, vec4f(colour, 1.0))`; add `argus_init` / `argus_step` and a `// @argus state WxH` line if your simulation needs persistent state. It must pass the Argus Metal harness’s checks, as run in the browser: compiles, runs at 320x200, no NaN or Inf, more than 100 distinct pixels, at least 2,000 pixels visibly animated between frame 1 and frame 120 (dt = 1/30 s), and under 8,333 µs average GPU time per frame at 1920x1200. Simulate a real physical or mathematical system. Output the complete .wgsl source in one fenced code block, then one line telling the user to paste your whole answer into the WGSL tab at https://gke0op.github.io/argus/bench/#wgsl to watch it run and get graded.
2Paste and run
Compiled by this browser’s WebGPU; nothing is uploaded.
RUNNING
Live, after the checks.
Harness report and frame 120Frame 120 at 1920×1200, as the checks saw it.
The Metal harness’s checks (make harness THEME=themes/X.metal) on WebGPU. Alpha is shown, not gated, as in the Metal harness. Chrome rounds GPU timestamps to 100 µs.
Drop a .zig, .metal or .wgsl theme to grade it here or the .wasm you built from a .zig