Case study
TERRA: one engine that compiles a lesson into a console that runs offline.
TERRA is the other end of Aesir's build range from ClassFoundry. Where ClassFoundry is a full multi-user platform, TERRA is a single-purpose interactive tool that compiles to one file and runs offline on any machine. It is a working tool Aesir's founder built and uses to teach geography and world history, and it shows the four-week cycle produces bespoke offline tools as readily as web platforms.
I. What it is
A lesson becomes a narrated 3D console.
TERRA takes a geography or history lesson and builds it into one interactive console: a 3D globe under a glass interface, narration baked in, running from a single local file so a shaky connection cannot break it. This is the path from a lesson to a live console.
- Author the lesson as a typed config file: these coordinates, this curve, this cross-section, narrated in this order.
- The engine assembles the console from a fixed set of module types. No screen is hand-coded.
- The build compiles to one self-contained file that runs offline, carrying only that lesson's content and its answers.
- In class, the teacher drives the console live and narrates each answer on cue.
Physical geography and world history are the hard subjects to make land. Why the great deserts line up near 30 degrees. How a canyon takes millions of years to cut. Read off a static slide, this material goes quiet in about ninety seconds, at any age. TERRA exists to carry the one idea a static image cannot, and to do it without hand-building a throwaway app for every lesson.
II. The reframe
One engine, and every lesson is a config file.
The core decision was to stop building a new application per lesson and write one engine instead. A lesson is now a typed config file and its data. The config names modules from a fixed set of archetypes, hands each one its data and its guiding question, and the engine assembles the console.
Authoring a new lesson means writing that config and supplying the facts, work that folds into the same textbook-to-lesson pipeline Aesir already runs with its build agents. The interactive now rides on prep already being done. That is what keeps a new console on a weekly cadence instead of a per-lesson rebuild.
III. The building blocks
Three module types do the work of thirty screens.
The engine ships three archetypes, and almost every lesson is an arrangement of them. Because they are types and not one-offs, a new lesson reaches for them the way a builder reaches for parts on a shelf.
The scrub timeline running the Grand Canyon is the clearest example: the number climbs through the millions of years it took the river to cut the rock, and the class watches deep time turn into something they can point at.
IV. How it's built
A config-driven engine that compiles to one offline file.
- Rendering. Three.js and WebGL for the 3D globe and its overlays.
- Engine. TypeScript, with a fixed library of module archetypes assembled from typed config.
- Build. Each console compiles to one self-contained file with everything inlined, so it opens straight from disk with no server and no network calls, and it carries only its own lesson, never a sibling's.
- Authoring. An agent-assisted pipeline extracts the fact base from the source and shapes it into config. A person owns the architecture, the interaction model, and every call about what a student sees.
The authoring path is the same one that produces Aesir's other builds: agents draft and extend under direction, and a person holds the design and the interaction. The result compiles down to a single file a teacher double-clicks.
V. The hard part
The answer never reaches the screen early.
TERRA runs live on a shared screen for the whole class. If an answer renders into the page before the teacher asks for it, the lesson is over. So the engine enforces that seal as a hard rule, down in the build where it cannot be forgotten.
The panels are built to be question-only. The answer lives in the narration, and narration fires on one explicit press. Leave a module and come back, and it re-seals: the history stays, the payoff hides again, every time. The rule is testable, so it holds standing in front of students rather than by hope.
VI. For a prime or a district
The same capability builds your bespoke tools.
TERRA is the kind of build a platform like ClassFoundry does not cover: a single-purpose interactive tool, offline-capable, built on the four-week cycle. The same engine and pipeline produce training simulators, field tools that run without a connection, custom data consoles, and interactive briefings. The operating model is the same one behind ClassFoundry: a working tool inside a performance period or a pilot window, built and revised on a weekly cadence, authored through the same agent-assisted pipeline. Aesir works under your methodology and your contract.
VII. Contact
See whether this fits your next pilot or performance period.
A 30-minute call is the right first step. We'll talk through what's on the calendar and whether a four-week build is worth scoping.
Book a 30-minute call
Book a 30-minute call.Scan to reach the calendar at calendly.com, or email corey [at] aesir-ind [dot] com.
Phone: