Universe Index

An app that takes one changed fact and builds an encyclopedia of the alternate history that follows, with articles, timelines, and generated images.

Date
April 2026
Built with
Next.js, React, TypeScript, SQLite, OpenRouter, fal.ai
Universe Index archive index showing freshly generated Aerial Commons and Tidal Republics universes with generated artifact imagery.

Universe Index starts with one changed fact and builds an alternate history around it, written up as an encyclopedia. From that premise the app works out what else would be true in the new world, builds a timeline, and writes article pages about the people, places, and organizations in it, with generated images. The facts it settles on become the universe's canon. Pages link to pages that haven't been written yet, the way red links work on Wikipedia, and every page keeps its revision history. The pages are meant to read as if you found them, not as if they were written for you a second ago.

I'm interested in using language models to make media you can explore. So far that means encyclopedia entries, timelines, and generated images. Eventually a universe might also have its own music, fake albums, radio stations, documentary clips, maps, and posters. A different history should produce a different culture.

Universe Index archive index showing newly generated alternate-history universes, recent activity, and a featured card from the Tidal Republics universe with a generated image.
The home page of the local prototype: a Reddit-style feed of newly generated universes, each of which opens into a Wikipedia-style archive.

How a universe grows

You type in a changed fact and the app builds an encyclopedia for that timeline. A universe starts with a handful of pages and grows from there. You can have it research and write up a red link, update the pages a new fact affects, add generated images, fork the timeline into a branch, or review proposed changes before they go in. Each of these runs as a queued simulation job.

There's no chat box. You use it the way you'd use Wikipedia: read pages, follow links, browse categories and timelines, and check a page's history and the canon behind it. Controls on the pages let you decide where the simulation goes next.

Because everything is saved, a universe can collect more than text. A political movement might build up posters and speeches, a city might get maps and transit diagrams, and a fictional music scene might get artists, album covers, interviews, and eventually its own sound. Whatever gets generated stays in the archive.

Aerial Commons universe overview showing generated articles, controls for expanding the universe, and a snapshot image made with GPT Image 2.
The Aerial Commons universe: an Expand button with its estimated cost, a list of articles still to write, a featured article, and a generated snapshot image with its prompt.

One run, start to finish

These are screenshots of the working app, not concept art. They follow one real run on my machine, starting from a premise about municipal dream archives. The app reads the premise, writes a set of rules for the new universe, and stops for review. Once the rules are accepted, it writes the pages and generates the images.

Universe Index create form filled with a municipal dream archives premise while the app is rendering the new universe.
Typing in the premise and picking a quality setting: Fast, Balanced, or Studio.
Universe Index progress screen showing the Interpreting step, OpenRouter as the provider, the budget, and a running log of model calls.
The first step running, with the model provider, the budget spent so far, a log of model calls, and a timer.
Universe Index review screen showing the app's reading of the premise, the rules for the universe, the build plan, and an outline of causes and effects.
Before writing any pages, the app stops to show how it read the premise, the rules it set, the chain of causes it plans to follow, and an estimate of pages and cost.
Universe Index completed dream archive universe showing generated pages, the job queue, and several generated images.
After the plan is accepted: the new universe's home page, with generated images for its first articles and a button to queue another pass.
Universe Index generated article for Library of Congress v. Somnium Corp with wiki sections, infobox metadata, and a generated archive image.
One of the generated articles, “Library of Congress v. Somnium Corp,” laid out like a Wikipedia page with an infobox and a generated image.

Building it with Codex and Claude

I decide the premise, the rules the simulation follows, and how the app should feel. Codex and Claude do much of the coding, debugging, and architecture. That's how I can work on something this large and still make the small decisions that keep each archive consistent.

This project suits working with agents, because one change can touch the interface, the database, the job queue, the prompts, the simulation rules, image generation, exports, and several small interface decisions at once. My loop is simple: I describe the next thing it should do, an agent writes the change, I run the app, look at what came out strange, and correct course. Codex handles the longer stretches of work in the codebase, like database migrations, tests, type errors, queue behavior, and changes across many files. Claude is more useful for critiquing the product, simplifying the interface, and suggesting other ways to structure the code. Together they work like a small team that I direct.

I don't write every line by hand. I keep the premise weird and make the calls on taste.

Where it's going

Eventually I want it to be an encyclopedia simulator that could cover everything in a universe. It wouldn't write all of Wikipedia up front, but every possible page would have a link and could be written when someone asks for it. A small universe might have 25 pages; a deeper run might have hundreds or thousands. Once a page is written it is saved as part of the canon, and you can check it, revise it, fork it, dispute it, or expand it.

I want the same system to handle text, images, music, video, and anything else that makes a timeline feel lived in. Everything the models make goes into the archive and adds up to one consistent world.

This is also how I like to learn: build the thing, keep pushing it until it gets interesting, and make the next version stranger and more capable.

Next on Systems

All systems
  1. 2026How I Use CodexThe skills and routines I use when working with Codex
  2. 2026Think DeeperA skill that pushes Codex and Claude past their first answer
  3. 2025SlopTokA video app where bots made every clip9,000 clips

Contact

elliotbquartz@gmail.com

For commissions and collaborations.