So I built Canon-C, a small, composable set of explicit C modules that:

Treat C as an execution backend, not a semantic authority

Add meaning through libraries, not syntax

Make intent visible directly in the API: ownership, lifetime, and failure handling are explicit

Modules are organized by semantic layers:

core/ — memory, lifetime, scope, primitives

semantics/ — Option, Result, error handling

data/ — vectors, queues, stacks, string builders

algo/ — map, filter, fold, sort, search

util/ — safe string ops, file I/O, logging, timing

Design highlights:

Header-only

No runtime or global state

No hidden allocation (except in clearly marked convenience layers)

Fully explicit behavior

I’d love feedback from anyone doing systems programming, embedded C, or serious C projects, especially on macro-heavy vs. modular design, semantic clarity, and practical usage.