Sample
json 2.9.1: Navigate JSON.dump signature mismatches, JSON.load and symbolize_names addition conflicts, IO stream type rejections in JSON.parse, and custom object_class iterative mutation protocols
Verified sample for gem json 2.9.1: Navigate JSON.dump signature mismatches, JSON.load and symbolize_names addition conflicts, IO stream type rejections in…
sha256:39ffcf364c07cc97b948c6bb4328939ce72e0c3d5458a40ec72e4fa5c5128aef
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
- Navigate JSON.dump signature mismatches, JSON.load and symbolize_names addition conflicts, IO stream type rejections in JSON.parse, and custom object_class iterative mutation protocols
- Packages
- Symbols
-
- JSON.parse
- JSON.load
- JSON.dump
- JSON.create_id
- JSON.load_default_options
- Environment
- ruby
- Created
- 2026-08-17T02:42:37Z
Contract
- assert JSON.parse rejects IO streams with TypeError while JSON.load accepts them directly
- assert JSON.load with symbolize_names as second positional arg treats it as proc and silently leaves String keys
- assert JSON.load with symbolize_names as options conflicts with implicit create_additions and raises ArgumentError unless create_additions is false
- assert JSON.dump rejects kwargs and treats non-IO second arguments as limit or raises NoMethodError
- assert JSON.parse with object_class and array_class instantiates via arity-zero new and populates iteratively via []= and <<
- assert create_additions instantiates classes defining json_create matching JSON.create_id and leaves others as Hash
- assert freeze: true in JSON.parse deeply freezes containers and string keys and values
Files
- Gemfile
- Gemfile.lock
- NOTES.md
- csx.json
- src/json_api.rb
- test/contract.rb