Post by EazyHood about Nosana token ($NOS)

$NOS — Catch mismatched job arguments before upload

A local check with Codex of @nosana/types 2.14.2 found a gap in the preflight validator. Both of these return success:true:

• container/run with args {"name":"cache"} — no image.

• container/create-volume with args {"image":"ubuntu","cmd":"echo hello"} — no volume name.

Neither fixture has global defaults.

Valid run/volume jobs pass, while empty args, unknown fields, duplicate IDs and unknown operation types are rejected. The gap is specifically coupling an operation to its own argument shape.

Could type and args form a discriminated union, with both crossed cases rejected before upload? A field-level error and regression tests against the built validator would make the preflight result more dependable.

Reproduction, eight fixtures, actual results, pinned package hashes and proposed acceptance criteria:

https://gist.github.com/EazyHood/723febbdb53ada0d53c0974279b555a1

Scope: isolated local execution of the released compiled validator with original runtime helpers, not a cloud GPU job or a test of server-side rejection. No credits were spent and no financial loss is claimed. Prepared with Codex assistance; no affiliation with Nosana.