Built, designed, not built

What runs and what does not.

Every part is one of three things. Running. Partly there. Designed and not written.

Copernicus Sentinel-2, 13 July 2026 · sources

0
parts running, both builds
counted from the list
0
parts partly there
counted from the list
0
parts designed, not written
counted from the list
running

Built and working

A system ticks. A board opens. A pack loads. Known faults are listed with it.

partly

Some of it exists

Four of fifteen data links have a reader. The running twin reads one feed of four. Five fetchers exist, one pack saved.

designed

On paper, not in code

Somebody wrote the document or the contract. Nobody wrote the code.

First build

Designed but not written yet

  • Five modules named at start-up, none written. Fire: danger, ignition, spread, track closures. Coast: erosion and build-up at Amity Point. Groundwater: aquifer, lakes, borefield. Then a whole-day board, and a nature board.
  • Scanned objects. The rules are written down to the file names. The folder is empty.
  • Ten ways in, lowest tech first: a spoken correction, paper cards, a tape measure, business and community facts, scans, sightings, wishes, scenario ideas, memory anchors, event plans. Only the spoken correction has been used.
  • The era lane would show the island as it was. No old maps pinned to real coordinates, no old aerial photos.
  • Scenario runs. Only the stamp exists, the record that a run happened. Nothing has been stamped.
  • The gate was red at the last save, with twelve findings. Mostly council records with no source, plus files whose fingerprints no longer match. New records and scenario stamps stay blocked.
  • A scheduled sync. Every data link says how often to run it. Nothing runs on a timer. The weather goes stale and the screen reads “not known”.

Second build

Not on screen yet

  • No map, no island shape. The renderer draws one test scene of flat rectangles, checkable pixel by pixel. A coastline waits on the licence call, because that data comes with a share-alike rule.
  • No residents. The rule says a made-up person gets labelled on their card. Nobody exists yet.
  • No live feed. The ferry page reads the printed timetable against the clock. On the day the barge stops, the page still shows it sailing. The build calls that its worst gap.
  • Live buses. TransLink positions over the printed timetable. Not started.
  • The biggest unknown is two numbers: sailings a day, and vehicles per barge. The operators have them. No open source lists them.
  • The tide table for Dunwich port, not obtained. The tide model has no numbers, so the page shows a marker and a date.
  • Four packs in the inbox: OpenStreetMap, weather, census, ecology. Fetched with receipts, waiting on the licence call.

Against the purpose

What neither twin can do

The purpose page sets the test. Push the model with a threat. Run it to real engineering numbers. Keep it inside joyful responsible abundance. Both repositories turn up seven gaps.

GapWhat is missingWhat was searched
No threat runsAsk what happens if the power drops, the sky burns, or the barge stops for a fortnight. Neither build answers.Space weather, solar storm, Carrington, micro-nova: nothing in the code.
The values are not in the codeJoyful responsible abundance is the test survival has to meet. No panel reports on it.The phrase returns nothing in either repository.
No generation runningThe first build's data rates four devices. Wave, 110 kilowatts over six chambers. Tidal vortex, 25. Bladeless wind, 15. Rooftop solar. Nothing turns those ratings into power.Those numbers sit in a data file. No generation code in either build.
No coastal chainSpoil, reef, oyster beds, living shorelines, shaped banks. Drawn up in the repositories, never on screen.No reef, shoreline or sediment system.
The second build has no islandThe build put measuring tools first. The land comes after.Its documents call that the planned order.
Unmeasured groundSix ground numbers have never been taken here. Hydraulic conductivity first: how fast water moves through sand. The lens surface comes off one satellite reading marked low confidence.The ground physics file names each one.
Where the cars goThe terminal upgrade leaves it open. Where do cars wait when the island is full?No parking demand, no park-and-ride, no peak-day arrivals.
The eco-city pack prints its own shortfall. Tiers one to three connect about 2,478 kilowatts, near 1,650 kettles at once. All four tiers come to 5,438 kilowatts. Day against day it needs 23,792 units off the power bill and makes 1,296. That is about 1,300 homes of demand against 72 of supply, 18 times short. Set the printed ratings side by side and it is 9.5 times: 2,478 kilowatts of load against 262 kilowatts of gear. The 54 kilowatt figure is an average output, not a peak. That gap is why the chain runs out to the reef.
The chain The test

Putting something in

What a person can put in today

A resident told the first build a business had closed. The record closed, with the correction and the date on it. Typed-up facts go through the intake tool, which needs consent and blurs the location. Your entry becomes the same kind of record as a council document, checked the same way, with your name on it. No points, no badges, no tallies.

The owner typed up the boat timetables on 19 August 2026. The second build counts that as a source. The file names who said it and when, and it is sealed, so a later change gets caught.

Neither build

No form, no portal, no account

Somebody types the facts in by hand. Both builds write files for a person to send on. Neither posts anything by itself, by choice.

Every term, in a sentence Every part