Open questions
Decided in September 2026 · Still open ·
The rules as shipped are what the code does; this chapter is what the design has not yet settled or the code has not yet caught up with, and what was decided when a question closed, so the reasons stay beside the rules they produced.
Decided in September 2026
Every question this chapter held on 26 September 2026 was answered that day. The answers are in the code and on the rules page; this is what they were.
The levers. Compulsory purchase has its button: Buy it out and pull it down on the inspector of a building you have clicked, the click being the gesture for “that one”. It costs purchase_price and purchase_legitimacy of the town’s standing, a conservation order refuses it, and a purchase the chest cannot pay for is written in the chronicle. Commissioning a building stays the browser API’s alone, because the player never places one. The launcher’s balance preset holds the rules’ dials and nothing else, and the report panels stay read-only.
The steward. Once a year the steward also judges the garrison, the grain reserve and the relief, a Council step at a time and never below the policy’s defaults. The garrison goes up while the threat is over 1.1, where the neighbours start to gather, and down while it is under 0.35. The reserve goes up after a year the town ate less than 80% of what it needed and down after twelve years without one. The relief goes up while the town’s mean discontent is over 0.5 and down while it is under 0.25. The player leans on these three as on the others. The welfare keeps its proportions, and the headless report prints it in its four parts beside their weights, so a long run can say whether they are right. The steward’s memory travels between valleys by default; a share link carries the memory its valley was founded with, or says it was founded fresh.
Hazards. The flood is spent by the day: the month’s chance at the stage the water model measured goes out over its days, each weighted by its rain, melt and storm, so a month of ordinary days carries the old chance and the river comes up in the storm. Standing water freezes band by band up the valley, each band on its own temperature, so the tarns under the summits go hard first; the river needs a fortnight of hard frost and freezes from its head down, opening as soon as the frost lets up, and the sea never freezes. An embankment is planned after a flood and raised by the builders a column at a time out of the store’s stone; it holds nothing back until the last column stands.
The quarries. A closed working with faces again is reopened before new ground is broken, and a town with no working of a material open takes one with as few as worked_out faces. A town short of stone or clay with none open robs its ruins first, however far across the town they are. The cut the town digs to turn a brook is recorded as civil work like a street’s, and nobody_digs_in_the_town allows it and a brook’s own bed; it passes.
A valley that fills up. A town that finds no house plot at the ordinary size builds in before it builds out. While houses go up in rows, it puts a narrow house against one already standing, row_min_width along the street and as deep as its neighbour. A crowded town builds its new houses to the age’s full height anywhere in the town, and its improvements add storeys, while the council allows density. Founders whose spot stands in a stretch of ground smaller than a third of the largest go to the best spot in that one. No tested seed moves (1 to 12 at 120, 192 and 384 paces): seed 11 at 192 starts with 8,365 reachable columns of an 8,611-column stretch, so the pocket it ends in is its own doing, not its founding.
Households. A mother and her children under thirteen are a household. The children sleep under her roof, in a place of their own if the house has one and in hers if not, walk and leave with her, and inherit her purse. Births keep their rule. The outskirts feel their houses: their births are scaled by the town’s room and their roofless share, and their roofless leave, families together.
The treasury. The garrison, the relief and the public works are each a share of the year’s takings (the tax, the customs, what the town sold abroad and the tools its people bought), not of the chest. A town that takes in more than it spends keeps the rest. The gates stay fixed sums.
The numbers people live by. Eight shapes became dials, their defaults unchanged: the share of a foreign army sent (expedition), what a sack takes of the treasury (loot_treasury) and of the people (massacre), the snow a sound roof carries (roof_load_mm), the flood’s chance of drowning somebody (drowning_per_course), how fast a skill is learned (practice) and forgotten (forget), and how much the town’s need weighs against a person’s own estimate (duty). The rest stay named constants on the rules page.
Firewood and bridges. After a winter it could not heat, the town plants a stool for every tree the shortfall would have taken, at most planting_max a year, on free ground nearest the town. A crossing is a piece of the street plan: once the town has a reason to cross, the plan puts the bridge at the narrows, keeps its landings as street and draws a street to the near one, and the bridge is built there.
The site’s size. There is no canonical size. Each door starts where it suits it: the rules and the headless runner at 384 × 160, the launcher at 512 × 224, a browser tab at 128 × 160, an engine recipe at 256 × 160. Every door clamps to the same limits (terrain::limits, on the rules page). The lightweight browser painter is gone from the site; the full WebGPU viewer holds a tab to 192 × 160.
Save and load. A valley saves to a versioned snapshot and carries on: Ctrl + S and --load in the viewer, --save, --load and --hash in the headless runner. The state hash holds across machines, and a town saved and carried on ends in the same state as one that never stopped. The fine 3 cm layer is drawn again from the fabric after a load.
Interiors. Interiors stay measured, not walked. Walking them would multiply the cost of every route for rooms nobody sees from outside.
The founders’ camp. For its first founding_camp_years (five) a town is its founders’ camp: nobody walks off for want of a roof and no party is sent to found another village. Without it, a party of forty-eight founders was crowded in its camp by the third year, split off a village on bare ground, and both lost their people to the road; at one day a turn a town has housed its founders by its fourth or fifth year. A valley opens on one day a turn again: at two days a turn a young town built half as much a year and its founders slept out for over a year.
God mode’s amounts. Its buttons bring ten or fifty people, call a five-year boom that doubles births (BOOM_FERTILITY), give a year of bread and 500 to the chest. The amounts are the viewer’s, not rules; the doubling is a named constant. Whether a boom should cost something, or strangers arrive only from a city that can reach the valley in the age, is open.
Levers and determinism. Every order the player gives is written with the turn it was given at, the world’s pace included. A share link carries the orders and the steward’s founding memory, and a valley founded from it gives each order again at its turn, so the same link opens the same town.
The browser. The browser stays WebGPU-only. On a touch screen one finger orbits and taps to inspect, and two fingers pinch and slide. The viewer publishes its memory, and the host names the graphics adapter in every failure.
Still open
Whether the steward’s proportions are right
The welfare is still fed, housed, employed and content in fixed proportions. The long runs below print it in its parts; whether a town the steward is steering towards that welfare is a town worth living in is what they should show.
Century-scale balance
Towns at 384 paces grow to between one and three thousand people in the thirteenth century, and a town saving for its next age keeps its public works in the chest. With the treasury now budgeted from takings, the families, the outskirts that feel their houses, the crowded town building in and up and the planted woods, nobody has yet run a valley through six centuries. What is open:
- The money gates. Whether the later gates (40,000 and 120,000) are reachable before the calendar’s slack brings them down, now that a town keeps what it does not spend.
- A small town and a fixed price. A town shrunk to a couple of hundred takes in little and still pays abroad for its houses’ material. Whether saving from takings is enough for it to recover is untested.
- Firewood. Whether planting after a cold winter keeps a town of fifteen hundred warm, or it still buys wood or freezes.
- The later ages. No natural run has been taken past the Renaissance with every change above in.
These runs take an hour or more each on four cores and are not part of any test:
cargo run --release -p palim-sim --bin palim-headless -- --years 600 --seed 3 --size 384 --every 10 --debug --chronicle
cargo run --release -p palim-sim --bin palim-headless -- --years 600 --seed 7 --size 384 --every 10 --debug
cargo run --release -p palim-sim --bin palim-headless -- --years 600 --seed 11 --size 192 --every 10 --debug
What to read in them: the treasury climbing through the gates rather than levelling at a year and a half’s takings; the steward’s welfare in its parts and its three levers; the outskirts staying near their houses rather than thousands past them; the fuel line after cold winters; narrow and taller houses in a crowded town; and the year each age begins. Add --save to keep a run’s end and carry it on later.
A small valley’s quarries
On a 120-pace valley seed 11 founds in a pocket its town holds 91% of by year forty, with 34 workable faces left outside it. The town now keeps the ground it will grow into and fills its old pits in when it reaches them, so a valley that small runs out of ground past its edge to open a working on; a town with no working of a material open then takes one inside its built-up edge as far out as the old thirty paces, still off its own ground, and fills it in once it is done with it (Quarry::last_resort), and the_diggers_never_work_the_town_s_own_ground passes. Whether a town that small should buy its stone instead is open.
city::town::tests::a_town_gets_a_church_and_not_a_row_of_hospitals (seed 7, 128 paces, 150 years) fails, and failed before the quarries were kept off the ground a town grows into: on that seed the town has at most a granary by the end, and no church. Which public buildings a town manages is emergent; whether the test should look at another site is open.
The ground’s numbers
The ground moves under one rule, the angle of repose, and its numbers were
chosen for their physics rather than for play: sand runs at one course, earth
holds two, turf and clay three; sodden ground a course less, the town’s own
ground two more; a slip moves at most slump_budget (400) courses a day; a
building loses undermine_harm (0.15) of its condition for each footing
column that slides from under it; a shock takes quake_landslides (1) course
of repose off the slopes at its epicentre; streams cut sand at 6, earth at 12,
turf at 16, clay at 18 and rock at 40 against the old flat 12 and 40, 1.6
times faster in the thaw, and spend 35% of their cutting on the bank ahead of
them at a bend. The first four are dials. Whether a town should lose houses
to the ground as often as these give (none in sixty years of seed 7 at 224;
the streams’ beds are mostly clear of the houses), and whether the range
should keep its crags as long as it does, is open until a long run says.
Snow and the fine layer
The engine’s snow writer reads the fine 3 cm layer to decide where a metre of snow may lie, and the viewer cuts that layer’s ground again whenever the renderer asks for chunks. In the viewer, then, where the snow lies can depend on when frames were drawn, and snow in the metre cells changes where people walk. The rules alone replay exactly: the headless runner, the web API and a save all carry them to the byte. Whether the snow should decide by the metre fabric alone, which would make the viewer exact too, is open.
The metropolis in the viewer
The rules hold at that size: forty villages on 512 columns, with 4,000 citizens walking and 20,000 counted, run at 15.4 simulated days a second on four cores (see performance). The native viewer’s frame budget there needs a GPU to measure, and the command is in the performance guide.
The browser on real devices
GPU coverage, memory use in mature cities, touch on real phones and performance on lower-end devices still need measuring on those devices. The viewer now reports its memory and the adapter’s name, so a report from a device carries both. A save is for the desktop viewer: a valley’s save runs to megabytes, and a page’s storage holds a few. In the browser the link is the way back to a valley; whether it should also offer a save to download is open.
This chapter is docs/design/12-open-questions.md in the repository; the site renders the file as it is.