tera-spatial: an NDJSON replay bridge to the TypeScript spatial environments

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>

This commit is contained in:

karti

2026-08-21 15:55:12 -07:00

co-authored by

Claude Opus 5

parent 00d21025ff

commit 162d67a83c

33 changed files with 9030 additions and 0 deletions

									
										environments/tera_spatial/tests/__init__.py
									
		+1
		
												View File
												
				@@ -0,0 +1 @@

				"""Tests for tera-spatial."""

				`@@ -0,0 +1 @@`
				`"""Tests for tera-spatial."""`