argenv
a declared, typed, machine-readable contract for a program's argv and env
Why it exists
Every program is told what to do in two ways when it starts: by the words typed after its name, and by settings left waiting for it in its environment. Almost no program writes down what it accepts in either.
What it must reach
3 / 4 milestones done
How each step is delivered and proven
One constant in the code is at once the contract's entry, the typed reader of the value, and a name the compiler checks.
Two things kept in step by hand drift apart. One thing cannot.
Checks a way of starting a program against its published contract: unknown names, values out of range, required inputs missing.
Failures that are normally silent become something a tool reports.
Released where Rust programs get their libraries, with its documentation built from the code.
An idea nobody can install is not yet a tool.
One of our own tools declares its inputs with argenv and runs on it.
A library nobody uses has proven nothing.
Nothing delivers this step yet.
Joined with one command; its activity and releases gathered daily.
So its state is seen with everything else's, without being reported by hand.
What is happening now
Made by work
66 commits in the last 90 days latest release argenv-v0.4.0 · 2026-11-17