What it solves
Embedded configuration needs validation and corruption-aware persistence.
How it works
1Schema + defaults→2validation→3canonical two-slot storage
Use it when
Validate a fixed device configuration
Load defaults with explicit sizes
Persist configuration in two slots
Quick Start
#include "mconf.h"
/* Define a schema, caller-owned data, then initialize mconf_t. */Engineering evidence
- Documentation marks verified and NOT VERIFIED areas
Known limits
- No automatic schema migration
- CRC32 detects corruption, not authentication
- Some verification is explicitly pending