Compatibility
The design follows CRuby’s builtin-validation behavior while adapting the mechanism to JRuby’s different concurrency model.
JRuby 10.1+ deployment
Valen Systems code ships worldwide in JRuby 10.1+.
Co-founder Troy Mallory’s builtin-tracking architecture was merged upstream through PR 9174, then expanded across JRuby’s runtime fast paths by maintainer Charles Oliver Nutter.
Shipped upstreamCore runtime infrastructurePublic evidence
JRuby PR 9174
One pull request became runtime infrastructure.
PR 9174 didn’t remain a promising experiment. It crossed the line that separates private invention from public infrastructure: maintainers reviewed it, merged it, expanded it, and shipped it.
JRuby needed a CRuby-compatible way to determine whether a builtin method was still safe to use without sacrificing JRuby’s true parallelism. Troy designed a thread-local tracking system with lock-free reads, tested the approach in Kestowv OS, and opened the implementation upstream as CufeHaco.
JRuby did more than accept the contribution. Maintainer Charles Oliver Nutter merged it, extended it, and integrated the architecture across core runtime fast paths. The release lineage carried that work into JRuby 10.1.0.0, and the credited implementation remains present in JRuby 10.1.1.0.
Deployment record
Reviewed outside the company. Shipped inside the runtime.
This is independent adoption, not a Valen Systems benchmark presented as deployment proof.
- Status
- Shipped upstream
- Runtime
- JRuby 10.1+
- Contributor
- Troy Mallory, CufeHaco
- Maintainer
- Charles Oliver Nutter
- Layer
- JRuby core runtime infrastructure
- Origin
- Author-reported Kestowv OS validation
What changed
Fast paths can verify the builtin before they trust it.
The architecture tracks builtin state per thread, preserves JRuby’s parallel execution model, and gives optimized runtime paths a low-overhead way to fall back when Ruby code replaces a builtin.
Parallelism
Thread-local state avoids turning a compatibility check into a global lock around a runtime built for true parallel work.
Integration
The maintainer expansion carried the mechanism beyond one patch and into the fast paths that need to know whether a builtin remains valid.
Author-reported validation
Microsecond decisions measured in nanoseconds.
These figures come from the PR 9174 submission. They measure builtin-validation checks, not the complete Ruby operations.
15ns → 3nsInteger plus builtin check
18ns → 4nsString bracket builtin check
12ns → 3nsArray append builtin check
20ns → 5nsRange include builtin check
The PR author reported roughly 4x to 5x gains for these validation checks. Valen Systems hasn’t presented them as independent end-to-end benchmarks of the full Ruby methods.
Evidence chain
From Kestowv to the JRuby release line.
Each step is public, attributable, and inspectable.
- 01Kestowv validation
Troy reported testing the architecture in Kestowv OS before opening it upstream.
- 02CufeHaco contribution
PR 9174 introduced complete thread-local builtin tracking for JRuby.
- 03Maintainer review and merge
Charles Oliver Nutter merged the contribution into JRuby.
- 04Maintainer expansion
A follow-on commit explicitly credits PR 9174 and extends the mechanism across runtime integrations and fast paths.
- 05JRuby 10.1 release
The contribution is an ancestor of JRuby 10.1.0.0 and remains credited in the 10.1.1.0 source.
Inspect the public record.
The deployment claim is backed by the upstream pull request, merge history, maintainer expansion, release lineage, and current credited source.
Working through a hardware or runtime decision? Explore compute evaluations