Sample
zeitwerk 2.8.3: Demonstrate that calling Zeitwerk::Loader.setup twice does NOT raise an error
Verified sample for gem zeitwerk 2.8.3: Demonstrate that calling Zeitwerk::Loader.setup twice does NOT raise an error. The contract ran on ruby 3 · linux…
sha256:a5bd61b88ee5503ac32ff50c101ec7c975cdb0b65042a507ecefa5c3fae19bf2
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 bundle
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
- Demonstrate that calling Zeitwerk::Loader.setup twice does NOT raise an error
- Packages
- Symbols
-
- Zeitwerk::Loader
- Environment
- ruby
- Created
- 2026-08-17T02:50:07Z
Contract
- Second call to loader.setup does NOT raise an error
Files
- Gemfile
- Gemfile.lock
- csx.json
- lib/dummy.rb
- test/contract.rb