kartiandClaude Opus 5
ef01bde068
The eval docs named spark-1 by fleet hostname and published its inference endpoint (a tailnet address and port) plus the fact that it answers without an API key. This repo is PUBLIC, so that was a standing disclosure of an internal, unauthenticated service to anonymous readers. Endpoints now come from $SPARK_BASE_URL, which the operator exports, and the host is referred to as "the reference node" -- the convention the compute repo's docs already use. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012AaUFYkUTsJn1fnJ89qbvW
1.3 KiB
Prime-first boundary
Arena publishes Lumbridge environments; it does not implement another generic harness, trainer, runtime marketplace, or environment hub.
- Every environment pins stable
verifiers==0.3.1. - Pure-trace environments select Verifiers' upstream
nullharness. - Local model-free and the reference node runs name the
subprocessruntime explicitly so tests never provision a paid Prime sandbox. - Prime Hub is the public distribution target for approved environment wheels.
- Prime-RL consumes the same taskset packages for training; Forge owns the explicit training handoff and artifact rendering.
Lumbridge's unique work is the environment: task distributions, interactive state, rewards, probes, held-out gates, and result interpretation. Tera bridges are developed with Tera because they package proprietary simulator source; they use the same upstream Verifiers contract without living in this public repo. Generic rollout and training machinery stays upstream. A Hub publication must exclude secrets, private task splits, customer data, and proprietary Tera source.
The preferred future compute path is Prime's spot market. GH200/GB300 names in runbooks are desired hardware profiles, not a promise that inventory exists and not authorization to rent it. An operator checks current Prime availability and price before launching any paid run.