A lightweight C99 guard-runtime. Explicit execution boundaries around risky code — parsers, protocol handlers, optional modules, recovery-sensitive routines.
Instead of only failing with an assert or watchdog reset, loxguard turns failures into structured runtime evidence. It introduces Guard Blocks and Checked Guard Blocks: explicit execution boundaries around code that can go wrong.
Guard Block lifecycle tracking with failure reporting.
Structured decisions when something fails inside a guard.
Local blackbox evidence and reports for post-mortem analysis.
Checked span and arena primitives for safer buffers.
CSV and KV import-export paths.
Optional persistence and adapters into the wider LOX ecosystem.
loxguard does not claim full memory safety for arbitrary C code and is not a safety-certified framework. Its value is narrower: make unsafe execution states easier to detect, record and react to in small embedded C systems.