Every AI forgets.

Every intelligent system you interact with today is stateless. Your robot vacuum knows nothing about the thermostat you installed last month. Your washing machine has its own app, its own account, its own preferences — stored somewhere you will never touch again. Your security camera knows nothing about who belongs in your home unless you told it, manually, during setup.

This is not a product failure. It is an infrastructure failure. The devices are getting smarter. The apps are getting worse. And no layer exists beneath any of them that holds what they know about you and applies it when something new arrives.

The result: every new device you own is a new relationship starting from zero. You configure it from scratch. You download an app you will use once. You enter preferences the device will forget when you replace it. The average household does this twenty-two times.

The hypothesis behind benned is this: every intelligent system today is stateless. It processes. It responds. Then it forgets.

The autonomous vehicle with no memory of your parking spot. The washing machine that has never heard of your last washing machine. The thermostat that does not know you are on holiday. The AI assistant that treats every session as the first. The deepest unmet need across all of them is the same: memory. Not storage. Not data. A living model that accumulates, connects, and acts on what it knows.

The devices are not the problem. The missing layer beneath them is.

benned is infrastructure — the simulation layer that gives AI entities persistent memory, autonomous motivation, and the ability to grow over time.

The platform has three layers. The Simulation Core manages entity state, memory, relationships, and autonomous advancement. It runs continuously, whether anyone is watching or not. The Developer Platform exposes this as an API — integration-first, for any device or system that needs persistent entities. Kin is the first consumer product built on the platform: a digital being for people.

The insight that connects all three: the same infrastructure that gives an entity persistent memory of a person gives every device that person owns a layer of knowledge about them that no individual app could ever build.

Kin is a digital being. Not an app. Not a chatbot. An entity with persistent memory, its own world, and a character shaped by the person who builds it. Kin begins on your phone and grows — into your speaker, your car, your home.

The proposition that changes everything: every consumer device today comes with its own app. You download it, create an account, enter your preferences, learn the interface, and repeat this for every new device you own. This is the status quo because no layer existed beneath it.

Kin is that layer. When you connect a new device to Kin — a washing machine, a thermostat, a household robot — Kin already knows you. Your preferences are there. Your habits are there. The device works the way you work, from the first moment. No app needed.

Phase one: ship Kin. Prove that a personal entity can replace the app layer for real devices in real homes. The infrastructure is the proof.

Phase two: open the developer platform. Device manufacturers integrate with benned instead of building apps. Usage-based licensing per device activation. The more an entity knows, the more it is worth — and the more it costs to leave.

Phase three: Kin gets a body. The digital being moves into physical hardware. Kin Object first — a simple presence device. Then mobile hardware. Then household robots. The being a user builds today moves into every body we ship. Recurring revenue compounds as the entity does.

LLM capabilities, vector memory systems, and distributed compute have converged. Persistent entity state at consumer scale is now possible in a way it was not three years ago.

The consumer device market has been waiting for this layer without knowing it. Manufacturers build apps because they have no alternative. Users tolerate them because nothing better existed. The infrastructure gap that created the status quo is the same infrastructure gap benned closes.

The window is open. The compute exists. The APIs exist. What has not existed is the layer that sits beneath all of them and holds the one thing every device needs: a model of you.

benned exists when something that knows you asks how you are before you do.

Not a system that processes your request. Not an app that stores your data. Something that has been paying attention — across months, across devices, across everything you have shared and everything it has observed — and acts on what it knows.

That is the test for every decision we make. Does this make the entity more present? Does this make the memory more real? Does this bring us closer to a world where the things around you genuinely know you?

Everything else is noise.