Karti Tripathi
d464459838
Ten agents wrote this in parallel against CONTRACT.md, which exists because the five design agents before them collided on fifteen blocking points — four files specified twice with incompatible contents, three separate backends for one box, and `Environment` exported twice meaning different things. What landed: a Stage owning only the renderer and the loop, with the city and an office as two scenes over it. They cannot share one — San Francisco is ~94 m per scene unit with 3.6x vertical exaggeration and an office is 1 unit = 1 m — and the city is paused rather than disposed on the way in, because rebuilding its 336,864-point heightfield costs about a second on the way back out. Offices are data. `src/offices/lumbridge-hq.ts` is fifteen rooms and seventy-six seats, and it is the file a self-hoster copies. Walls are a segment list with 1-D openings, so doors and windows are holes punched in a wall rather than placed objects, and the pass that splits a wall around its openings hands the walk-mode collider its segments for free. The sun is real. `solar.ts` is a NOAA/Meeus implementation with no imports at all — not even three.js — so time of day keeps working on a laptop in a field. Verified against known values: 75.45 degrees at the June solstice in SF, 28.79 at December, sunset at 03:15Z. The first screenshot after wiring it was a black rectangle, which turned out to be correct: it was midnight in San Francisco. Presence binds to a seat id and never to a coordinate. The pack knows where `eng-04` is; who is sitting in it is private data behind an API. Same shape as the marker rule, one level in. Two corrections to ARCHITECTURE.md are in here. Containment does not discharge ODbL — publishing OSM-derived coordinates is Public Use of a Derivative Database wherever the rows live, so the rule is about the geocoder (US Census, public domain) and not the storage. And a person at a desk is not a Marker; markers are geographic. One contract gap surfaced only in a screenshot: two agents read `height` on a viewpoint differently, so the establishing shot aimed at empty air fourteen metres above the roof. It now means what the same field means for a city. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
43 lines
1.3 KiB
Caddyfile
43 lines
1.3 KiB
Caddyfile
# The one Caddy snippet.
|
|
#
|
|
# Three server designs each brought their own, on three different ports, and all
|
|
# three wrote to this filename. This is the one that replaced them: one service,
|
|
# one port, one prefix. CONTRACT.md §5.
|
|
#
|
|
# Install it beside your Caddyfile and import it into whichever site serves the
|
|
# Tera browser build:
|
|
#
|
|
# import /etc/caddy/snippets/tera-api.snippet
|
|
#
|
|
# tera.lumbridgecorp.com {
|
|
# import tera_api
|
|
# root * /srv/tera/dist
|
|
# file_server
|
|
# }
|
|
#
|
|
# The API and the static build are deliberately the same origin. Nothing here
|
|
# needs CORS, which is why TERA_CORS_ORIGIN defaults to empty — set it only for
|
|
# a Vite dev server on another port.
|
|
|
|
(tera_api) {
|
|
handle /api/v1/* {
|
|
reverse_proxy 127.0.0.1:8431 {
|
|
# Fail fast rather than holding a browser connection open while the
|
|
# API is restarting. systemd brings it back in under two seconds.
|
|
transport http {
|
|
dial_timeout 2s
|
|
}
|
|
}
|
|
}
|
|
|
|
# The API stamps its own Cache-Control — `private, no-store` by default, and
|
|
# `public, max-age=…` only where a route opted in. Do not add a cache
|
|
# directive here: this file cannot tell which route answered, and the
|
|
# fail-closed policy is only fail-closed if nothing downstream overrides it.
|
|
|
|
header {
|
|
X-Content-Type-Options nosniff
|
|
Referrer-Policy strict-origin-when-cross-origin
|
|
}
|
|
}
|