Memo on BXM.net

BXM 0.1.0 Launches With Canon and Memo, Two Open Source Tools for Repeatable Results

Thu, 22 Oct 2026 00:00:00 +0000

BXM 0.1.0 is out. It’s two small command-line tools in one repository, open source under the Apache License 2.0, with builds for Linux, macOS and Windows.

They share one idea. Same input, same bytes, same result. Canon applies it to data and Memo applies it to work.

BXM Canon is a binary encoding with exactly one valid form for every value. Two programs that encode the same data get the same bytes, whatever order they wrote the keys in and however they spelled the numbers. A hash or a signature taken on one machine holds on every other. The decoder refuses any byte string that isn’t the one encoding of its value, so a second spelling can’t sneak in through the back door.

Why CI Pipelines Redo Work Nobody Changed and How a Command Memoizer Stops It

Thu, 22 Oct 2026 00:00:00 +0000

Watch a CI log for a week and count the steps that produced exactly the same output as last time. Code generation from schemas that didn’t change. Image resizing for assets nobody touched. Test fixtures rebuilt from the same seed data. A documentation site rendered from the same pages. Each step is a few seconds or a few minutes. On every push, on every branch, on every laptop, it adds up to hours a week of machines doing work they’ve already done.

How BXM Was Tested With Two Million Damaged Inputs, Sixteen Processes and a Killed Run

Thu, 22 Oct 2026 00:00:00 +0000

Each BXM tool makes one main promise. Canon promises that every value has exactly one encoding. Memo promises that it never hands you a wrong or half-restored output. Most of the testing went into trying to break those two promises, and the results are recorded in the repository’s test/results folder by a script anyone can run again.

Canon

The property behind Canon is short to state: if the decoder accepts a byte string, encoding the decoded value gives back exactly the same bytes. If that holds, no value can have a second accepted spelling.

Memo in GitHub Actions Skipped a Rust Release Build and Caught Runners With Different Compilers

Thu, 22 Oct 2026 00:00:00 +0000

Most CI jobs build the same thing again and again. A docs fix or a typo in a README triggers the whole pipeline, and the release build runs as if the code had changed. This case study puts BXM Memo in front of one such step, a release build of the bxm-canon binary, and keeps Memo’s cache between jobs with actions/cache.

The workflow is in the repository as .github/workflows/case-study-memo.yml. Five jobs run one after another, each on a fresh GitHub-hosted runner. plain builds without Memo for the baseline. cold builds through Memo with an empty cache, warm changes nothing, docs edits the README, and source edits a Rust source file. The inputs are canon/src/**, Cargo.toml and Cargo.lock, and the salt is rustc --version, so a different compiler means a different result. We ran the whole workflow twice.

Replaying 13 Commits Through Memo Cut Test Time From 228 to 79 Seconds and Turned Up Two Flaky Tests

Thu, 22 Oct 2026 00:00:00 +0000

BXM’s repository has two packages with their own test suites: Canon, tested with cargo test, and Memo, tested with go test. Most commits touch one of them, or neither. A docs change or a new JavaScript build script doesn’t change either suite’s result, yet a plain CI job runs both every time.

So we replayed the repository’s own history. All 13 commits from 0.1.0 to the end of 0.3.0 were checked out one after another, and both suites ran at each one. That happened twice: once plain, and once with each suite behind Memo. Canon’s suite takes canon/** and the spec’s test vectors as inputs. Memo’s takes memo/**. Memo needs a declared output, so each suite writes its log to a file and that file is the output.

Why Did My Build Step Run Again, Six Cache Misses and What Memo Said About Each

Thu, 22 Oct 2026 00:00:00 +0000

A cache that misses without saying why is almost as annoying as no cache. Someone notices the step ran again, nobody knows why, and the cache key gets a random suffix “to be safe”. After that the cache never hits.

BXM Memo keeps the manifest of the last run of each named job. On a miss it compares the two and says what changed. We put that to work on a small report step: a Python script that totals sales per region from monthly CSV files into out/report.txt. The step runs through Memo with the script and data/*.csv as inputs, REPORT_CURRENCY as an environment variable that changes the result, and the Python version as the salt.