Follow one number
from the pin to the prompt.
This is the entire pipeline, end to end. A single pitch reading leaves your ESP32, rides AlloyLogger into Alloy Mesh Storage, and comes back through the Alloy MCP as an answer in Claude Code. Watch the same 8.2° change shape at every layer.
The wobble happens
Your control loop reads the IMU over I²C at 100 Hz. Each reading lives for one loop tick, then it's overwritten. Without a logger, it's gone.
i2c 0x28 · bno055 · 100 Hz pitch → 8.2°
in your loop()
signed, batched upload
The number gets a name
log() names the value, formats one compact CSV row, and buffers it in RAM in microseconds; your loop never blocks. A background task on core 0 batches rows into per-channel chunks and uploads over TLS every 4 s, store-and-forward across WiFi drops. No SD card, no flash wear.
12
13
alloy.log("bno055") .set("pitch", pitch); // RAM buffer → core 0 → TLS · 4 s
It lands on the timeline
Every power-on becomes one run under your mesh path. When it ends, Alloy assembles one indexed .mcap mission plus a meta.json semantics sidecar: replayable, scrubbable, and queryable in place with SQL.
| A | B | C | |
|---|---|---|---|
| 1 | time | heading | pitch |
| 2 | 0.5 | 187.0 | 2.4 |
| 3 | 0.6 | 187.4 | 4.9 |
| 4 | 0.7 | 187.6 | 8.2 |
no exports · no CSVs
Claude reaches in
One command connects Claude to your mesh. It gets real tools, list_missions, get_mission_summary, query_mesh_storage: read-only SQL over every run you have ever streamed.
The number comes back as an answer
Claude writes the SQL itself, pulls the rows, and answers from your data, comparing run #47 against every run before it. Same reading, five layers later.