Type-system failures refused
Chelis rejects shape, precision, effect, and ownership errors during build. These are language-level failures, not test cases that have to find the bad path.
Proofs
What C Proof checks
C Proof separates language failures from specification checks. The type system rejects bug classes in Chelis code. The property layer checks an implementation against the specification it was given.
Type system
Refuses invalid programs
- Shape
- Precision
- Effects
- Ownership
Property layer
Checks against specifications
- Payoff invariants
- Risk bounds
- Portfolio constraints
- Model requirements
Implementations checked against specifications
Requirements become computationally verifiable properties. The property layer checks the implementation against those specifications and records what was checked.
Proofs back the language rules
Proof artifacts support the rules Chelis relies on: type soundness, dimensional consistency, effect discipline, ownership, and differentiation behavior.
Boundary
Checks are only as good as the specification
A correct implementation of a wrong specification is still wrong code. C Proof makes the checked surface inspectable, so model owners can review the requirements, properties, proofs, and artifacts behind the binary.