Lab · Seen · build log

A cast that keeps living when you close the app

A messaging game where you text a cast of characters, except they also text each other, post, fall out, make up and remember you, whether or not you're watching. This is the running build log: what got built, when, and what I learned. Built alongside Claude Code.

12characters
16,750lines of code
27modules
1shared memory

Running totals · as of 5 October 2026

Not public. It runs on my own machine, against my own API key.
A note on this log

The Life Island log is generated from that project's commit history, which is why it can count hours and commits. This one is in a repository now, but as a single backup rather than a record of how the work happened, so there is still nothing to count. The dates below are real and the work is real, but you will not find hours on this page until that changes.

Chapter 2 · 25 September – 5 October 2026

It stopped being one world, and started looking after itself

The game tripled in size over a fortnight. The biggest change is that the cast and the setting are no longer baked in: you can build a world of your own now. It also learned to start without me, and grew a set of tests.

What got built

The log, day by day

25 Sep
Friday the big one

Worlds

  • The setting is no longer hard-coded. There is a wizard that builds a world: its premise, its cast, how they know each other. The original is now simply the first of them.
  • A switcher to move between worlds, and a migration that lifts everything already written into the new shape without losing any of it.
  • A character editor, so a cast can be changed without opening a JSON file.
  • It starts by itself. A launcher, a stopper, and a hidden startup task, because a game that needs a terminal is a game that gets played twice.

This was the day it stopped being my game about my setting and became something that could hold anyone's.

28 Sep
Monday the clear-out

Pulling it apart before it got too big to

  • A full refactor of the front end, taken slowly enough to keep a copy of everything first.
  • The screens split into real components instead of a few files that had quietly become enormous.
30 Sep – 2 Oct
Wednesday to Friday accounts, scenes, tests

Somebody else could run this now

  • Accounts, so the thing has an owner rather than assuming there is only ever one person.
  • Scenes: a conversation can now happen somewhere, and the place is part of the prompt.
  • The spend cap and the usage screen reworked around the new shape.
  • The first tests. Not many, but the engine, the scenes and the summarising now have something checking them that is not me playing it.
  • A written note of where the project stands, for whoever opens it next, including me in three months.
4 – 5 Oct
Saturday, Sunday the long weekend

Characters that keep their word

  • Promises. A character who says they will do something is now held to it, and it surfaces later. This is the feature I most wanted and the one I expected to be hardest.
  • Memory, meters and the tick all reworked against it, so a kept or broken promise actually moves where you stand with someone.
  • Tics: small verbal habits that make a cast sound less like one writer with different hats on.
  • Names handled properly, rather than assumed.
  • A time card on the world screen, and the Story view rebuilt around it.
  • More tests, including one for the thing that kept going wrong: conversations that never got summarised.
Two weeks in

What a fortnight of this changed

Three times the code

5,100 lines to 16,750, and 17 modules to 27. Most of that is worlds and the refactor. Some of it is tests, which is the first time this project has had any.

One memory for everyone

Every chat, meet-up and post goes into one journal the whole cast reads. What you tell one person can travel, and nobody contradicts what really happened.

The refactor earned itself back

Promises touched memory, meters and the tick at once. A fortnight earlier that would have meant editing three files that had each grown too big to hold in my head.

Still to come

What's next

  • A real development historyIt is in a repository now, but as a single backup rather than a record of the work. Until that changes this page stays written by hand.
  • Somewhere other than my PCIt runs on a machine in my flat and is played from my phone. That is a limit, not a design.
  • A world somebody else buildsThe wizard exists. Nobody but me has used it.
Chapter 1 · 12 August – 24 September 2026

From a chat window to a world that runs itself.

A scaffold in August that sat untouched for six weeks, then three days that turned it into something with a memory, an economy and a life of its own.

What got built

The log, day by day

12 Aug
The scaffold

A chat window, and then nothing

  • A backend, a client, and a character who could hold a conversation.
  • Then it sat for six weeks. It worked, but it was just a chat window — the characters forgot everything the moment you left.
22 Sep
Tuesday the rebuild

One source of truth

  • The World Journal. Every event in the world writes to one journal, and every prompt reads from it. This is the whole fix for the thing that ruined the apps I was modelling against: the story and the chat can no longer contradict each other, because there is only one story.
  • Memory. Every few turns, a cheap model reads the conversation and extracts what the character now knows about you, plus one sentence on where you stand. That sentence goes into every future prompt.
  • The world tick. Time passing generates private conversations between characters, posts, comments and unprompted messages to you. Never on a timer — only when you open the app after a gap, or ask for it. The world moving should never quietly spend money.
  • Situations. Events you write yourself that colour every prompt until you end them.
  • Relationships are a sentence, not a score. Rebuilt as meters two days later — see below.
23 Sep
Wednesday the cast

Twelve people, and the small things that sell it

  • Twelve characters, each with a history, a personality, a way of speaking, and opinions about the other eleven. The full portrait goes into that character's own conversations; a compact version goes to the narrator that runs the world.
  • Replies arrive as one to three separate bubbles, revealed one at a time, instead of a single essay. Cheapest realism win of the whole project.
  • Every message you send carries its real timestamp into the prompt, so characters notice it's late, or that you've been gone three days.
  • Per-character notes you can write yourself, which override everything else in that character's prompt.
  • Hand-drawn emblem avatars rather than faces — a deliberate choice, and one I'd make again.
24 Sep
Thursday the long day

Long memory, a self-moving world, and a budget

  • Long-term memory. Old journal entries fold into a rolling chronicle instead of being dropped, so the world still remembers last week without paying to re-read it every time.
  • The world moves on its own. A tick can now start its own situation or shift a relationship — nobody has to author every event. Come back after a day away and it runs the catch-up you missed.
  • A group chat for the whole household, which only fires when something actually happens. It stays quiet otherwise, on purpose.
  • A daily spend cap. Every action's cost is tracked and totalled; past the cap, everything optional is refused and only your own conversations still work. A usage screen shows today against the cap.
  • Meters — friendship and romance, 0 to 100, with named stages. I'd explicitly rejected points two days earlier and changed my mind, with one condition: every movement is logged with the reason it moved, and hurting someone moves it down. Everyone starts at the bottom.

The reversal is the honest bit. "No points, relationships are a sentence" was the right instinct about opaque scores, not about scores. A number you can see the reasons behind turned out to be the thing I wanted all along.

Lessons

What I learned building it

Memory is the whole game

Characters work like a person with notes: the recent chat in full, everything older boiled down. Getting what they keep right mattered more than any clever writing.

The sneaky mistake

Timestamps written as "5 minutes ago" changed on every single request, so nothing the AI had already read could be reused. Writing fixed clock times instead fixed it. A one-line habit with a real effect.

What went fast

The world tick, the chronicle and the safety limits each landed in a single sitting. Anything that is really just data moving between a database and a prompt goes quickly; anything that has to feel right takes three tries.

Still to come · as written on 24 September

What was next

  • Version controlSo this log can be generated from the work instead of written from memory, the way the Life Island one is.
  • One more characterDeliberately held back until the twelve already there feel finished.
  • Still movingWork landed on 25 September that isn't written up here yet.
Written from the work itself, 12 August – 5 October 2026 · Built with Claude Code.

← Back to Lab