ri-esp-core 0.1.1

no_std shared traits and types for ESP32/S3 sensor nodes, displays, and endpoints
Documentation
  • Coverage
  • 0%
    0 out of 28 items documented0 out of 12 items with examples
  • Size
  • Source code size: 13.1 kB This is the summed size of all the files inside the crates.io package for this release.
  • Documentation size: 306.22 kB This is the summed size of all files generated by rustdoc for all configured targets
  • Ø build duration
  • this release: 8s Average build duration of successful builds.
  • all releases: 5s Average build duration of successful builds in releases after 2024-10-23.
  • Links
  • Homepage
  • RecursiveIntell/esp32-reusable
    0 0 0
  • crates.io
  • Dependencies
  • Versions
  • Owners
  • RecursiveIntell

ri-esp-core

Shared no_std types for ESP32/S3 sensor nodes.

ri-esp-core architecture

What it provides

EnvironmentReading, ReadingStatus, display traits, sensor traits.

It is dependency-light and designed for embedded reuse.

Install

[dependencies]
ri-esp-core = "0.1"

Quick start

// See crate docs/tests for complete examples.

API shape

  • no_std by default
  • fixed-capacity data structures where strings/payloads are needed
  • explicit receipt/schema constants where the crate crosses firmware/host boundaries
  • small public API intended to be readable in firmware reviews

Verification

From the workspace root:

cargo test -p ri-esp-core
cargo +esp check -p ri-esp-core --target xtensa-esp32s3-none-elf -Z build-std=core,alloc

This crate is also covered by the workspace gate:

cargo test --workspace

Integration path

Use this crate as one boundary in the larger ESP32 physical-AI stack:

sensor reading -> deterministic policy -> local-language receipt -> proof receipt -> display/log/optional escalation

Claim boundary

This crate is a reusable building block. It does not certify physical wiring, safety-critical behavior, production deployment, or model quality outside tests/receipts stated in the repository.

License

MIT OR Apache-2.0