About errfix

What is checked before anything is written

Before an error becomes an article, a machine checks these three things. Whatever does not pass is not written up.

1. Reproduce: case.json runs inside the version-pinned image named in it and produces the exact error signature the article is about. Nothing depends on the versions on the author's machine.
2. Fix: The steps the article gives are applied exactly as written.
3. Signature gone: Re-running no longer produces that signature. The condition is "that error is gone", not "the build passed".

Each article's "Verification (machine-verified)" section carries the image used and the result of that run. The whole pipeline is on the home page.

What does not get published

• Errors that could not be reproduced. They are thrown away even when the fix seems obvious.
• Claims that do not generalise past the verified environment. Articles keep what was actually run apart from what is written on the strength of documentation, and draw no conclusion beyond the former.

The focus is errors in the environment, dependency and build layers — the kind that stay invisible locally and appear only in CI or on a particular version.

Contact

An error in an article, an environment the given steps did not fix, a missing condition for reproducing it — all of them are useful to hear about. Machine verification still only covers the environment it ran in, and what lies outside is filled in by readers' reports or not at all.

This is a receive-only address. Everything is read, though a reply is not always possible. A correction to what an article says lands more easily than a question about one particular environment.