Guarantees
Each one rules out a class of failure before a binary exists.
Chelis checks tensor shapes, numeric precision, side effects, and resource ownership at compile time. A dimension mismatch or a precision error is a build failure, not a runtime surprise. The same checks apply to code a model generated as to code a person wrote.
Requirements written in structured English become properties the compiler verifies, by formal proof where the math admits it and seeded testing where it does not. Every check yields an audit certificate that records what was checked and how. This holds across high-stakes domains, finance first.
The language semantics are carried in a proof assistant, so the guarantees rest on machine-checked theorems, not the compiler alone. Type soundness, dimension safety, effect correctness, linearity, and automatic-differentiation correctness are theorems a proof assistant confirms.
A correct implementation of a wrong specification is still wrong code.
