Glossopoeia. Research

Field Notes

№ 006 TARN

Hitting the limits of frontier reasoning

After every batch of specification edits, I have Claude run a bunch of checks on the specification itself, decision record, and the supporting conformance files. Lately, these have begun to run into [reasoning_extraction] blockages. I’ve had to downgrade the subagents to Sonnet 5, which apparently doesn’t have much reasoning to extract? The same prompts that succeed with Sonnet 5 are blocked by both Opus and Fable.

№ 005 TARN

Frontier models still write awfully

Claude Fable 5 has been assisting in the writing, editing, and formalization aspects of the TARN file format specification draft. And while it is unquestionably thorough and fast in finding edge cases that would take me much longer to find, the quality of its writing is still awful. Editing AI-generated technical prose is half reading, half scratching your head wondering what the heck it’s trying to say.

It doesn’t do a bad job of explaining itself in plain terms when prompted. The question then is, why didn’t it say it that way first? Maybe it’s user error on my part.

№ 004 Flatsphere

Exporting a map at a different size

A map that fits a wide browser window may need a different frame on a portrait page. When you change the export dimensions, Flatsphere renders a preview at that aspect ratio so you can see how the map will be framed before you save it. The map in the main window stays where you left it.

№ 003 Flatsphere

What Flatsphere stopped doing at startup

We used to compile and load n² shaders when Flatsphere opened, even if you only wanted to look at one map. As we added more projections, the load time became crippling. So now, we compile a pair the first time you use it and cache the result. You might wait a little when you try a new pair, but switching back will reuse the work, and the initial page load is much more responsive.

№ 002 Flatsphere

One shader for each pair of projections

Reprojecting an image takes two pieces of math: 1) a destination transform tells us where an output pixel draws from the sphere and 2) a source projection tells us where to sample the original image. We compile a shader for each pair, which removes two branches from the per-pixel code. But, it also means that with n projections, we now build n² shaders!

№ 001 Flatsphere

Why Flatsphere uses WESL

Every projection has its own math, but much of the shader code around it is shared. We use WESL so those shaders can import the same helper code. When a helper needs a fix, we can make it in one place. Otherwise, we’d have one copy of all that code for each projection shader!