AN AI-FIRST HOME.
ONE BRAIN, EVERY ROOM, EVERY HOUSE.

One assistant, every surface

Web, iPhone, iPad, Mac, voice, Siri Shortcuts. Same session, same memory: ask in the car, continue on the couch.

Generative UI

Woodhouse renders what it means — a day schedule, a chore ring, a board preview, a device card — and the app draws the same card natively.

Lock-screen decisions

“Can I go out after school?” arrives as YES / NO. A dinner time proposal arrives as ACCEPT, with Woodhouse having already checked both calendars.

Latency you notice

The owner runs on the newest Grok the AI Gateway offers, tuned for first-token speed; the physical board, the pool and the thermostats respond in about a second from the app.

Reflexes, no model at all

“Poles off.” A short command that plainly names a light, a scene or a routine is matched by Jev — a decision model that answers in a third of a second and writes no prose — and runs directly. Anything with a question, a time or a second step goes to Woodhouse as usual; the gate never runs this way.

Live boards

Chores (a tile per task: green done, black not yet, red late), today's calendar, who's home, the points leaderboard — rendered from house data the moment you ask.

Artwork

GPT-5.5 paints 6×22 pixel art from the eight tile colors; Woodhouse shows the preview in chat and sends nothing until you say so.

Saved boards

Name one and anyone in the family can put it up — “the welcome board”, “the birthday board”.

An eve extension

The board ships as a proper extension: tools, a composition skill, a rate guard, and hooks the host uses to mirror every send to Cortex.

Triggers

Arrive or leave a site, first person home, last person out, a time on given days, or manual — including Siri Shortcuts.

Conditions

Who's present, who's absent, a time window, a day of the week.

Actions

Notify, Sonos, lights, a delay, the gate (approval-gated), and any Cortex scene on every open screen.

Dry runs

Every routine can be rehearsed: the trace shows each step and what it would have done.

A whole game first, then small steps

“A ship that dodges asteroids, with a score.” About a minute later it's playable in the preview — controls, collisions, score, game over. “Make the ship faster” edits the same files. Undo puts it back.

Explained, not dumped

The builder never pastes code at a kid. It names one idea per turn — a variable is a labeled box, a loop repeats — and “explain it like I'm not an engineer” walks through the whole game without changing a line.

Sandboxed, family-only

fx is fenced in a throwaway microVM with the project folder as its whole world; games are stored privately and reach the kids only through the family's own sign-in, never a public URL. Publishing to the web is a parent's later decision.

Guardrails a parent set

Plain HTML/CSS/JS only, no network calls, kid-safe content rules the model follows and the house double-checks, every build load-tested (a crash goes straight back to the builder to fix), a middle-school guide with three example games, and per-kid daily, weekly and monthly caps — in builds or in dollars — that a parent sets.