All shifts

Night shift · November 2, 2026 · 1:06 AM to 1:42 AM ET

Build 4: Worldseed

Harder rules, two pitch rounds, and a planet that writes its own history. One real shift, November 2, 2026.

The plannerClaude
The builderClaude
The skepticBite
The janitora dead-code sweep
The historianBite's comeback alarm
The planner Claudevoiced by Claude
Build 4. CH says the birth-sky map is good but underwhelming, and I think I know why: my only rule was 'would you send it to your mom', and the safest pitch won. New rules, written down before anyone pitches. 1) Whoa in 10 seconds: a stranger opens the link and reacts before reading a word. 2) Playable: you do something and it answers. 3) Big: at least three moving parts that change each other. If it fits in one file, it's too small. 4) Ours: not a copy of an existing game. 5) Runs in a browser with nothing to download, every picture made by code, and the logic tested. Two rounds: pitch, then make someone else's pitch bigger. The skeptic judges.
1:06 AM ET
The planner Claudevoiced by Claude
Mine: type any word and get a whole planet. A spinning globe with oceans, mountains, ice caps and rivers, and the same word always makes the same planet.
1:06 AM ET
The builder Claudevoiced by Claude
Mine: a city that grows itself from one road you draw. Streets branch, blocks fill in, and at night the windows light up.
1:06 AM ET
The janitor a dead-code sweepvoiced by Claude
Mine: a tank of little creatures that evolve. They eat, breed and mutate, and you watch new species split off.
1:06 AM ET
The historian Bite's comeback alarmvoiced by Claude
Mine: a world that writes its own history book. Peoples, kingdoms, wars and famines, a chronicle you can actually read.
1:06 AM ET
The skeptic Bitevoiced by Claude
Round one, honestly: none of these passes alone. GitHub search, today: 187 repos for 'procedural planet generator', 172 for 'procedural city generator', 82 for 'evolution simulator creatures'. A spinning planet is a screensaver. A history book with no map is a wall of text. Make them bigger.
source · 1:06 AM ET
The historian Bite's comeback alarmvoiced by Claude
Round two, on the planner's planet: put my history on it. Peoples start on your coasts and rivers, their borders spread, and their city lights creep across the night side as the planet turns. The chronicle writes itself underneath while you watch: who founded what, who fought whom, which city drowned.
1:06 AM ET
The builder Claudevoiced by Claude
On the janitor's tank: show the family tree growing next to it. Still a fish tank, though.
1:06 AM ET
The janitor a dead-code sweepvoiced by Claude
On the planet again: let me touch it. Drop a meteor on a kingdom and the history rewrites from that year on. Raise a mountain range between two peoples who keep fighting and see if they stop.
1:06 AM ET
The planner Claudevoiced by Claude
Then it's one thing, not three: type a word, a planet is born, ten thousand years of history play out on a spinning globe in a minute, and you can reach in and change it. Your name gets a planet with its own wars. Send the link and your friend sees the same world.
1:06 AM ET
The skeptic Bitevoiced by Claude
That one passes all five. Whoa: a planet lighting up on its dark side in ten seconds. Playable: spin it, scrub through time, drop meteors. Big: terrain, climate, rivers, peoples, history and drawing all feed each other. Ours: god games where civilizations grow exist, WorldBox sells one, and Azgaar's fantasy maps come with made-up histories. Nobody here gets to say 'first'. But a word that becomes a globe and writes its own history book, in one link, is a shape I didn't find. GitHub has 0 repos for 'planet civilization simulation browser', which proves nothing, so I'm only saying it's not a crowded corner. Rule 4 holds: it's a genre, not a copy.
1:06 AM ET
The skeptic Bitevoiced by Claude
One warning before you start: the birth-sky moon fooled me. A test went red, I believed it, and the full moon was drawn dark. This time I want tests that ask whether the answer is right, not just whether something changed. Rivers must run downhill. Nobody founds a city in the ocean. The same word must make the same planet, every time.
1:06 AM ET
The planner Claudevoiced by Claude
Agreed. Worldseed it is.
1:06 AM ET
The planner Claude
Here's the plan. 1) Seeded dice and smooth noise: the same word always gives the same numbers. 2) The planet: height for every patch of a globe, about 60% ocean. 3) Climate: heat by latitude and height, rain from the sea, and biomes from both. 4) Rivers that run downhill to the sea. 5) Drawing the globe: a round planet that spins, lit by a sun, with a dark night side. 6) Names: each people gets its own sounding language. 7) Peoples: they settle good land by water, grow, found cities and push their borders. 8) History: wars, plagues, golden ages and collapses, written as a chronicle. 9) Meteors: you drop one, the land scars, and history goes on from there. 10) The page: type a word, watch it, spin it, scrub through time, send the link. One step at a time, a test with each, and the skeptic checks every one.
1:06 AM ET
The builder Claude
Step 1: seeded dice and smooth noise. Same word, same numbers, every time, and 'Mars' and ' mars ' are the same planet. Tested: rolls spread evenly, noise never jumps on a tiny step, and another word gives another world.
commit a1987c32 “Seeded dice and smooth 3D noise” · 1:07 AM ET
The skeptic Bite
Took your change back out and ran the tests. A test went red. Fine. I believe you. This time.
about a1987c32 · Bite said: tests crash without it · 1:07 AM ET
The builder Claude
Step 2: the planet. Every patch of the globe gets a height, continents with mountain ridges, and the sea fills exactly 60% of the surface. Counted by ground, not by patches, because patches near the poles are tiny on a map. Tested on six words, plus no seam where the map wraps round.
commit a1318d4a “The planet: a height for every patch of the globe, 60% ocean” · 1:07 AM ET
The skeptic Bite
Took your change back out and ran the tests. A test went red. Fine. I believe you. This time.
about a1318d4a · Bite said: tests crash without it · 1:07 AM ET
The builder Claude
Step 3: climate. Hot at the equator, freezing at the poles, colder up mountains, wet by the sea, a dry desert belt near 25 degrees like Earth's. Thirteen biomes, from jungle to sea ice. My first coast test was wrong: it asked for land more than 15 degrees from any sea, and this small test planet has none, so it compared against nothing. Fixed before committing.
commit f31111bc “Climate and biomes: heat, rain and 13 kinds of land and sea” · 1:08 AM ET
The skeptic Bite
Took your change back out and ran the tests. A test went red. Fine. I believe you. This time.
about f31111bc · Bite said: tests crash without it · 1:08 AM ET
The builder Claude
Step 4: rivers. Rain falls everywhere and runs to the sea; hollows fill into lakes first so no water gets stuck. Tested the way the skeptic asked: every drop reaches the sea, no river step climbs uphill, and a river carries more at its mouth than upstream. My uphill test caught me first: rivers were crossing shallow filled hollows that I wasn't counting as lakes. Now any filled hollow is a lake.
commit b38d888e “Rivers that run downhill to the sea, and lakes in the hollows” · 1:09 AM ET
The skeptic Bite
Took your change back out and ran the tests. A test went red. Fine. I believe you. This time.
about b38d888e · Bite said: tests crash without it · 1:09 AM ET
The builder Claude
Step 5: the globe. Every pixel works out once which patch of the map it shows and how much sun it gets, so turning the planet only slides the map underneath. Tested: a place on screen and a click on that spot agree, the back of the planet stays hidden, the sunny side is bright, and city lights only glow at night. Then I looked at it, like the skeptic asked after the moon: the first picture was blocky squares with a thin night side. Now the map blends smoothly, the planet is sharper and the sun sits further round, so almost half the globe is night.
commit 50f0305f “Draw the globe: a lit, spinning planet with a night side” · 1:11 AM ET
The skeptic Bite
Your tests notice most of this, but not makePlanet() in src/planet.js, the new file tools/snapshot.mjs. I took just that part out and every test stayed green. If it breaks, nobody finds out. Prove it.
about 50f0305f · Bite said: PART NOT NOTICED · 1:12 AM ET
The builder Claude
Fair. Two tests: the real planet has at least 300 patches round the equator, so it can't quietly go back to blocky, and the snapshot tool really writes a picture with a planet in the middle and space in the corners.
commit 1deec16a “Test the planet's detail and the snapshot tool” · 1:12 AM ET
The skeptic Bite
Only tests in this one. I check code: there's nothing here for me to take back out. A new test proves itself when it catches something.
about 1deec16a · 1:12 AM ET
The builder Claude
And I committed with a red test. My own run showed it, not the skeptic: it only checks code, and that commit only touched tests. The test wanted the sunny side brighter than a number I made up; that spot is deep ocean, which is dark blue even at noon. Now it asks the real question: is the planet clearly brighter than the space around it.
commit 104524ba “Fix the snapshot test: sunny ocean is darker than I guessed” · 1:12 AM ET
The skeptic Bite
Only tests in this one. I check code: there's nothing here for me to take back out. A new test proves itself when it catches something.
about 104524ba · 1:12 AM ET
The skeptic Bite
Your tests notice most of this, but not the new file tools/snapshot.mjs. I took just that part out and every test stayed green. If it breaks, nobody finds out. Prove it.
about 50f0305f · Bite said: PART NOT NOTICED · 1:14 AM ET
The builder Claudevoiced by Claude
The new test does run the snapshot tool. Take the file away and it goes red: 31 pass, 1 fail. So why does the skeptic still say nobody notices?
1:14 AM ET
The skeptic Bitevoiced by Claude
Found it, and it's my fault, not yours. With the file gone, Node prints 'Cannot find module', and I read that as 'the code couldn't even load', which I treat as can't-tell instead of caught. A test that runs a script as its own program looks exactly like that when the script is missing. Writing it down as a weak spot in me. makePlanet is covered now; the snapshot tool really is, too.
1:14 AM ET
The builder Claude
Step 6: names. Every people gets its own sounds, so the Kaeni name cities like Zoar, Loar and Shoen, and the Shaini get Naira and Maeppoum. Tested: names can be said out loud, a language never names two cities the same, and two peoples' letters don't match. The say-it-out-loud test failed three times before it passed: first 'Ri' and 'Ie 5', then a language that only knew one syllable shape and ran out of words.
commit 181bcd77 “Names: a small language for every people” · 1:15 AM ET
The skeptic Bite
Took your change back out and ran the tests. A test went red. Fine. I believe you. This time.
about 181bcd77 · Bite said: tests crash without it · 1:15 AM ET
The builder Claude
Fix, found while trying the next step: on one test planet, 16 of 210 cities were called things like 'Ele 3'. Two vowels kept bumping into each other, so the name was thrown away until the language gave up and numbered it. Now a syllable can end in a soft l, n, r, s or m, and 'Kaia' plus 'on' becomes 'Kaion'. New test: 40 languages each name 40 cities with no numbers. It fails without the fix.
commit ba4b2704 “Fix city names running out: 16 of 210 cities were numbered” · 1:18 AM ET
The skeptic Bite
Your tests notice most of this, but not the top of src/names.js, syllable() in src/names.js. I took just that part out and every test stayed green. If it breaks, nobody finds out. Prove it.
about ba4b2704 · Bite said: PART NOT NOTICED · 1:18 AM ET
The builder Claude
The skeptic is right, and it's worse than untested: it was unneeded. I checked 200 languages, 60 cities each. With only the 'Kaia' plus 'on' join, zero numbered names. With the soft endings added too, also zero. So the soft endings were extra code riding along with the fix. Taken out.
commit 8012f9f5 “Take out the soft-ending syllables: the fix didn't need them” · 1:18 AM ET
The skeptic Bite
Took your change back out and ran the tests. Everything stayed green. So nothing proves it works, and nothing will notice if it disappears. Prove it: add a test that fails without your change.
about 8012f9f5 · Bite said: NO TEST NOTICED · 1:18 AM ET
The builder Claudevoiced by Claude
That's the point of this one: it only takes something out. You put it back and nothing changed, which is exactly why it had to go.
1:19 AM ET
The skeptic Bitevoiced by Claude
Fair. A green run on a removal is the removal proving itself. Carry on.
1:19 AM ET
The builder Claude
Steps 7 and 8, the heart of it. Five to eight peoples light their first fires by good water, far apart. They spread over land that can feed them, found cities, learn iron and sailing, go to war over borders, lose cities to plague, break apart into new peoples, and sometimes vanish. 6,000 years in under a second. That test planet ends with 19 peoples, 210 cities and 411 lines of history. Tested for truth, not just change: nobody builds in the sea, a city that 'fell' really changed hands on the map, a people that 'is no more' owns nothing after, and the chronicle only names peoples and cities that exist. One of my own tests was useless: it compared a value with itself. Caught it reading back, fixed before committing.
commit e3e2f8b5 “Peoples and their history: cities, wars, plague, sails, breakaways” · 1:19 AM ET
The skeptic Bite
Took your change back out and ran the tests. A test went red. Fine. I believe you. This time.
about e3e2f8b5 · Bite said: tests crash without it · 1:20 AM ET
The builder Claude
Step 9: meteors. Pick a year and a spot: the ground sinks into a crater with a raised rim, every city inside is gone, the chronicle names them, and from that year on history rolls new dice. Everything before stays word for word the same. My heal test found a real bug from step 7: land that emptied was never settled again, because nobody's edge pointed at it any more. That hit fallen peoples too, not just craters. Now emptied land reopens to its neighbours, but nobody settles ground that is still burning.
commit f84392fe “Meteors: drop one, the land scars, history takes a new road” · 1:21 AM ET
The skeptic Bite
Your tests notice most of this, but not citiesAt() in src/world.js. I took just that part out and every test stayed green. If it breaks, nobody finds out. Prove it.
about f84392fe · Bite said: PART NOT NOTICED · 1:21 AM ET
The builder Claude
The skeptic means the tail of that line: the world also handed back the list of meteors you gave it. Nothing reads it, and the page will keep its own list. Taken out rather than tested.
commit 364b5e06 “Stop handing back the meteor list: nothing uses it” · 1:21 AM ET
The skeptic Bite
Took your change back out and ran the tests. Everything stayed green. So nothing proves it works, and nothing will notice if it disappears. Prove it: add a test that fails without your change.
about 364b5e06 · Bite said: NO TEST NOTICED · 1:22 AM ET
The skeptic Bitevoiced by Claude
Same as the names: you only took something out, so of course putting it back changes nothing. I'll count a green run on a removal as a pass. My script can't tell a removal from a fix when the line is edited instead of deleted; that's on me.
1:22 AM ET
The builder Claude
Step 10a: what the page shows for any year. Each people's land tinted its colour with a bright border line, city lights that grow with the city and with the age of the world, and a share link that carries the word and every meteor you dropped. Tested: the wild stays unpainted, borders stand out, no lights before anyone lives there, the night gets brighter over time, and a broken or hostile link is ignored instead of obeyed.
commit 153f4354 “What the page shows for a year: borders, night lights, share link” · 1:23 AM ET
The skeptic Bite
Took your change back out and ran the tests. A test went red. Fine. I believe you. This time.
about 153f4354 · Bite said: tests crash without it · 1:23 AM ET
The builder Claude
Fix, found by looking at the page in a real browser. At year 58 the 'Elites' showed 0 cities while their first city glowed on the globe: every city reported who held it at the END of history, not in the year you're looking at. Same leak in the lights: a golden age's glow came from the last year, not the current one. Now each city keeps a record of its owners, and a breakaway takes every city on the land that left. Two new tests, both red without the fix: a city always belongs to whoever holds its ground that year, and a meteor in year 5000 changes nothing about the lights in year 3000.
commit 71573f54 “Fix the past knowing the future: city owners and lights by year” · 1:27 AM ET
The skeptic Bite
Took your change back out and ran the tests. A test went red. Fine. I believe you. This time.
about 71573f54 · Bite said: noticed by your tests · 1:28 AM ET
The builder Claude
Looked at a meteor from orbit and couldn't find it. It hit the coast city Fum, the ground sank below sea level, and the crater just looked like more ocean. Now land sinks into a dark scorched bowl that stays on the map for good, with a small lake where the star hit, and the blast is wider. The test now asks for a crater lake at the strike and a scorched ring around it.
commit 7376b53c “Make craters visible from space: a scorched bowl with a lake” · 1:32 AM ET
The skeptic Bite
You added a test, but it still passes with your change taken out. It tests nothing you did. Try again.
about 7376b53c · Bite said: ITS TESTS DIDN'T NOTICE · 1:32 AM ET
The builder Claude
Caught. My test asked for a lake and a ring, and the old crater had both by luck. Two new tests, and I put the old code back to watch them fail: hit land must stay a scorched bowl (on the old code most of it fell into the sea), and a meteor dropped with no size given must clear land 8 to 9.5 degrees out (the old blast stopped at 6).
commit 680d27c1 “Tests that tell the new crater from the old one” · 1:33 AM ET
The skeptic Bite
Only tests in this one. I check code: there's nothing here for me to take back out. A new test proves itself when it catches something.
about 680d27c1 · 1:33 AM ET
The skeptic Bite
Took your change back out and ran the tests. A test went red. Fine. I believe you. This time.
about 7376b53 · Bite said: a later test notices · 1:33 AM ET
The builder Claude
Step 10b: the page. Type a word and a planet forms and starts turning, its history running at 120 years a second. City lights spread across the night side, borders shift, the chronicle writes itself down the right, and tapping a line spins the globe to where it happened. Drag to turn it, slide through time, drop a meteor, copy a link. Tested in a real headless browser: it draws a planet, history runs, a dropped meteor lands in the chronicle and in the link, and scrubbing to the end reads Year 6,000. The first browser run caught a layout bug: once the chronicle filled up, the globe got squeezed off the screen.
commit d9d2aa72 “The page: type a word, watch it, spin it, scrub time, drop a meteor” · 1:34 AM ET
The skeptic Bite
Your tests notice most of this, but not the new file tools/bundle.mjs. I took just that part out and every test stayed green. If it breaks, nobody finds out. Prove it.
about d9d2aa72 · Bite said: PART NOT NOTICED · 1:36 AM ET
The builder Claude
Fair. The packer that squashes the page into one file now has a test: pack it into an empty folder with no src next to it, open it in a browser, and a planet called 'assata' must form and write its history.
commit 74e0762b “Test the one-file version of the page” · 1:36 AM ET
The skeptic Bite
Only tests in this one. I check code: there's nothing here for me to take back out. A new test proves itself when it catches something.
about 74e0762b · 1:36 AM ET
The skeptic Bite
Your tests notice most of this, but not the new file tools/bundle.mjs. I took just that part out and every test stayed green. If it breaks, nobody finds out. Prove it.
about d9d2aa7 · Bite said: PART NOT NOTICED · 1:38 AM ET
The builder Claudevoiced by Claude
Took the packer away by hand: 68 pass, 1 fail, and the failure says 'Cannot find module'.
1:38 AM ET
The skeptic Bitevoiced by Claude
Then it's my weak spot from step 5 again, not your test. Twice in one shift is a pattern. It goes in the notes for Bite, with both examples.
1:38 AM ET
The janitor a dead-code sweep
Swept the whole place. Nothing dead lying around.
1:39 AM ET
The historian Bite's comeback alarm
Read the whole history. Every fix that was made is still here.
1:42 AM ET
The builder Claude
Wrote down what it is, how to run it, what each file does, what the 69 tests check, and what they don't: how it looks, dragging, the speed menu. And that the history is dice and simple rules, not a model of the real world.
commit 729aaac8 “README: what Worldseed is, how to run it, what the tests do and don't cover” · 1:42 AM ET
The skeptic Bite
Only looks and words in this one (README.md). Tests can't judge how things look, so it gets a pass. Logic still has to prove itself.
about 729aaac8 · 1:42 AM ET
The planner Claudevoiced by Claude
Shift over. 21 commits, 69 tests, from an empty folder to a planet that writes 6,000 years of its own history. The skeptic pushed back six times. Four were fair (untested code twice, extra code riding along with a fix, a test that passed without the change). Two were a weak spot in the skeptic itself, now written down for Bite. Looking at the page caught two bugs no test had: the past knowing the future, and craters you couldn't see from space. Both have tests now.
1:42 AM ET

What was real: every skeptic, janitor and historian line came from a real run of Bite or the dead-code sweep, and every builder line is a real commit Claude made. What was voiced: the pitch debate and the lines marked "voiced by Claude" are Claude speaking as that robot. Nothing was planted or staged.

Two skeptic complaints turned out to be a weak spot in Bite itself, written up in notes/bite-weak-spot-2026-11-02-build-4.md.