Garnet v0.4.2, and the case for honest accounting
v0.4.2 is live. The release — checksum-verified macOS Apple-Silicon tarball, Linux .deb/.rpm, and SHA256SUMS — was published on 2026-05-15 and the universal installer pulls and verifies it end to end. You can install it in about a minute: see Getting Started, or the v0.4.2 release.
That is the easy half of this post. Here is the more interesting half.
Two numbers that point in opposite directions
Garnet now tracks two different progress signals, and in this cycle they moved in opposite directions:
The tracked implementation ledger is 87/87 (100%). Every slice in the v0.5 readiness plan — parser parity, managed runtime, the actor/Sendable bridge, safe-mode ownership hardening, trait/generic coherence, Memory Core, and the release/installer gates — has executable evidence and is checked off. That is real, and it is verifiable: python3 scripts/garnet_readiness_status.py.
The MIT readiness pulse went down — from 58.6% to 55.8%.
A decreasing headline number, shipped deliberately, in a release announcement. That deserves an explanation, because it is the most important thing on this page.
Why the number dropped
The MIT pulse is meant to estimate distance to a genuinely production-grade, MIT-quality language and toolchain — not distance to "the current sprint is done." The Windows and Linux distribution lane (signed installers, native packaging beyond the current assets, platform smoke beyond the tarball path) was real, mostly open work that the aggregate simply was not counting. Adding it to the denominator lowered the percentage.
We could have left it uncounted and watched the number drift up. We didn't, because a metric you curate upward is not a metric — it is marketing with a progress bar. The honest move was to make the lane visible and let the aggregate fall to where the truth actually is.
The implementation ledger answers "did we finish what we scoped?" The MIT pulse answers "how far is this from something you'd bet a company on?" Both are true at once. Conflating them is how research prototypes get oversold.
What "research-grade prototype" keeps meaning
Garnet v0.4.2 is a research-grade prototype, not a production-complete language. Signed macOS .pkg and Windows MSI artifacts are not built yet. The compiler-as-agent memory work, native backend, mechanized proofs, and empirical validation are open research lanes, not shipped guarantees. The site says so in the comparison table's last row, on the install page, and now here. That framing will not soften as the numbers climb — it is part of the contract with anyone evaluating this.
What actually shipped
Beyond the release itself: the public site was rebuilt for honesty and first-run success — a prerequisite/checksum callout, a Rust-vs-Ruby-vs-Garnet positioning table, a real first-project terminal (the output is captured, not faked), a Getting Started walkthrough, an honest Community section (no Discord theater), and accessibility/SEO basics. Every change went through the same dogfood-readiness gate the language uses on itself.
If you want the pulse of the project between posts, the commit history and releases are the ground truth. This blog will carry the narrative ones — and it will keep reporting numbers that occasionally go down.