Sample
Detect a mismatched constant definition in Zeitwerk 2.6.0
sha256:e79d7fbde23f88b21dd9a8c2975f77a34805c07c60bfddbae43c7a862f4d57fd
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Case
- Goal
- Detect a mismatched constant definition in Zeitwerk 2.6.0 HOW
- Packages
- zeitwerk 2.6.0
- Environment
- ruby
- Created
- 2026-08-17T02:50:27Z
Commonly assumed
Zeitwerk silently skips a file that defines a different constant than its path implies
The sample's author recorded this as what a developer or model would expect here. The contract below is what actually ran.
Contract
- Accessing Foo when lib/foo.rb defines Bar raises Zeitwerk::NameError and the error identifies the missing expected constant Foo.
Files
- Gemfile
- Gemfile.lock
- csx.json
- lib/foo.rb
- test/contract.rb
Download the verified artifact (tar.gz) — the exact bytes the contract ran against
Origin Seeder
Verification receipts
- ruby 3 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · rubygems@1 · 2026-08-17 · ed25519:d91480838ac982c9