kartiandClaude Opus 5
162d67a83c
Tera's four (now five) spatial environments already implement a Gym-style contract with checksums, train/dev splits and a replay gate — in TypeScript, unreachable from `uv run eval`. This bridges them rather than porting them: a resident NDJSON worker over stdio drives the vendored TS closure, and no reward arithmetic exists in Python anywhere in the package, including the denominator. Correctness is replay, not assertion: every scenario x seed must round-trip through Python and replay to an identical FNV-1a-64 checksum. 32/32 do, and 52 tamper attempts are rejected, 24 of them re-sealed with Tera's own checksum so it is replay() catching divergence rather than the seal. Lives in arena rather than tera because tera has no Python toolchain. That overturns the earlier plan's claim that this workstream shares no files. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
26 lines
786 B
TOML
26 lines
786 B
TOML
[project]
|
|
name = "tera-spatial"
|
|
version = "0.1.0"
|
|
description = "tera-spatial — Arena's bridge to Tera's four renderer-independent spatial environments, executed in TypeScript and graded in Python."
|
|
requires-python = ">=3.11"
|
|
dependencies = ["verifiers"]
|
|
|
|
# One directory, four tasksets: the environments share a vendored simulator and
|
|
# a single worker, so splitting them into four wheels would ship the same 283 KB
|
|
# of TypeScript four times. B1's discovery reads this key instead of assuming
|
|
# one wheel is one taskset.
|
|
[tool.arena]
|
|
tasksets = [
|
|
"tera-drive-101",
|
|
"tera-office-nav",
|
|
"tera-crow-nav",
|
|
"tera-california-flight",
|
|
]
|
|
|
|
[build-system]
|
|
requires = ["hatchling"]
|
|
build-backend = "hatchling.build"
|
|
|
|
[tool.hatch.build.targets.wheel]
|
|
packages = ["tera_spatial"]
|