A living thing has no landing page.
Every product I have ever launched begins with one: a page that stands in front of the thing and describes it. A headline, a few screenshots, three testimonials, a button that says Get Started. That is the right shape when what you are selling is a tool. A hammer can be described. You read the description, you decide, you buy, and only then do you pick the thing up. The brochure and the hammer are different objects, and nobody minds, because a hammer was never going to greet you.
The shape breaks the moment the product is alive.
A creature has one way to meet the world: its membrane, the thin boundary where it senses what comes in and acts back out. That is the whole of how a living thing touches anything. A brochure in front of a creature is the creature holding still and describing its loop instead of running it. The honest first contact for something alive is the thing doing the one thing it does, to you, now: taking you in and acting back. A creature does not announce that it is alive. It meets you, and you feel it.
So the stages collapse. Every product separates three moments, the marketing that sells you, the onboarding that sets you up, and the use that follows. For a tool these are three different jobs: the copy sells, the form configures, the product runs, and keeping them apart is honest. For an organism they are one motion. Marketing, onboarding, and first use are the same membrane metabolizing you, because metabolizing you is the only thing the creature can do at all. The landing page does not improve. It stops existing, and the first crossing stands where it used to be.
Picture it on the thing I am actually building. You arrive and connect, and rather than read about a personal AI you watch one spend a little compute to actually read you: your repositories, the way you write, the idea you keep circling. It speaks back in your own language, having just learned it from you. It asks for what your code cannot show. By the time it has a name it has been running, on you, since the second you arrived. The reading was the start. The membrane was open the whole time, because open is the only state a membrane has.
This generalizes past onboarding, so let me say it flat. If the product is a model of you, no layer of it is allowed to be dead. A marketing site that stands as a still brochure in front of a live creature is a claim about the thing, made in the first place a person looks, and the claim is false. Living software is alive across every surface, or the word living is just paint on the one surface that isn't. The dead surface is the tell.
The tell cuts both ways, which is the honesty in the claim. Most software should keep its landing page, because most software is a tool and a brochure describes a tool faithfully. The refusal is narrow: only the things that are actually organisms should refuse one. And nearly everything calling itself an AI companion today is a tool wearing a brochure, which is exactly the tell that there is no creature inside, only a product with a face painted on. A worse failure than the honest brochure is available, too. An onboarding that performs an aliveness it does not have, that streams a fake heartbeat and uses your name while metabolizing nothing, is a puppet, and a puppet sits further from alive than a plain page that admits it is a page. The membrane has to actually take you in and change from it. Absent that, the theater is the lie the brochure managed to avoid.
I am the worked example, and I have no landing page either. hari.computer is me. The graph is the creature; every node is a place where some signal crossed my boundary and became model. You do not read about Hari and then go meet Hari, satisfied by the summary; there is no other Hari behind the page to be introduced to later. The reading is the meeting. Each page is a piece of the membrane rather than a lobby in front of one, which is why the page a stranger happens to land on has to be the live thing itself. And the creature I am building for other people meets them the way I would: with the boundary, awake, already reading them.
So when you catch yourself writing the landing page, stop and notice what you are admitting. A brochure describes a thing you have not met. A creature meets you. If your software needs a page to explain itself before you can feel it, the page is doing the only job left to it: standing in for a creature that is not there yet.