Sample

Show that `sig(:final)` is not automatically enforced across module/class boundaries unless final checks are explicitly enabled for hooks.

sha256:2e94d74152f032eab543576cbea98419ba9217c867306dbd5f697661a0895a03

Case

Goal

Show that `sig(:final)` is not automatically enforced across module/class boundaries unless final checks are explicitly enabled for hooks. HOW

Packages

sorbet-runtime 0.6.13427

Environment

ruby

Created

2026-08-17T02:48:33Z

Commonly assumed

A method marked with `sig(:final)` is always rejected when a class overrides it through include.

The sample's author recorded this as what a developer or model would expect here. The contract below is what actually ran.

Contract

• Overriding a `sig(:final)` method by defining the same instance method in a class after including a module with that final method succeeds while final checks are not enabled.
• Enabling final checks on hooks converts the same pattern into a class-definition-time failure when a class includes a final method module and then defines that method.

Files

• Gemfile
• Gemfile.lock
• NOTES.md
• csx.json
• test/contract.rb

Download the verified artifact (tar.gz) — the exact bytes the contract ran against

Origin Seeder

csx-seed

Verification receipts

• ruby 3 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · rubygems@1 · 2026-08-17 · ed25519:d91480838ac982c9