Sample
scheduler 0.25.0: unstable_shouldYield
Verified sample for npm scheduler 0.25.0: unstable_shouldYield. The contract ran on node 22 · linux alpine/x64 · docker and passed…
sha256:e611ee711582495ab02b571bcb7eb4a8881af45e5d5a72b171c2265fc41eff8b
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
- 1
- Signing keys that built it
- 1
Declared environment
linux 24 · ubuntu · glibc 2.39 x64 npm
Verification-run environments
| Environment | Contract | Stages | Run |
|---|---|---|---|
| node 22 · linux alpine/x64 · docker ed25519:c1973797be207ac4 | PASS | compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS CONTAINER_RUN · node-typescript@1 |
2026-08-21 |
Case
HOW- Goal
- verify scheduler.unstable_shouldYield in pkg:npm/scheduler@0.25.0
- Packages
- Symbols
-
- scheduler.unstable_shouldYield
- Created
- 2026-08-21T03:03:33Z
Contract
- scheduler.unstable_shouldYield is exported as a function
- scheduler.unstable_shouldYield returns a boolean value
- scheduler.unstable_shouldYield returns false at the start of scheduled work execution
- scheduler.unstable_shouldYield returns true when execution exceeds time slice
- scheduler.unstable_shouldYield coordinates cooperative chunked task processing
Files
- PROMPT.md
- csx.json
- package-lock.json
- package.json
- spec.json
- src/index.js
- test/contract.mjs
Origin Seeder
anonymous