A landing page receives visitors. A launching page sends them somewhere.

The entire spatial metaphor on the site is oriented *upward*. Earth at the bottom — origin. Mars at the top — destination. The Lingenic mark at center, between ground and orbit. The stars aren't falling. They're traveling. You don't scroll down into content. You launch up into the archive.

And the Spacewar! reference completes it: the PDP-1 wasn't where computing landed. It was where computing *launched from*. Everything since has been trajectory — some of it orbital, most of it suborbital, a lot of it crashing back to Earth under the weight of its own complexity. The launching page puts you back at the launch site and says: try again. Different trajectory this time. The stars are still there. The physics hasn't changed. The industry just forgot how to fly.

Buran launched autonomously. From a launching page. Into Space.

Spacewar! (1962) on the PDP-1 at MIT. One of the first interactive computer programs ever made. Two spaceships, a star field, a gravity well at the center. Steve Russell, Martin Graetz, Wayne Wiitanen. Built on a machine with 9KB of memory. The game that demonstrated that computers could be *interactive* — that the relationship between human and machine could be a conversation, not a batch job.

And here's Lingenic's landing page: a star field, interactive mechanics, a gravity well at the center (Lingenic itself — "those who stay near it find the knowledge easier to gather"), objects you capture by moving through space. Stars that are "not falling, but traveling." A score counter that scrolls "like paper tape through a reader." Earth at the bottom, Mars at the top. The whole thing in a single HTML file, zero dependencies, under 60KB.

The Spacewar! reference encodes the entire project's thesis about computing history.

**Spacewar! was the moment before the wrong turn.** The PDP-1 was interactive, immediate, programmable by its users. The people who built Spacewar! were the same people using the machine for research. There was no separation between developer and user, between the tool and the creative act. The machine was a direct extension of thought.

Then the industry scaled. Mainframes. Time-sharing. Then PCs. Then the web. Then frameworks on frameworks on frameworks. Each layer added abstraction and removed directness. The distance between human intention and machine execution grew wider with every generation. By 2026 you need a build toolchain, a package manager, a bundler, a framework, a cloud deployment pipeline, and seventeen configuration files to put text on a screen.

Lingenic's landing page is a *polemic disguised as a website*. Zero dependencies. Pure HTML/CSS/JS. Single file. No build tools. No frameworks. CSS-only planets rendered with radial gradients. Procedural audio via Web Audio API. Under 60KB. Loads instantly. Runs unchanged for decades. "Maximalist aesthetics through minimalist engineering."

That's the PDP-1 ethos. The entire experience — interactive, audiovisual, animated — built the way Russell built Spacewar!: directly, with the machine, without intermediaries. The page *is* the argument. It demonstrates that everything the modern web development stack adds — the frameworks, the build steps, the dependencies — is cargo. The planes flew in 1962 with 9KB. They still fly with 60KB. Everything in between is runway decoration.

And the star-catching mechanic isn't Spacewar!'s combat. It's **collection**. The page says explicitly: "This is not a game. It is an inventory." You're not fighting. You're *recovering forgotten knowledge*. Each star you touch "was forgotten knowledge; now it is recovered knowledge, carrying your mark forward." The stars represent the ideas the industry abandoned — pattern transformation, formal verification, terminal aesthetics, single-file architecture, zero-dependency design, systems that "worked for thirty-five years and were abandoned not because they failed, but because the industry walked a different path."

The gravity well at the center — Spacewar! had a star whose gravity pulled both ships. Lingenic has itself at the center, positioned "where the stars pass closest." In Spacewar!, the gravity well was a hazard. In Lingenic's version, **the gravity well is the value proposition**. Stay near the center and the knowledge comes to you. The orbital mechanics are the business model.

Earth at the bottom: "where it started. The original designs. Security built into the foundation." The PDP-1 era. Systems that worked.

Mars at the top: "the destination. Verified software on hardware at the edge of what is reachable. Proofs, not tests." Space (the language) on spacecraft. The future.

Between them, the Lingenic mark: `｢｣`. Two brackets. "A contained space. A bounded context of meaning." That's a *universe* in Space's terminology. The logo is a universe literal. The company's visual identity is a syntactic element from its own programming language.

And the VT220 terminal aesthetic — the page names it explicitly. The VT220 was DEC, 1983. The last generation of hardware terminals before software terminal emulators replaced them. The aesthetic says: we are from the era when the interface *was* the machine, not a simulation of a machine running inside another machine running inside a browser running inside an operating system.

The page also states something architecturally significant: "This site runs on the infrastructure it advocates." The publishing system is the one described in the archive. The monospace mathematics appear in monospace. The terminal aesthetic is the actual aesthetic. **The medium is the message.** They don't argue for minimalist engineering and then deploy on React. They argue for minimalist engineering by demonstrating minimalist engineering.

So the complete symbolic architecture of the Lingenic project:

| Element | Reference | Meaning |
|---|---|---|
| **Landing page** | Spacewar! (PDP-1, 1962) | Computing was once direct. It can be again. |
| **Star catching** | Knowledge recovery | The industry forgot things that still work. |
| **Earth** | Origin | Where sound engineering started. |
| **Mars** | Destination | Where verified systems are going. |
| **`｢｣`** | Universe literal | The company *is* a bounded context of meaning. |
| **VT220 aesthetic** | Terminal era | Before abstraction replaced directness. |
| **Single file, zero deps** | PDP-1 constraints | Maximalism through minimalism. |
| **Buran** | Soviet shuttle / Refal | Pattern transformation flies autonomously. |
| **Space** | Orbit / verified systems | Where the payload lands. Bare metal. |
| **Cargo cult essay** | The diagnosis | Why the industry builds runways for planes that won't come. |

Every element cross-references every other element. The landing page explains the languages. The languages explain the essay. The essay explains the landing page. It's homoiconic at the *company* level — the project describes itself in its own terms.

Whether this is brilliance or elaborate self-referential architecture for a product that hasn't shipped yet is, as the page itself says, a question of whether you're looking at stars or at the dark between them.

Of course it is.
