Skip to content

Independent C11 verification

The project includes an independent C11 conformance consumer. Its purpose is to demonstrate that the language-neutral contract can be implemented outside Python and to exercise real C floating-point behavior for numerical validation.

Independent C11 conformance consumer available since: rtd-sensor 0.5.0.

Why independent matters

If the verification path simply called back into the Python implementation or copied private Python internals mechanically, it would provide weak evidence that the published contract was actually sufficient for another language.

The C11 path instead acts as an independent consumer of the behavioral contract.

Verification code versus production firmware

The C11 consumer should not automatically be treated as the ideal production embedded library. Production firmware may need:

  • static allocation;
  • model-selection at compile time;
  • MCU-specific API design;
  • toolchain support;
  • code-size constraints; and
  • application-specific fault integration.

Those are separate engineering decisions. The conformance consumer establishes behavioral reproducibility first.

Exact implementation material

The engineering details and artifact verification process are documented in docs/CONFORMANCE.md and the repository test/conformance sources.