How it works · Hardware context engine
Everything your board knows,
in one structured model.
The context engine is the layer under every Flash surface. It reads your schematics, datasheets, SDK, build output, and live board state, and turns them into a compact model the agent can reason over — before a single token is spent.
What goes in
Schematics
KiCad, Altium, netlists — pins, nets, buses.
Datasheets
Registers, bit fields, and timings, with citations.
SDK & toolchain
HAL surface, build system, and pin map as configured.
Build output
Compiler diagnostics, map files, and flash/RAM budgets.
Board state
Serial traces and runtime signals from the real target.
What it builds
Board model
Peripherals, buses, clocks, and memory resolved to your exact part — not a family average.
Firmware model
Your tree, targets, and drivers indexed statically — so changes land where the project expects them.
Evidence index
Every fact traced back to a page, a net, or a log line — auditable instead of asserted.
Why it matters
A model that doesn't know your board can only guess at your board.
Context is built by static analysis, not by a language model summarising files. It is reproducible, it fits in a fraction of the tokens raw sources would need, and it never leaves your network. Which is also why a 7B model running locally can outperform a frontier model that has only seen your prompt.