Design Activity Verification
The Design Activity C module requires boundary and numerical tests before a release is treated as build-verified.
Required tests:
- Normalize six valid 0–100 measurements.
- Reject null input/output.
- Reject values below 0, above 100, NaN, and infinity.
- Validate every supported science domain.
- Reject unknown domains.
- Compare normalized and reference vectors.
- Verify zero variance when vectors are identical.
- Verify finite variance, RMS deviation, and L2 distance.
- Reject non-finite comparison vectors.
- Verify JSON output rejects unsafe executable names and reports buffer exhaustion.
- Run the same tests under Linux, macOS, and Windows CI.
- Run the tests with warnings enabled and treat warnings as errors where the platform toolchain supports it.
The production module performs no dynamic allocation, so the tests should remain deterministic and bounded.
A design-activity record is a software conformance record. It must not be presented as a physical measurement uncertainty statement.