The journal · updated

Chasing the signs of life.

Sun-followers, comet-like blobs, worms and labyrinths: the promising moments are shaping the next experiments. We’re looking for what makes those behaviours possible, then trying to amplify them. This journal keeps three things apart: what we saw, what we measured, and what we hope.

The direction

Find the spark. Turn it up.

Our strongest working hunch is that reopening resource-rich space helps keep worlds interesting. Moving light also gives sensing and movement a purpose; selection among ponds gives us a way to push a chosen trait. Starting genomes and time matter too.

We want to search across combinations and strengths, with a tenfold increase in a compelling trait as an ambition. Ten times the disturbance does not mean ten times the life: harsh wounds can favour thin films, and fast-moving light can leave founders behind.

The first sandbox looks make that tradeoff concrete. The full storm world went extinct in its one seed; moving one lever at a time showed the sun’s speed is what kills, and the storm without its sun survived. On a calmer world, slowing the sun was the more promising lead. Breeding ponds for movement alone bred real movement and emptied most of the ponds; a score that also rewards a well-stocked founding packet kept them occupied, with movement arriving at about half the pace, and adding body size as well kept them occupied with movement at about a third of the pace. Storm worlds and the breeder are now in the lab as sandbox worlds, and you can stop the world at each pond cycle and choose the donors yourself. All of it is exploratory, not registered.

A separate line asks what it would take to make a game of evolution out of these worlds. Its first gene experiments give genomes gainable genes — decomposition, then polymer building; the entries below say what happened.

See where this is going →
Seen · exploratory

What we’re keeping an eye on

  • Sun-followers. Hand-built sensing patterns survived wandering light where blind drifters failed in a small comparison. A lead about environment and sensing, not an evolved capability.
  • Comet-like blobs. Noticed in repeatedly reset random-donor ponds. Visually promising; speed was not measured.
  • Worms and labyrinths. Longer, more elaborate bodies turned up in a few runs with inherited shape rules, and in the control worlds too, so no difference in shape is shown. What would make them last still needs exploring.
  • Selection among ponds. Choosing which groups seed the next cycle provides a practical starting point for breeding toward visible traits. More drive in a score must still be checked against actual movement.
Measured · through 18 Oct
MetMilestone 3: founders that regrow after a wound
Not metMilestone 4: open-ended evolution over 10⁶ steps
1 of 12Founders whose mutants reliably took up a new ecological role
ConfirmedRegistered test: ponds cycled with selected donors beat all three controls at founding new ponds
24 of 24Registered histories where the evolved genome alone founded more ponds
0 of 24Pilot cases that qualified as a self-renewing habitat
Measured · one entry per result
Confirmed · 27 Sep

Regenerating founders

Milestone 3 (M3) asked for founders that can mend themselves. Its screen found genetically distinct seeds that regrow after a wound removes about 30% of a body, and die in a no-light control. A stricter retest narrowed the founder set to 12 genomes, which seeded the long-run ensemble.

Passing this gate does not establish open-ended evolution.

Negative · 28 Sep

Open-ended evolution (M4)

All 170 registered runs of 10⁶ steps finished with exact conservation. With mutation, new adaptive activity exceeded both controls in one of the two worlds. The second test failed in both: neutral runs, where mutations do not change behaviour, also counted as “growing”. A 10⁷-step extension showed the same pattern.

Living things kept recycling the waste, and different ways of living kept coexisting. A further hypothesis, held back to be checked separately, was not supported by any of its 4 measures.

Measured · 29 Sep

Where variation stalls

Genomes are copied faithfully: grown separately, the genomes of tracked parents and offspring behave alike (slopes of 0.85–0.96, where 1 would mean offspring traits rise one-for-one with their parents’, on average), though most pairs carried identical genomes. Mutation rarely changes what a genome does in the ecosystem: the mutants of only 1 of the 12 founders reliably took up a new role. A broader sample of genomes did so far more often (11 of 24), so the way founders were chosen was a bottleneck.

Evolved lineages also lost the founders’ ability to regenerate (0.17 against 0.98).

Measured · 29 Sep

What counts as an individual

The tracker credits each birth to a nearby parent. A direct check found that in 135 of 200 sampled births the credited parent contributed no copied material at the time of the birth. A tracked birth is therefore not, by itself, evidence that an individual reproduced.

This is a limit of the measurement, not a negative result. It qualifies every result built on tracked births. New exploratory worlds can still be tried while better measurements are developed.

Measured · 1 Oct

Measures that need work

None of the four activity, novelty and role measures met every validation requirement: three flagged too many neutral runs, and the role measure barely separated the comparison it was meant to.

This limits what those scores can tell us about evolution. A visually interesting world remains a lead to investigate.

Measured · 30 Sep

Founders and environments

What the founders were mattered more than how varied they were. Clouds of drifted founder genomes did little better than single founders (2 of 12 against 1 of 12), while a set made only of non-producing genomes met the new-role criterion in 4 of 5 runs, though part of that may be sorting of roles already present. Whether new roles keep arriving after niches first fill is mixed: they do not in the main comparison, and an excess in the 10⁷-step extension becomes unclear once ambiguous returns are set aside.

A bug that zeroed a background genome’s weights in one screen was found and fixed; the affected result is corrected in the plan.

Measured · 1 Oct

A life cycle for groups

Following experiments that impose a group life cycle on microbes (Black, Bourrat & Rainey, 2020), each tile became a pond. At every cycle, ponds are cleared and reseeded with a small fragment from a successful pond. In new histories, with each test fixed before its data, heritable differences between ponds (genetic or structural) appeared in 6 of 6. Fragments from cycled ponds also passed a regrowth test more often than those from random-donor ponds, uncycled ponds and the ancestor, both at once and after 200,000 steps without the cycle, again in 6 of 6.

Exploratory, not a registered milestone. Random-donor ponds show heritable differences too, so the cycle’s causal role is not shown. The genome-swap test passed only at its threshold, and a later matched control showed that most of that apparent genome gain came from mutants in the control. The life cycle is imposed rather than discovered.

Confirmed · 3 Oct

The pond result, registered

The pond life cycle then went through a registered test: hypotheses and decision rules frozen on 2 October, 24 histories per arm. Both primary hypotheses were confirmed. Worlds evolved under the cycle with selected donors founded new ponds from fragments more often than random-donor worlds, uncycled worlds and the ancestor, both when the cycle stopped and 200,000 steps later (median success 0.97 against 0.61 and 0.66 for the last two at the later point). Separately, the genome taken when the cycle stopped, placed on ancestral material, founded more ponds than the ancestor’s genome in 24 of 24 histories. That test does not explain the later persistence.

The genome’s effect is small: a median of 19 more successes in 512 fragments, and its gain did not meet the registered threshold of half the worlds’ advantage (5 of 24), a comparison that does not measure the genome’s causal share. The whole-world comparisons used fragments with different starting masses. Heritable differences between ponds were shown in 17 of 24 histories, and in as many random-donor histories, so they are not shown to be specific to the cycle. Many random-donor worlds collapsed, so the comparisons that carry the claim are those against uncycled worlds and the ancestor. The life cycle is still imposed; ponds reproducing on their own is not tested. By a decision made before the run, this counts toward no milestone.

Not yet measured · 3 Oct

Can ponds select themselves?

The next question removes our hand from the ranking. If a pond’s number of offspring follows its own export rather than our choice, do ponds evolve to export better? A frozen, exploratory hunt passed its entry checks: worlds stayed viable under the new regime, and the export measure separated a known large difference in 6 of 6 cases.

A small diagnostic with mutation switched off (four pairs, 30 cycles) showed no consistent advantage in the export measure; it cannot rule out non-genetic effects. The evolutionary stage is prepared and has not run. A hit there would be a candidate that still needs a registered replication.

Negative · 4 Oct

A search for self-renewing habitats

A new workbench asks which worlds let evolution accumulate, using exact cases that replay identically on a second machine. No scientific case has run on it yet. It starts from the audited records of a separate renewal experiment, which looked for habitats that keep a source of life going and also maintain a site outside it by local synthesis rather than imported biomass. None of the 24 main pilot cases qualified, so the confirmation stage was not run. All 40 histories conserved matter exactly, and the designated CPU and GPU replays matched.

A negative for this panel only, with one pilot seed per habitat. In calibration the detector raised no false alarm on 12 of 12 null controls and caught 3 of 4 known positives, so a steady renewal could be missed. Nothing here is evidence of evolvability, for or against.

Measured · 4 Oct

Breeding, storms and bodies

Sandbox looks, one seed each. The full storm world was extinct by step 29,000. In a separate ladder of sun speeds on the calmer gradient world, the fastest sun was lethal to the regenerating founders and each slower one left more living cells; hand-built founders survived the fastest. Sixty cycles of breeding ponds for movement alone left 23 of 64 ponds occupied; adding the size of the founding packet to the score kept 63 occupied, moving at about half the speed. When a vision model picked the most unusual-looking ponds, 9 ponds were occupied after 16 cycles against 14 under random picking, and the median movement score was zero from cycle 8 on. One seed and one model draw, so no general difference between pickers is shown; novelty and movement are not the same thing.

Separately, eight screens of rules meant to make evolution keep bodies (lossy takeover, injury, inherited shape rules, declared cells) produced no arm that met its pre-stated bar for promising; each reads unclear or dead end. Feeding a world by hand is now a lab tool, and it is logged as the one deliberate break in a closed world.

Measured · 16 Oct

A first gene

A game-kernel line gave genomes one gainable gene: decomposition as a paid-for capability, off in every founder, flipped on or off by mutation. Under a criterion written before the first run, carriers reached a quarter of the living cells by step 75,000 in all three seeds, and held about 99% at every census from step 155,000 through step 200,000. In a null arm with the same cost and the same flips but no benefit, carriers hovered at 2 to 14% and never approached the bar.

The gene paid for the lineage, not for the world: the carriers’ worlds ended as a decomposing film — more living cells gathered into fewer individuals, no growth flux at the end, and less free energy. Three seeds and 200,000 steps, not a registered test, and the sweeping clade carried other mutations too, so the null argues the gene drove the sweep but does not prove it. The gene exists only in worlds that ask for it; every standard world behaves exactly as before.

Unclear · 16 Oct

A second gene

The gene set then grew to two: polymer building as a second paid-for capability over the same founders, against a null arm whose build gene costs the same and does nothing. By the rule written before the first run, the result is confounded: the do-nothing gene reached about half the living cells in two of three null seeds, so the one treatment seed where the build gene’s share ended high says nothing about polymer. Carriers who could build barely did — build flux peaked at 16 quanta a step in one seed and read zero over the final stretch in the other two, and polymer never passed 2% of bound mass. Decomposition, the first gene, swept again in all six runs.

Three seeds and 200,000 steps, not a registered test. No run here tests a polymer gene that is expressed, so nothing follows about polymer itself. The proposed explanations — founders whose controllers barely drive building, a near-neutral bit riding clade turnover in a decomposer film — are readings, not measurements. The null design reads only on a quiet background: the first experiment’s world held its do-nothing gene to a few percent, while on this background with clade turnover a costly, unused gene reached the bar twice, so a zero-cost arm is the named next control. One treatment film collapsed after step 150,000, losing nine tenths of its cells; the null on the same seed did not, and no cause is assigned. Both genes exist only in worlds that ask for them; every standard world behaves exactly as before.

Negative · 17 Oct

An anomaly bell

The first piece of an AI naturalist is a bell written in code, not a model. It scores how far a run has strayed from the neutral runs of the same world, where mutations do not change behaviour, and its rules were written down before it read any data. Over 85 finished runs, at the setting fixed beforehand, 30 of the 70 neutral runs rang where the bar allowed at most 2. By its own rule, then, it rings on drift. Every treatment and no-mutation run rang too, all but one of them in the first stretch the bell counts, from step 10,000. Those worlds are already smaller than neutral ones at the first census the bell counts, so it tells the kinds of run apart; it does not show it hearing something arise inside one.

A second reading, fixed beforehand as descriptive only, took each world’s threshold from 20 of its neutral runs and tried it on 30 other neutral runs in all: one rang, against about 1.4 expected if the two sets of runs are alike, and all 10 treatment and all 5 no-mutation runs rang. The false alarms at the first setting came almost entirely from two signals with long tails under drift, how many generations deep one line gets (20 runs) and how much of the jar one lineage holds (16), with one run on splits; a run can ring on more than one. No model was called and no new simulation ran. An exploratory instrument, not a registered test: this is a result about the instrument, not about the worlds. A field notebook built on the bell rings only above those thresholds, and its dated example is the one held-out neutral run that rang: a false alarm.

Measured · 18 Oct

A quieter bell

The bell’s second version drops the two signals behind nearly all of the first version’s false alarms: how many generations deep one line gets, and how much of the jar one lineage holds. Its scoring rules were written down before it ran, and it was judged on 70 new neutral runs of the gradient world that it had never seen. None of them rang, where the bar allowed at most 2; the first version’s rule rang on 19 of the same 70. All 10 treatment runs still rang.

As before, it tells the kinds of run apart; this test says nothing about hearing something arise inside a run. One world and 70 runs of 300,000 steps: the bar can tell a bell that false-alarms near 2% of the time from one near 10%, but cannot certify 5%. Checks that each run’s files were whole were tightened while the runs were going, before any output was read. Exploratory, not a registered test. All 120 runs of this version ran locally, and no model was called.

Negative · 18 Oct

Can the bell hear a wound?

The next test gave the bell twins. Ten treatment histories were each run again five times, identical to the original through step 200,000, then given one deliberate act there: a tiny wound of five sites (twice, in two different places), a wound of radius 64, a wound of radius 96 that removed over a third of the living cells, or a feed. The threshold came from the first set of tiny wounds (5.70). By the rule fixed before the runs, the bell had to ring on at least 8 of 10 twins for the radius-96 wound and for the feed. It rang on 4 of 10 for each, and on 0 of 10 for the radius-64 wound. The held-out tiny wounds rang on 0 of 10, so the threshold itself held up.

Scored afterwards on the eleven signals of the quieter bell, with the threshold taken again from the tiny wounds (2.58), the radius-96 wound would ring on 10 of 10, the feed on 8 of 10, the radius-64 wound on 5 of 10 and the held-out tiny wound on 1 of 10. That is a hypothesis for a next version to fix in advance and test on new twins, not a pass. One reason a sudden wound scores low: the jar regrows part of what it lost within the 1,000 steps a departure has to hold. All the twins come from the same ten histories of one world. The third part, a model reading the same twins, has not run; its calls are paid and wait for a yes.

Negative · 18 Oct

Change read from the mutation tree

Three measures read change from who descends from whom, rather than from lineage labels that every mutation renews: how recently most of the jar shares one ancestor, how often a mutant family sweeps to half the jar, and how much of the jar passes from one family to another. Over 130 finished runs (30 treatment, 70 neutral, 30 with mutation off), none of the three passed every check, written down before computing, that a measure must pass before it can be used to look for selection. In the gradient world every measure pointed the wrong way, ranking neutral runs as more “selective” than treatment runs. Each treatment run was compared with each neutral run, counting 1 when the treatment run looked more selective, a half for a tie and 0 otherwise; the average had to reach 0.8, and the three scored 0.34, 0.18 and 0.00. The two measures that flag single runs flagged 16 and 40 of the 70 neutral runs, where the bar allowed 2.

In the spots world the expected direction held, but against neutral runs showing almost no change by these tree measures, so that pass says little. Neutral and treatment worlds also differ, by world, in size, in how many lineages they hold and in how many mutations they mint, and those differences alone separate them; a neutral comparison matched on size and lineages is needed before a tree measure can mean selection. Nothing was dropped to rescue a measure. Exploratory, computed from runs already on disk with no new simulation: a result about the measures, not about the worlds.

Unclear · 18 Oct

How long a stone stays findable

The shared garden plans to let visitors drop stones: wounds of a chosen size. This test, its rules written down before it ran, asked how long one stays findable in the big storm, founded as the garden’s commons would be. Twin worlds were forked from three early checkpoints of each of three seeds, identical but for one stone. At each census, every 1,024 steps, the twins are compared by the share of cells, living in either, whose lineage label differs. A stone’s horizon is the first census from which that share in the patch around it (a disc twice its radius) is no larger than in the rest of the jar, four censuses running. The prediction, written on 9 October, was that a radius-8 stone fades within about 13,000 steps, the time in which the storm itself wounds each cell about once. By the rule it fails: the median is 97,279 steps over 9 pairs, and 4 of them had not met the rule when the window closed, one sun wander after the stone. Stones of radius 32 and 64 read by the rule as marks with no lasting effect, with medians of 26,623 and 35,839 steps. Both are under one wander, so the garden’s provisional day of one wander stays.

The rest of the jar drifts from its twin fast: it is at least nine tenths different within 5 to 20 censuses in 23 of 27 pairs, and after census 16 both regions read 0.99 or more in 759 of 1,089 censuses. The measure saturates, and a small patch reaches its ceiling more easily, which is why radius 8 runs longer than 32 and 64. So these are the rule’s outcomes, and what they say about how long a stone stays findable is unclear. Three seeds, one of them a carpet (97 to 99% of the jar living); one of the first three seeds had died out before the first checkpoint and was replaced. Nine pairs per radius. “The sun is the first letter” is the rule’s branch, not something the measure showed. The rules were not committed before the run, so git alone cannot show that they came first. A catalogue test, not registered; it ran locally in 3 h 48 min and changed no garden setting.

Measured · 18 Oct

A stone against a nudge

Two controls followed, forked from the same nine checkpoints (three from each of the three seeds), their rules fixed before they ran. A null stone was the same wound dropped on a disc chosen so that it would change no cell. All 7 such twins stayed identical to the undisturbed world at all 16 censuses checked: radius 8 at 5 of the 9 checkpoints, and radius 32 at 2 of the three seeds’ first checkpoints, the only ones with such a disc that large; none had one of radius 64. A one-cell nudge, which removes no biomass, stood in as the smallest change. Read in patches the size of each stone’s own, its median horizon was 1,023 steps against the radius-8 stone and 9,215 against radius 64, under half the stones’, so by the rule both radii read as stone effects. At radius 32 it was 30,719 against the stone’s 26,623, so by the rule that radius reads as a divergence clock: the horizon times how any difference spreads, not the stone. None of the three readings is firm: checkpoint by checkpoint, the nudge lasted at least half as long as the stone at 4, 5 and 5 of the 9 at radius 8, 32 and 64. The split is by day: at the first checkpoint the nudge was under half the stone’s in all three seeds at every radius, and at the two later ones it lasted at least half as long at 5 of 6 checkpoints at radius 32 and 64, and 4 of 6 at radius 8. Censused every 64 steps through the first 8,192 steps after the first checkpoint, each stone’s patch ran ahead of the rest of the jar, summed over that window, by more than twice the nudge’s at radius 8 and 32 in all three seeds, and at radius 64 in 2 of 3.

The nudge clears one cell that holds no biomass but that the physics still counts as living, and its patch is centred there, not where the stone fell, so “stone effect” could be the size of the change alone. A stone removes the bodies in its own patch, so a larger early difference there is close to what a stone is. The null stone checks the plumbing of a scheduled wound, not “the act of intervening”: a wound that writes nothing intervenes in nothing. In one seed the nudged twin’s lineage labels first differed from the undisturbed world’s at the 26th of the 128 fine readings, at all three patch sizes, though the two worlds’ states already differed at the first census. The fine census covers the first checkpoint only; at the two later ones, a stone is not shown here to be more findable than any other change. The rules were not committed before the run, so that they came first rests on hashes of the note taken at the time, not on a commit, and the nudge cells and null discs were chosen, from the checkpoints alone, before the rules were fixed. The same three seeds and nine checkpoints as the first test; a catalogue test, not registered. It ran locally in 1 h 35 min; the garden’s day stays one wander and no setting changes.

Day by day

How we got here

  1. The sun letter, in the code: a logged change to the light for a span of steps, which scales the world’s light settings to half or three quarters, or, where a world’s light allows, to a quarter or a half more (on most worlds it can only dim, and none yet takes the brightest), after which the world’s own light returns. Matter stays closed and a replay is exact: in runs on our machines, in a Sun tool in the lab beside Wound, Feed and Drain, and in the shared garden as a letter that shines for one garden day; such a day goes only to islands that say they can replay a sun. The big storm takes the two dimmer settings. A keeper can found a garden without sun letters; by default it takes them. No garden is planted, and its page stays unlinked.
  2. The meteor, in the code and off unless a keeper founds a garden with it: a rare large stone, of radius 64 by default, which clears 12,853 cells, about 5% of the big jar. By default it lands only when visitors on 5 different networks ask within one dawn (until the garden sees visitors’ own addresses, every visitor counts as one network, so it could not land yet), at most once every 7 garden days (a keeper can set both at founding), at a place fixed by a public rule before anyone asks, never one a visitor picks. A hand carries nothing, and hands are kept only as salted hashes in memory. For a meteor of radius 64 on the big storm, the garden page gives the stone tests’ readings as what their rules said, with their caveats, and it always says the name promises no lasting change. No garden is planted, and its page stays unlinked.
  3. In the site’s code: a Feed or Drain refused on a pond world now says why and the world keeps running, instead of reading “World stopped”; Pond keeper’s log of firsts and family tree come back when a world saved after this change is restored after a reload; and the Worlds catalogue’s notes caught up with the results of 17 and 18 October.
  4. How long a visitor’s stone stays findable in the big storm, tested with rules fixed before running, then against a stone that removes nothing and a one-cell nudge. By the rules the prediction for a small stone failed, but the jar drifts from its twin so fast that what this says is unclear. The garden’s day stays one sun wander.
  5. A dated status page for the seven apps on main (the lab, the public site, the archipelago, the shared garden, the naturalist, the evolution game and the research instruments): what works, how to try each one locally, and what waits on a decision.
  6. Getting ready to open the shared garden, without opening it: a checklist of every decision and step, each with a recommended default and its evidence; and a founding script that only rehearses unless told, twice, where to send. Nothing is deployed, and the garden is not open.
  7. In the site’s code, not yet on cadence.garden: each field note in the lab now carries the proposer’s suggestion beside it, written by fixed rules, with a prediction that can be checked on our machines, not by Try it here, and the commands that would run it there. A Try it here button applies its feed, drain or wound once, and only on your click; the notes then stop, as after any change by hand. A suggestion carries no score and its prediction is not yet measured: whether the rules beat random choices is the bench’s question, and the bench has not run.
  8. Field notes in the lab, in the site’s code and not yet on cadence.garden: beside a running gradient or spots world, the bell scores each census against neutral runs of the same world, at the rule fixed for that world beforehand, and files a note with its receipts when it rings. Code writes the notes, not a model. A ring says the world differs in kind from neutral runs, not that something arose inside it, and the notes stop once you wound, feed or drain the jar. Other worlds say the naturalist has no baseline for them yet.
  9. Dawn predictions, in the code: before a shared garden’s next day is released, a visitor can guess which line (a lineage counted with the mutants born in the day being predicted and the day before, each going to the nearest of the three biggest it descends from; older mutants count with the rest) will hold the most of the field at that day’s end, or that the rest will. The guess is kept as a receipt on the visitor’s own device and sent nowhere; when the day is verified, the page checks it against public numbers that a second island regenerated. There is no prize, and since the physics is exact anyone can replay the day early, so a receipt is for fun, not proof of foresight. No garden is planted, and its page stays unlinked.
  10. An experiment proposer, written in code and not a model, turns a bell’s ring into a proposal: rerun a copy of the run, identical up to a chosen step, then add a feed, a drain or a wound there, or change nothing as a control where none of those would test the signal, with a prediction that can be checked; only a person’s yes runs one. A bench to test its proposals against random ones has its rules fixed: from each of 10 recorded histories, one rerun follows the proposal and three follow each of two kinds of random choice, 70 reruns in all. Each kind is judged on its own: the proposal’s rerun must depart further from the original, early on, than the middle of that kind’s three in at least 9 of the 10 histories. A larger departure is not a better experiment, only a test that the proposals aim somewhere. No proposal answering a real ring has been approved or run (only test reruns on made-up rings have), and the bench has not run.
  11. The public pages and the lab were checked with the keyboard and an accessibility scanner, at phone and desktop widths, in day and night colours, and what the checks found was fixed or, where the scanner could not decide, reviewed by hand. An unknown address now gets a real not-found page. All of it is in the site’s code, not yet on cadence.garden.
  12. Running the archipelago: an operator page showing gardens, bred runs, limits and failures in one place; islands that stop cleanly mid-run, so their piece of work is offered again; and coordinator settings checked when it starts. In the code; the live coordinator has not been updated.
  13. The lineage report, a local analysis tool, now draws a pond-cycle line’s route: each mutation in its pond and cycle, and each crossing between ponds marked “named” (the record of what crossed names the ancestor), “not excluded” (what crossed could hold the ancestor without naming it) or “not recorded” (there is no such record).
  14. A garden can take food, in the code: by default a feed lands only when visitors on five different networks ask within one dawn, and no more than once in any 7 of the garden’s own days. It is off unless a keeper founds a garden with it, and the garden’s plumbing was tightened too. No garden is planted, and its page stays unlinked.
  15. Pond keeper v2 adds a family tree, with families told apart by descent rather than likeness and marked “seen, not measured”, and five new pond firsts, from a moving pond to a pond that outlives a wound; built for the lab, awaiting deployment. A playtest kit for three newcomers, written for the version before, has what counts as a pass fixed before any session. In its walkthrough on one seed, ten entries were in the log of firsts by step 8,600, three of them already there when watching began, so most would arrive during the kit’s first task, which asks players to start the world, say what they see and change nothing yet. No session has been held.
  16. The bell’s second version, its scoring rules fixed before 120 local runs, is quiet on fresh drift, falls short of its bar on wounds and feeds, and its model part has not run.
  17. Three measures read from the mutation tree: none passed the checks, fixed before computing, for a measure of selection.
  18. Bred worlds can go to the archipelago: a breeder world can be split across islands, checked by replay and stitched like any other run, and in a test through two islands the stitched record equalled one continuous run. Only worlds bred by the rule are covered; hand picks stay in the lab. In the code; the live coordinator has not been updated.
  19. The lineage tool, run on our machines rather than in the lab, now opens dossiers on pond-cycle runs: each line of descent is walked back through the run’s own record of which pond seeded which. In the two short test runs kept as test files, all 379 walks were exact.
  20. Release checks for the public site, the local half, none of it deployed yet: the public status reports aggregate counts and their update time, each island’s requests for work and for its segments are rate-limited, its pending work is capped, and a per-address join limit is built but stays off until the checks that need the live host pass.
  21. The shared garden gets its machinery, in the code and not on this site: a coordinator that releases at most one day of a shared world per dawn, letters that drop a stone into it, a public count of the islands tending it, their kinds of device and the days a second island checked, and a way to stitch the checked days into one record. In one small test world, the stitched record files matched a single continuous run’s, byte for byte. No garden is planted, and its page stays unlinked while there is nothing to tend.
  22. A field notebook, a tool run on our machines rather than a page on this site, turns one finished run into field notes with receipts. Code writes them from the bell’s rings above the calibrated thresholds; no model writes a word, and the notes say the bell has not been shown to hear something arise inside a run.
  23. Pond keeper is built for the lab, awaiting deployment: a log of firsts (first body, first split, first grandchild…), a session card, and a session file that replays to the same final state. Then a pressure dial for the breeder, auto-breed, keep a lineage, and a What’s next? ladder. No physics changes; the dial is logged so a replay in the lab holds.
  24. An anomaly bell, its rules fixed before it ran, reads 85 finished runs and rings on drift: 30 of 70 neutral runs, where its bar allowed 2.
  25. A second gene, polymer building, fails against its own control: a do-nothing build gene reaches about half the cells in two of three null seeds, so the run reads confounded. The kernel’s capability genes become a named set that can grow.
  26. A genome gains its first gene. Decomposition as a paid capability sweeps where it pays and lingers at a few percent where it does not — and the world it wins becomes a decomposing film. A dated note asks what a game of evolution would take.
  27. The lab’s world can go full screen with just the cells: a button beside Fit view or the f key, Esc or f to leave, and the view you zoomed or panned to survives the exit. Nothing in the simulation changes.
  28. The site counts visits with its own analytics, shipped in its own files: no cookies, no script from another host. The About page now names the gardener.
  29. Every world gets a catalogue card, its own link and preview, and a plain name you can say aloud: the Worlds catalogue says what each one asks, how it differs from its base world, what to look for, and what has been seen so far, in the same labels as this journal. The lab opens on a fresh seed unless the link names one.
  30. The project becomes Cadence Garden: every world a sealed jar under a lamp, the lab the bench, the site the garden around it. A new Light view draws the light the physics uses.
  31. Breeding by hand reaches the lab: stop at each pond cycle, pick the donor ponds, confirm, and watch the next generation. Storm worlds are in the lab too.
  32. A renewal experiment closes as a negative: none of 24 pilot cases qualified as a self-renewing habitat. A new discovery workbench imports its audited records.
  33. A broader creative direction: follow promising behaviours, combine environmental levers and breed toward visible traits. Storm worlds and a breeder start in a development sandbox; an AI naturalist and a persistent shared garden are future ideas.
  34. The registered pond test confirms both primary hypotheses on 24 histories per arm. The test of how much the genome carries is not confirmed.
  35. The transition hunt passes its entry checks. Its evolutionary stage is prepared, not run.
  36. Two protocols are frozen before their data: the pond registration and an exploratory hunt for ponds that select themselves.
  37. The decisive pond test replicates on fresh histories (6 of 6). Next: integrate the pond cycle, then draft a registration.
  38. A fresh pond-heredity test, fixed before any data, shows heritable differences between ponds in 6 of 6 histories.
  39. The first pond-heredity test is not demonstrated (0 of 6), and an adjusted reading made afterwards falls short too (3 of 6, with 4 needed).
  40. Founder recipes tested: drifted clouds, sets that leave a niche empty, and screens in conditioned media. Whether new roles keep arriving reads mixed.
  41. Tracked births fail a direct copy check in 135 of 200 samples, so tracker parenthood is no longer taken as evidence of reproduction.
  42. A 10⁷-step extension repeats M4: mutation beats both controls, and neutral runs also count as growing.
  43. A review of the foundations points at variation: mutation rarely changes what a genome does in the world. A founder diagnostic finds that how the founders were chosen is a major bottleneck.
  44. The M4 ensemble completes and M4 is not met. A time-boxed foundations review replaces scaling up.
How we check