Sample
zeitwerk 2.8.3: Show that Zeitwerk reload support is opt-in before setup and that `unload` is intentionally ineffective until then.
Verified sample for gem zeitwerk 2.8.3: Show that Zeitwerk reload support is opt-in before setup and that `unload` is intentionally ineffective until then.…
sha256:2a90ce3c040d689d13a78f69612cc42ce3d1451ba0e44e9418dd497a657ab283
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
- 2
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-17 |
| ruby 3 · linux debian/x64 · docker ed25519:2175b912ea1c23b1 | PASS | compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS CONTAINER_RUN · rubygems@1 |
2026-08-18 |
Case
HOW- Goal
- Show that Zeitwerk reload support is opt-in before setup and that `unload` is intentionally ineffective until then.
- Packages
- Symbols
-
- Zeitwerk::Loader
- Zeitwerk::Loader#enable_reloading
- Zeitwerk::Loader#reload
- Zeitwerk::Loader#unload
- Environment
- ruby
- Created
- 2026-08-17T02:49:45Z
Contract
- assert a loader without `enable_reloading` raises `Zeitwerk::ReloadingDisabledError` on `reload` after `setup`, and then `unload` keeps a previously loaded constant in place
- assert enabling reloading after `setup` raises `Zeitwerk::Error` and leaves `reloading_enabled?` false
- assert enabling reloading before `setup` makes `unload` remove a loaded constant so that the next reference is a `NameError`
Files
- Gemfile
- Gemfile.lock
- NOTES.md
- csx.json
- fixtures/noreload/no_reload_widget.rb
- fixtures/reload_after/reload_after_widget.rb
- fixtures/reload_enabled/reload_enabled_widget.rb
- fixtures/reloadable/with_reload_widget.rb
- test/contract.rb