LOX · Liquid Oxygen for Embedded Systems

LOX Dust

Small persistent objects need a canonical layout and recovery checks without storing raw C structs.

A portable object store registers fixed objects, computes deterministic layout and exposes format, mount, propose, check and repair operations.

DevelopmentMITC99
GitHubQuick Start
Last verified
Not audited against current README/docs
Platform scope
Portable C99; integration depends on caller-provided adapters

What it solves

Small persistent objects need a canonical layout and recovery checks without storing raw C structs.

How it works

1Application object→2registered layout→3check/repair→4backend

Use it when

Persist a small configuration object
Validate object layout on mount
Check and repair redundant object state
Use host backends while developing an adapter

Quick Start

#include "loxdust/loxdust.h"
/* Register objects and provide a storage backend as documented. */
/* Format once, then mount and read/write registered objects. */
/* Expected: explicit status from every storage operation. */

Engineering evidence

  • Source includes tests and host-side backends
  • Repository documents canonical fixed-width encoding and caller-owned context

Known limits

  • Not a general database or filesystem
  • Backend durability and power-loss behavior depend on the supplied backend
  • Object schema and storage sizing are fixed by the application