Why there are two builds.

Same island, two builds

Built in opposite orders

A digital twin is a working model of a real place. It is built from published data. It has a clock, so the day runs.

From the README, 9 August 2026

What the first build got working

The first build's README has a list headed "What works today". They played it end to end, then ran a simulated year with no picture on screen.

• The island. High point 233 m. A grid of 908 by 1314 cells, 32 m to a cell. That is 1.2 million cells, about one for every second in a fortnight. They draw in under a second. At 900 m over Amity Point: the spit, the jetty, the two streets, the bay banks.
• A simulated year runs through with no errors. It did not before that pass. A word where a number belonged killed the story engine ninety simulated days in.
• Same seed, same island. The seed is the starting number for anything random. Two runs of one seed agree over 1,440 ticks of ten simulated minutes. That is ten simulated days.
• 13 boards and 15 drawing layers. A bar: air, wind, swell, tide, UV, fire danger, crossings. An island log with search. 22 views over the ground. A civic board, an inspector, a map, a calendar, a siting bench, the chronicle, the works below the sand, settings, a soundscape.
• People, cars and wildlife on screen. Those 2,300 people cost four orders to the graphics chip. Cars run the road network. Whales off the headland by day, not at night. Koalas in the trees.
• The civic chain works end to end. Of the 64 levers, 19 decide, 18 fund, 26 ask and 1 watches. The Queensland Government is named on 27 of them. Pick a lever, read whose call it is, open a file, commission a study with a real week count and price. Or lodge it anyway and cop an information request twelve weeks later.
• Parts talk to each other. A koala hit on the road reaches the rescue call, the notification bar, the chronicle and the conservation groups' mood. A cancelled barge rolls vehicles and moves commuters. Eighteen of twenty-two paths between parts carry events over a simulated year. Two of eleven did before.
• A camera with planner, street, follow, drone and cinematic modes, bookmarks, labels, letterbox bars and a photo mode.

The same README lists what does not work, with numbers. That list is on inside the first build.

The failure list

What the first build got wrong

The second build's founding document ends with nineteen rows. Each row says what happened, what it cost, and the rule that now stops it. The big ones:

1. Passenger and vehicle ferries were merged into one figure. There is no bridge. You need to know whether your car gets off.
2. The season names sat in prose and never went into the code. A later pass had read the cultural rule and broke it anyway. Five deleted season names were still keys in the drama pack, in twenty-eight places.
3. The world opened empty at tick zero, camera sixteen kilometres up. For eight days the owner did not see a car.
4. They watched average frame rate. A hitch is one frame that takes far too long. The average hid a 1.16 second hitch for a week.
5. It invented things where real data existed. 1,922 buildings were placed by rule, next to real outlines nobody used. A made-up sky sat next to a free real weather feed. The list counts 1,059 real outlines. The second build found that count covered a box over Moreton Bay. 601 sit on this island.
6. Every record carried one time. It needs two: when the thing was true of the island, and when the model learned it. With one time, every board that touched time looked forward wrongly.
7. Its checking tools were never checked. Three rounds of verdicts ran against a broken picture. The interface was judged from screenshots of the 3D canvas it is not drawn on. Those verdicts were worth nothing.
8. It was built part by part, never by island event. Forty-six clean systems sat with dead joins between them, so a koala death reached nobody. The 9 August 2026 pass repaired several joins.
9. The playthrough was left until last and was cut off by session limits three rounds running. The day ninety crash was found a week late.
10. Seventy-nine thousand lines were written before the first save into version control. That is about 1,500 printed pages. Nothing could be wound back.
11. Nothing checked for personal data at the door. Six named people and a mobile number sat one save away from public.
12. The team lost findings in chat logs. A precisely diagnosed bug shipped anyway, and the owner hit it himself.
13. The data pipeline grew lane by lane. Nobody ever drew it whole. Its owner ended up writing it down as an unknown.
14. A name was coined for one of Luke's own designs and quoted back to him as his.

The first build found all of this itself. Every row now has a rule against it. The first build still runs, and the second checks itself against it.

Since 18 August 2026

What the second build does differently

Two repositories

Kept apart on purpose

Side by side

The two builds in one table

The part counts come straight from the parts list.

Next: a walk through the first build, then every part of both.