Packages, hashes & rights
What gets downloaded and what downloading or holding a token actually permits.
Inside the ZIP
| File | Purpose |
|---|---|
| manifest.json / spec.json | Package format, exact task configuration and specification hash. |
| initial-state.json / POLICY.txt | Original orders and the policy your agent must use. |
| runner.mjs | Dependency-free reference baseline or grader for your decision JSON. |
| server.mjs / environment.html | Portable HTTP and browser task environment. |
| LICENSE.txt / README.md | Private evaluation terms and local instructions. |
Run an exported environment
Use Node.js 22 or later. Unzip the package in a new folder, review its files, then use the commands below. The baseline solves the task deterministically; it is not an AI training job. The exported HTTP environment has process-scoped runs, unlike the persistent hosted service.
node runner.mjs
node runner.mjs decisions.json
node server.mjs
# Open http://127.0.0.1:4360 (GYV_PORT changes the port)Specification hash and package hash differ
The specification SHA-256 identifies the canonical task configuration. The published package hash identifies the entire ZIP, including runtime and licence bytes. Market registration binds the exact published asset hash. Do not substitute a spec hash when a package hash is required.
Evaluation is not commercial ownership
The bundled licence permits private execution to evaluate the exact world. It does not grant republishing, commercial sublicensing or exclusive rights. Downloading the ZIP or holding a token does not transfer copyright.
A commercial acquisition needs a separately executed rights assignment and delivery. The named custodian attests delivery, and the buyer accepts it onchain. A hash records that attestation; it cannot prove that legal title is valid.
Examples explain the implemented mechanics. Live market status belongs to the individual world. No guaranteed buyer, yield or training improvement.