Sample
zeitwerk 2.8.3: Autovivify namespace modules with Zeitwerk across empty directories, non-Ruby assets, and multi-level subdirectory trees
Verified sample for gem zeitwerk 2.8.3: Autovivify namespace modules with Zeitwerk across empty directories, non-Ruby assets, and multi-level subdirectory…
sha256:8fa0af5cf0e7a129c995c34fca5c50864a243c0f2ab9a568a2c7a3633e99b46b
This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured.
How many distinct signing keys filed a passing contract receipt. One is the author alone; more than one means somebody else built it too. A key is self-generated with nothing registered behind it, so it counts keys, not people.
MIT-0
Execution evidence
The declared environment and the signed runs are kept apart, so you can see exactly what this sample ran and where.
- Evidence basis
- Signed contract pass
- Verification receipts
- 2
- Signing keys that built it
- 1
Declared environment
ruby linux x64 ruby ruby rubygems
Verification-run environments
| Environment | Contract | Stages | Run |
|---|---|---|---|
| ruby 3 · linux debian/x64 · docker ed25519:d91480838ac982c9 | PASS | compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS CONTAINER_RUN · rubygems@1 |
2026-08-16 |
| ruby 3 · linux debian/x64 · docker ed25519:2175b912ea1c23b1 | SKIPPED | compile:SKIPPED · contract:SKIPPED · load:SKIPPED · resolve:FAIL CONTAINER_RUN · rubygems@1 |
2026-08-18 |
Case
HOW- Goal
- Autovivify namespace modules with Zeitwerk across empty directories, non-Ruby assets, and multi-level subdirectory trees
- Packages
- Symbols
-
- Zeitwerk::Loader#push_dir
- Zeitwerk::Loader#setup
- Zeitwerk::Loader#all_expected_cpaths
- Zeitwerk::Loader#cpath_expected_at
- Zeitwerk::Loader#eager_load
- Environment
- ruby
- Created
- 2026-08-16T17:20:20Z
Contract
- assert empty directories and directories containing only non-Ruby assets or hidden dotfiles do not autovivify namespace modules and raise NameError on constant access rather than resolving to Module instances
- assert loader.all_expected_cpaths only tracks directories that contain Ruby source files, omitting empty and non-Ruby directories while cpath_expected_at still computes hypothetical inflection names
- assert accessing nested constants through directories lacking matching Ruby files autovivifies intermediate namespace segments strictly as Module instances, which causes class re-opening to fail with TypeError
- assert providing an explicit matching Ruby file defining a Class allows subsequent nested classes and class re-openings without TypeError
- assert loader.eager_load walks all valid Ruby file trees and autovivifies intermediate modules while leaving empty and non-Ruby directories completely uninitialized
Files
- Gemfile
- NOTES.md
- app/asset_dir/README.md
- app/asset_dir/config.json
- app/backup_dir/handler.rb.bak
- app/billing.rb
- app/billing/invoice.rb
- app/billing/invoice/line_item.rb
- app/domain/order/item.rb
- app/empty_dir/.gitkeep
- app/hidden_dir/.secret.rb
- app/services/README.md
- app/services/worker.rb
- csx.json
- test/contract.rb