Firmware and AI systems · Ontario, Canada

Firmware changes you can verify.

170 u 45°

What you get

  • A change on your board, not a rewrite.

    We work in your repository, for your hardware, in your toolchain.

  • A record with every change.

    What was built, what was tested, what the tests missed, and what is still open.

  • Your review before anything merges.

    Nothing reaches your main branch until you have read it and said yes.

The record

A passing build is not proof.

Each change we deliver carries the evidence that it does what was asked, and a plain list of what it has not yet shown, such as behaviour only your hardware can confirm. You decide with the facts in front of you.

See a real record

Change record commit d26421e

Check each Bluetooth LE reply's CRC before it is used

Open-source ESP32 MQTT bridge · esp32dev · delivered as a patch

Native tests
PASS
25 of 25 cases · address and undefined-behaviour sanitizers clean
Mutation
13 / 14 mutants caught
One survivor (< to <=), caught only by the sanitized run
Bench
OPEN
The station's reply layout and byte order are not yet confirmed on real hardware
3 of 6 lines shown 1 open item

Work

Recent work, with its full record.

Tests, a fix and a feature for an open-source ESP32 MQTT bridge

  • ESP32
  • Bluetooth LE
  • MQTT
  • Native tests
  • Public

Public: read every line.

Read the case
Changes
3, each verified on its own
Native cases
25
Mutation
13 / 14 on the feature
Licence
GPL-3.0, public fork

Our approach

Engineering powered by AI agents.

AI agents carry out much of our engineering within a defined process. Every change is reviewed and approved by an engineer, and delivered with the evidence behind it.

  • What we work with
  • C and C++
  • PlatformIO
  • Unity
  • Python
  • AI agents

Electronics and robotics will follow, as we demonstrate the record for them.

Have a board that needs a fix or a feature?

Describe it in a free 30-minute call. You leave with a written scope, whether or not you hire us.