FerrisOxide
The broader Rust-centered workspace direction for signal analysis, validation evidence, controller simulation, rule packages, and future runtime targets.
About the project
FerrisOxide is about making signal evidence inspectable.
The current implemented slice is FerrisOxide Signal: a Rust CLI and library workflow for turning local CSV waveform data into auditable pass/fail evidence.
Why it exists.
Engineering signal review often starts as a one-off script, spreadsheet, screenshot, or manually interpreted plot. That is workable for a quick look, but fragile when a reviewer needs to understand exactly what data was used, what rules were applied, and why a run passed or failed.
FerrisOxide focuses on repeatable analysis. The same CSV waveform and the same explicit configuration should produce the same evidence, with raw data preserved and derived transforms recorded as derived artifacts.
The project is Rust-centered because the long-term direction includes deterministic, constrained, embedded-compatible rule evaluation. The current desktop workflow is the authoring and validation side of that path.
FerrisOxide and FerrisOxide Signal.
FerrisOxide is the umbrella workspace. FerrisOxide Signal is the active signal-analysis slice inside that workspace.
FerrisOxide Signal
The implemented CLI and library workflow for CSV waveform analysis, criteria evaluation, reports, plots, and portable evidence artifacts.
ferrisoxide-signal
The current CLI binary and signal primitive crate identity used for the active signal-analysis product slice.
Current maturity.
FerrisOxide is in a validated MVP stage. It has a substantial local-file workflow, source-backed tests, golden reports, software-only validation fixtures, and early embedded-facing boundaries.
That maturity is deliberately bounded. The project does not present itself as a finished commercial system, certified validation system, live controller runtime, hardware qualification platform, or cloud service.
Implemented
CSV loading, criteria evaluation, text/JSON reports, SVG plots, rule packages, simulation fixtures, and no_std-oriented foundations.
Future
Runtime loaders, Raspberry Pi 5 bare-metal runtime work, and optional Pico 2 micro-runtime profile.
Not claimed
Certification, hardware validation, live DAQ integration, production RTOS readiness, full GUI, or cloud product behavior.