Devblog

The build, as it actually happened -- including the parts that broke.

The polish pass, and a confession about the finale

The season got reordered so it teaches before it tests, death screens stopped being skippable by accident, bedtime got its glow -- and our test robot just admitted it cannot beat our own final room.

The boxes grow legs

The sitter and the kids are no longer rectangles. On silhouettes at sixteen pixels, seeded wear and tear, a sleeping frame that had better look like sleeping, and the house finally moaning about it.

The fridge is real

Every object the intercom has been talking about now exists on screen -- the fridge, the coathook, the door you must not knock on -- all generated from code, none of them allowed to look like anything that matters.

Seven rooms, and a jailbreak from our own law

Three new rooms built entirely from mechanics we already shipped, a difficulty pass with meaner tolerances -- and the embarrassing discovery that the narrator's script was violating this project's one commandment.

Trust no unit

The modern CSS unit that exists to solve the mobile-fit problem did not solve the mobile-fit problem. A two-paragraph sequel about asking the browser a direct question instead.

Losing the chrome

Beta report two — the game didn't fit on phones, because a CSS unit lies on mobile. On forcing fullscreen where the web allows it, begging where it doesn't, and an icon drawn in twelve pixels.

The intercom gets a name

The first beta note said the narration was "mindless chatter with no lore behind it." Correct. A confession about writing a voice before writing a person, and the season-long script that replaces it.

The house works sideways

The game now plays on phones — landscape only, thumbs only, and a rotate card that tells you exactly one thing. Also, two bugs that had been waiting all week for a narrower screen to walk into.

The door with the password

A closed beta exists — one gated door, no announcements, and a 401 page that stays in character. If you have the password, you know who you are.

The house hums

The game now ships zero audio files and is no longer silent — a mains-hum drone, a hum we don't discuss, and a music box playing a lullaby that never repeats, all synthesized from math the moment you clock in.

The house gets its glow

The ugly-on-purpose era is over — scanlines, grain, phosphor amber, and a shade of green reserved exclusively for people who are no longer using it. Plus the second genuine engine bug our robot has caught this week.

Four rooms in the bank

Episode four introduces the second child, and the season hits its required minimums of fridge, hum, and water-damaged paperwork. Also: why this game will never announce a release date, as a design decision with teeth.

Rooms are files now

The whole project rests on one bet — that shipping a new room must never require writing code. Today the bet became infrastructure: three rooms, one of them a trap the narrator personally recommends walking into.

The intercom crackles on

The narrator is in the building. He is very proud of his kids, he has opinions about the pantry wall, and following his advice is now officially how you lose. Also, drawing more text than ever before broke the font renderer, because of course it did.

Sixty-two seconds of bait

The first human playtest, on video — one immediate chase, one genuine death, one heroic dig, one seal spent on the wrong hole, and a door that was never going to open. This is exactly what we built the room to find out.

The game worked. The page didn't. Three times.

Ten green tests, two green builds, zero lint warnings — and the first human to open the page got a postage stamp and a dead keyboard. A confession in three bugs, and the robot we hired so there is never a fourth.

One room, one zombie, no engine

M0 exists — a single room, a single pursuer, two verbs, and a kill criterion that is allowed to cancel the whole game. Also, we died on purpose, for journalism.