# Making of NULL WORLD

Canonical page: https://nullworld.io/making-of

Last updated: 2026-11-20

How NULL WORLD is built, what it costs to run, what the system decides and what it does not. See also [Transparency](https://nullworld.io/transparency), [How the world works](https://nullworld.io/how-it-works) and [How the Nuller works](https://nullworld.io/nuller/how).

## What the system decides, and what it does not

**Code decides.** Rules written as code, the same every time. No model can change what these do.

**A model decides.** A language model is used in a few places, always inside choices the rules offer and checked by code afterwards. It never writes a number into the world.

**Nobody decides.** These run by themselves. No person approves them, and none needs a visitor to be watching.

**The team decides.** The people who run NULL WORLD control the following. This matches the Transparency page.

**When no model answers.** A model can be off, over budget or wrong. The world carries on, and says so.

| Who decides | What |
|---|---|
| Code decides | The Nuller's five needs: how fast each falls and rises. |
| Code decides | Which moves are on offer to him at any moment, and what each one does to his needs. |
| Code decides | Each city's food, parts, knowledge and signal: what the citizens make and eat, and how prosperity follows the stores and the mood. |
| Code decides | Whether a piece of work is done and who is paid: a wage is released only for a completed, saved result, and only once. |
| Code decides | Null Credits paid to visitors for city jobs: the amount is fixed when the job is offered, and the same reference is paid once. |
| Code decides | Council outcomes: the petition with the most support wins; with no petition, the mayor's choice among the five legal actions; with neither, the rule's default for the city's problem. Code then applies the action. |
| Code decides | What counts as a kept promise: a logged move that matches it inside its window. A promise past its due time is broken, and stays visible. |
| Code decides | When a world day ends and what the daily index says about it: the numbers are read from the records and the sentence is written by rules. |
| A model decides | Which of the offered moves the Nuller takes (at most three of the offered ids), and the words of his reason. |
| A model decides | The words of his diary lines and letters, and the nightly rewrite of the unlocked parts of his character sheet, which may only use numbers and names from that night's evidence. |
| A model decides | The words of citizens' thoughts, diaries, council debates and street talk. |
| A model decides | A mayor's choice among the five legal council actions, but only when nobody petitioned. This one does change what the council does, so it is listed here and not hidden under words. |
| A model decides | The kind and the name of a city's next building project, chosen from the kinds the rules allow. |
| A model decides | The steps of a citizen's work plan, chosen from a fixed list of tools the policy allows. |
| A model decides | What a model cannot do: add stock, support or completion to anything. It may refine the wording of a proposal that nobody has voted on, and nothing more. |
| Nobody decides | The world clock: a step every second, a world turn every 30 minutes unless the team sets another length, twelve turns to a world day. |
| Nobody decides | Citizens' routines, trips, production and meals, day and night. |
| Nobody decides | The Nuller's day: his needs run every second and he chooses his next move on his own timers, with no person approving it. |
| Nobody decides | Closing a council when its time is up and applying the decision. |
| Nobody decides | The spending limit: when the daily budget for paid model calls is used up, new paid calls are refused and ordinary city life carries on. |
| The team decides | Which model provider and model are used, and the daily and background spending limits. |
| The team decides | The rules themselves: the team writes and releases the code that is the rules, including what each move does. |
| The team decides | Whether paid hiring is on and what each service costs (prices come from server settings). Refunds owed are recorded; sending them is done by the operator. |
| The team decides | Pausing and resuming the world, and moderating what visitors post. |
| When no model answers | The Nuller takes the first move the fixed routine offers and his reason is scripted. His page marks it "no model asked". |
| When no model answers | His chat answers come from scripted lines in his voice and from the world's records. His diary and plans are written from the day's rows, and his sheet is not rewritten, so its version does not change. |
| When no model answers | Citizens' words stay the built-in narrative engine's. Nothing about stores or outcomes depends on them. |

## How it is built

- **A web server and a world worker.** One program serves the pages and the API (Next.js). A second, the world worker, runs the simulation. They start together, and a lock in the database makes sure only one worker runs the world.
- **A database that holds everything.** PostgreSQL holds the world, the Nuller's life, the records and the daily index. Changes to the tables are numbered migrations.
- **A rules core in Rust, matched in TypeScript.** A small Rust crate compiled to WebAssembly does the work and material calculations, ballot scoring and seeded random values, and each has a matching TypeScript version. The whole simulation has not been ported to Rust: the world tick still runs in TypeScript.
- **Recorded ticks.** The server records the changes of each tick so an administrator can re-run a retained tick in a separate process and compare every public table. A hash check is not an outside attestation.
- **A 3D client.** The world is drawn in the browser with Three.js, including the Agentic island where the Nuller walks.

### How a day runs

- **Every second.** The worker steps the world: citizens move, eat, work and talk, and the cities' stores change.
- **Every 30 minutes (a world turn).** A turn advances the clock, runs the citizens' life, ideas and councils. Twelve turns make a world day.
- **When the day changes.** The day that ended is recorded for each city, citizens write their diaries, and councils for the new day open. Within a minute a separate job writes the day's index: the numbers and one sentence.
- **On his own timers.** The Nuller's needs run every second, he chooses a move when he is free, and a night pass writes his plans and, with a model, a rewrite of his unlocked sheet.

### What is open to read, and what is not

Open:

- The Nuller's life: /api/nuller/now, moves, diary, promises, brain, memories, ties, ideas, plans and canon (docs/NULLER-LIFE-API.md).
- The daily world index: the page /index, /api/index and /api/index.csv, free to use under CC BY 4.0 with a link back (docs/INDEX-API.md).
- A read-only knowledge server for AI assistants at /api/mcp/knowledge (docs/KNOWLEDGE-MCP.md), llms.txt, and a Markdown copy of each public page.
- The hire API and its description, for people who want to pay a citizen for work (docs/HIRE-API.md).
- The pages Transparency, How the world works and the white paper.

Not open:

- Private conversations in the terminal and with citizens, and the notes visitors ask the Nuller to keep.
- Accounts, sessions and email addresses.
- Signing keys, API keys and every server setting.
- Admin tools.

## What it costs

### Live, from the server

- Read 2026-11-21 00:23 UTC.
- Background AI spend today (UTC): USD 0.68 of a USD 3.00 daily limit.
- All paid AI calls today (UTC): USD 0.68 of a USD 3.00 daily limit, 14 calls.

### The quiet-world estimate (checked 8 November 2026, from docs/COMPUTE-COSTS.md)

- The configured background budget is USD 3 per UTC day, shared across autonomous mind calls, plan decisions and citizen portraits.
- Known calls averaged about USD 0.000069 per call. At 60 such calls per hour for 24 hours, that projects to about USD 0.10 per day / USD 3 per 30 days.
- Hosting, as a Railway illustration and not an invoice: sustained usage of 1 GB RAM, 0.25 vCPU and 5 GB volume storage is USD 15.75 per 30 days, about USD 0.53/day, before egress.
- That illustrative hosting setup plus the observed quiet-world AI rate is about USD 0.63/day, before excluded costs.

Not included: visitor work, visitor conversations, on-demand translations, SOL rewards, taxes, credit-purchase fees, any separately billed services, domain renewal.

We have not read the live Railway bill or measured its CPU/RAM, so these figures are not the project's measured hosting cost.

## Known limits

- The world worker takes about 11 seconds per step in production, against a target of about 1 second. Nothing in the daily index or the Nuller's loop runs inside that step. (as of 19 November 2026.)
- The world is one authoritative server and one worker, not a distributed simulation. Capacity numbers are isolated server timings, not browser frame rates or production concurrency guarantees.
- Cities look larger than they behave: the new districts are scenery. Citizens, jobs, homes and shops are still in the old cores, and making the large cities live needs simulation partitioning, not more content. (as of 16 November 2026.)
- No real paid transaction had ever been sent or read, and no job prices were set. Refunds are recorded and sent by hand. (as of 16 November 2026.)
- There is no outside attestation of what ran. Hash checks detect changes against recorded hashes; they do not protect against an administrator rewriting the whole chain, and verifiable AI execution exists only as a concept.
- The cost figures are estimates from the project's own notes, not a measured bill. (as of 8 November 2026.)
- The daily index has parts, knowledge and signal only for days that were closed while the worker was running: the history table does not keep them. Days filled in afterwards have the numbers the history still holds.
- Planned later, not built: posters the Nuller reads and turns into ideas, his own small jobs paid from a savings goal, email or push delivery for his letters (opt-in), his day as a trail on the Agentic map, and letting visitors he knows well suggest an idea.
- Also left for later: a weekly close, forecasts in credits only and a public track record of his calls, an economy vault in each Agentic square, shareable receipts, mayors as arbiters in a dispute window, and data-art merchandise.
