Every part

Every part of both twins.

A twin is built from small pieces. Each has a name, a job and a file.

Copernicus Sentinel-2, 13 July 2026 · sources

What counts as a part

One job, one name, one file.

A digital twin is a working model of a real place, built from what the place publishes. Each piece does one job. There are five kinds.

  • A system runs every tick. A tick is ten island minutes in the first build. The tide, the koalas, the ferry and the council are systems.
  • A layer draws. Ground, sea, trees, people, rain. It changes nothing.
  • A board is read. The opening noticeboard, the civic board, the panel that fills with detail when you click.
  • A pack holds data. Records that name their source: businesses, timetables, Acts of Parliament.
  • A checker says pass or fail. You run it in a terminal, the plain text window on a computer.
First build opening screen. An acknowledgement panel and a list of what the project will not do, over a dark island.
First build, 2 September 2026. The camera bar (Planner, Street, Follow, Drone, Cinematic, four bookmarks, Photo) is one part.
0
running, first build
parts list
0
running, second build
parts list
0
partly there, both builds
parts list
0
designed, not yet written
parts list

Sixteen areas

Each part belongs to one area.

The first build fills eleven areas. The second fills six. Both share world and data. Folder names come from the code. "agents" is called people here.

AreaBuildWhat lives there
worldfirst secondFirst build: the ground. A height reading every 32 metres, how the round Earth is flattened onto a map, land cover, named regions. Second build: the store that keeps two dates on every fact, and the ladder of sources that answers or says "not known".
environmentfirstTide, daylight and weather run. Fire, coast and groundwater are designed, not written.
ecologyfirstVegetation, koalas, whales, shorebirds, marine life, dunes, lakes.
infrastructurefirstPower, water, waste, phone and internet. A proposed works under the sand, drawn as proposed, nothing more. Plus public features an islander pinned on the map.
economyfirstBusinesses, tourism, housing, jobs, prices, and a ledger that counts money only, on purpose.
peoplefirstThe first build invents about two thousand residents, a small town's worth. Not one is a real person. Minjerribah itself has about 2,200 residents, the number for the real island. Each has needs, a daily round, friends, visitors and today's events.
movementfirstRoads, traffic, crowds on foot, and boats on the published timetable.
civicfirstSixty-four policy levers and who decides each. Council process, public mood, budget, consultations, petitions, which Acts bind whom.
storyfirstA director watching for moments worth telling, storylines over days, the written record.
renderfirstCamera, ground, ocean, people, vehicles, colour finishing, sound.
boardsfirstFifteen panels, from the opening noticeboard to settings. A stewardship board and scanned assets are designed, not built.
datafirst secondPacks, feeds, connectors, and the gate that checks every pack. The second build also lists every source.
kernelsecondThe clock, the store, the world runner. Random numbers from a set seed, hooks for breaking things on purpose, the short code that fingerprints a run.
systemssecondThe sun, a tide that says it does not know its own height, and the crossings.
pagessecondThe ferry page for a person, and the lab where the checking tools live.
instrumentssecondTen checking tools. The selftest breaks a copy of the build on purpose.

How the parts fit

Each build has one rule.

First build

Systems read each other by name.

One World object gives each system a phase and a place in the order. They run in that order every tick. No system reaches inside another. Each posts a summary under its own name, and reads the others by name. Half the island can go missing and the rest runs.

The rule written into the first build is "simulation never imports the renderer". The renderer draws and nothing else. So the island runs in a terminal with no picture: a year of island time in five minutes. Same seed, same packs, same island, on any machine.

Second build

Every rule is a check.

One tick is one island minute. That is 1,440 ticks a day, one for every minute on the clock. Nothing in the simulation reads the real clock. Systems run in number order, then by name. The check shuffles that order to show nothing depends on it. Random numbers come in named streams from one seed. When two runs differ, the check names the system that drifted.

Every rule about the code is a named check in the gate, a script that runs those checks over every file. A rule with no check is marked NOT YET CHECKED, with a reason why. Two states only. The build says "There is no third state." A year of island time takes a seventh of a second.

The explorer

Filter by build, area and status.

Click a part for its file. Type to search. The status words:

Where this list came from

Read straight from both builds.

One file holds the list, assets/components.js. It was written on 2 September 2026 from the first build's list of systems and both builds' folders. Every count comes from it. Every entry names its file.

First build on GitHub Second build on GitHub Where the numbers come from