lumbridge-public/tera

Archived

Fork 0

Commit Graph

Author	SHA1	Message	Date
karti	06455f7424	The office learns where it stands, and the sky stops being a backdrop Aircraft actually move now, and the reason they did not is the headline. `HttpFlights` holds a frozen snapshot between network refreshes and is polled at 1 Hz, so a live feed handed the layer the same position five to fifteen times and then jumped. `span` therefore measured the poll interval rather than the gap between the two positions that differ, the teleport test saw an airliner covering 36 units in a "second" against a ceiling of 8, and every live track's history was wiped on every refresh — so no aircraft on the deployed site could ever grow a trail, however long TRAIL_POINTS was set. Skipping the repeat fixes the motion and the trail at once. Trails then go to 72 points / 240 s, which is about seventy seconds of flying. Three more defects in the same file, found while looking: trail truncation dropped the segments nearest the aircraft (leaving a streak with no aeroplane attached), MAX_TRACKS was declared and never enforced, and one missing target deleted its whole trail. The buffer now uploads only what it wrote, rather than 46 MB/s of untouched array. You can get above the constellation. Dome to 1.05 board radii and the orbit to 2.0 spans. Radii, not spans: scene space is centred on the city and the Bay Area board runs forty kilometres down the peninsula, so the furthest corner is 0.94 spans out where the half-diagonal is 0.65 — sized off the half-diagonal the dome sat inside its own city. The far plane goes to 4 spans to stop clipping the sky from off-centre chapters, and `PointsMaterial` defaults `fog: true`, which was quietly dimming the whole constellation with the city's haze. An office can say where it stands. `Office.site` — lat, lng, height above the ground outside, and the compass bearing the pack's −Z points along — and with one it gets the same sun the city does, a sky, and a horizon at `-elevation`. CONTRACT §4 reserved this as "a later refinement"; it is taken up rather than overturned, and `daylight.ts` computes no light of its own. It does the two things a room needs that a map does not: turn the sun into the building's frame, and move the fog outdoors before it greys out the far wall. Two buildings now, and they are deliberately unalike: Lumbridge HQ 188 m up a Transbay tower facing 205°, and Frontier Valley, a startup in a hangar at Alameda Point — one room, 54 x 30 m, nine metres to the trusses, four metres above reclaimed ground. Floor-to-floor in the reference pack is now 16.8 m: the interstitial is ten times a real one, so the space between the slabs is somewhere things can hang. It is frankly not architecture, `PLENUM` is the one number to change, and the file says so. Also fixed, all found by review rather than by looking at the screen: - `sun.shadow.camera.updateProjectionMatrix()` was never called, so three's default ±5 unit box has been in force this whole time and every `shadowExtent` this repo passes — including the city's ±752 — has been silently ignored. - A missing aircraft was kept alive by the new grace period and drawn, so it froze in mid-air at full opacity for 32 s. - Frontier Valley's mezzanine was a `Room`, which carries no height: its slab lay on the concrete, its chairs floated 4.4 m over it, and its balustrade fenced off a patch of ground floor. It is a `Level`. - Overlapping floor slabs z-fought. The format permits overlap and resolves later-first, so `shell.ts` now lifts a slab a hair per earlier slab it overlaps — and by nothing at all in a pack, like the reference office, whose rooms only ever abut. - `switchOffice` bypassed the `entering` guard (leaking a whole scene per double-click) and tore down the old room before knowing the new one would load, with no way back. Known and not fixed: raising MAX_SPAN to 30 s doubles the worst-case re-base snap when a feed's gap shortens. It is bounded, pre-existing in kind, and the fix wants carrying the live head into the next leg. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-08-06 23:30:45 -07:00
Karti Tripathi	fe43077ff8	The same bug the camera had, still live in the default light rig Three loose ends turned into four, because one of them was not a stale comment. `cityDaylight()` closed its fog at 210/460 — numbers tuned when San Francisco's 230-unit board was the only one. Every caller who supplies an `Atmosphere` overrides them, which is why this survived: the demo does, so nothing looked wrong. A self-hoster who renders a city with no clock and no weather gets the default path, and on the Bay Area's 1003 units that fog closes well inside the city. It now scales to the board exactly as the camera limits do, with the old constants preserved as the default for a caller holding a palette but no world. The three that really were comments: socal.ts justified its `latScale` by citing the 340-unit orbit cap and the 460-unit fog as things the engine insisted on, and the engine stopped insisting when both became board-relative — 285 is now a choice the pack makes because its lot sizes and hill radii were authored against it. CONTRACT.md and ARCHITECTURE.md still measured the retention argument against a 336,864-point San Francisco that has been the whole Bay Area for some time. And server/package.json listed five routes where there are six. None of these changed behaviour except the first. All of them would have gone on quietly disagreeing with the pages that now cite them. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-08-05 04:34:00 -07:00
Karti Tripathi	d464459838	Spaces: the inside of the world, and a sun that is actually where it should be 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>	2026-08-05 00:11:01 -07:00

Author

SHA1

Message

Date

karti

06455f7424

The office learns where it stands, and the sky stops being a backdrop

**Aircraft actually move now, and the reason they did not is the headline.**
`HttpFlights` holds a frozen snapshot between network refreshes and is
polled at 1 Hz, so a live feed handed the layer the same position five to
fifteen times and then jumped. `span` therefore measured the poll interval
rather than the gap between the two positions that differ, the teleport
test saw an airliner covering 36 units in a "second" against a ceiling of
8, and **every live track's history was wiped on every refresh** — so no
aircraft on the deployed site could ever grow a trail, however long
TRAIL_POINTS was set. Skipping the repeat fixes the motion and the trail
at once. Trails then go to 72 points / 240 s, which is about seventy
seconds of flying.

Three more defects in the same file, found while looking: trail
truncation dropped the segments nearest the aircraft (leaving a streak
with no aeroplane attached), MAX_TRACKS was declared and never enforced,
and one missing target deleted its whole trail. The buffer now uploads
only what it wrote, rather than 46 MB/s of untouched array.

**You can get above the constellation.** Dome to 1.05 board *radii* and
the orbit to 2.0 spans. Radii, not spans: scene space is centred on the
city and the Bay Area board runs forty kilometres down the peninsula, so
the furthest corner is 0.94 spans out where the half-diagonal is 0.65 —
sized off the half-diagonal the dome sat inside its own city. The far
plane goes to 4 spans to stop clipping the sky from off-centre chapters,
and `PointsMaterial` defaults `fog: true`, which was quietly dimming the
whole constellation with the city's haze.

**An office can say where it stands.** `Office.site` — lat, lng, height
above the ground outside, and the compass bearing the pack's −Z points
along — and with one it gets the same sun the city does, a sky, and a
horizon at `-elevation`. CONTRACT §4 reserved this as "a later
refinement"; it is taken up rather than overturned, and `daylight.ts`
computes no light of its own. It does the two things a room needs that a
map does not: turn the sun into the building's frame, and move the fog
outdoors before it greys out the far wall.

Two buildings now, and they are deliberately unalike: Lumbridge HQ 188 m
up a Transbay tower facing 205°, and **Frontier Valley**, a startup in a
hangar at Alameda Point — one room, 54 x 30 m, nine metres to the
trusses, four metres above reclaimed ground.

Floor-to-floor in the reference pack is now 16.8 m: the interstitial is
ten times a real one, so the space between the slabs is somewhere things
can hang. It is frankly not architecture, `PLENUM` is the one number to
change, and the file says so.

Also fixed, all found by review rather than by looking at the screen:

  - `sun.shadow.camera.updateProjectionMatrix()` was never called, so
    three's default ±5 unit box has been in force this whole time and
    every `shadowExtent` this repo passes — including the city's ±752 —
    has been silently ignored.
  - A missing aircraft was kept alive by the new grace period and *drawn*,
    so it froze in mid-air at full opacity for 32 s.
  - Frontier Valley's mezzanine was a `Room`, which carries no height: its
    slab lay on the concrete, its chairs floated 4.4 m over it, and its
    balustrade fenced off a patch of ground floor. It is a `Level`.
  - Overlapping floor slabs z-fought. The format permits overlap and
    resolves later-first, so `shell.ts` now lifts a slab a hair per
    earlier slab it overlaps — and by nothing at all in a pack, like the
    reference office, whose rooms only ever abut.
  - `switchOffice` bypassed the `entering` guard (leaking a whole scene
    per double-click) and tore down the old room before knowing the new
    one would load, with no way back.

Known and not fixed: raising MAX_SPAN to 30 s doubles the worst-case
re-base snap when a feed's gap shortens. It is bounded, pre-existing in
kind, and the fix wants carrying the live head into the next leg.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

2026-08-06 23:30:45 -07:00

Karti Tripathi

fe43077ff8

The same bug the camera had, still live in the default light rig

Three loose ends turned into four, because one of them was not a stale comment.

`cityDaylight()` closed its fog at 210/460 — numbers tuned when San Francisco's
230-unit board was the only one. Every caller who supplies an `Atmosphere`
overrides them, which is why this survived: the demo does, so nothing looked
wrong. A self-hoster who renders a city with no clock and no weather gets the
default path, and on the Bay Area's 1003 units that fog closes well inside the
city. It now scales to the board exactly as the camera limits do, with the old
constants preserved as the default for a caller holding a palette but no world.

The three that really were comments: socal.ts justified its `latScale` by
citing the 340-unit orbit cap and the 460-unit fog as things the engine
insisted on, and the engine stopped insisting when both became board-relative —
285 is now a choice the pack makes because its lot sizes and hill radii were
authored against it. CONTRACT.md and ARCHITECTURE.md still measured the
retention argument against a 336,864-point San Francisco that has been the
whole Bay Area for some time. And server/package.json listed five routes where
there are six.

None of these changed behaviour except the first. All of them would have gone
on quietly disagreeing with the pages that now cite them.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

2026-08-05 04:34:00 -07:00

Karti Tripathi

d464459838

Spaces: the inside of the world, and a sun that is actually where it should be

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>

2026-08-05 00:11:01 -07:00

3 Commits