Jeff Ellis
What I'm Building

The flagship build

Lyrn

An AI-native operating environment for the enterprise.

In active development

The two parts

Lyrn OS

The operating environment.

The layer where applications, tools, and operators run against one shared context. It is where the work actually happens, and where every action reads from and writes back to the same memory.

In development

Lyrn Memory

The persistent memory layer.

The foundation everything else stands on — persistent organizational memory infrastructure that is LLM-agnostic and hierarchy-aware. It currently operates as MemoryStack.

Currently operating as MemoryStack

MemoryStack.net

The problem

Every enterprise I have worked inside runs on the same setup: dozens of tools that do not talk to each other, data scattered across systems that were never meant to share it, and institutional knowledge that lives in people's heads and walks out the door when they do.

AI does not fix that on its own. Bolting a model onto a broken foundation gives you faster access to the same disconnected mess. The model forgets everything the moment the conversation ends, so nothing compounds.

The idea

Start with memory, not the model. Give the organization a persistent, shared layer that remembers context, decisions, and outcomes — then build the operating environment on top of it so every tool and every operator works against the same source of truth.

That is Lyrn: an AI-native operating system for the enterprise, where the advantage lives in the memory and the architecture, not in whichever model happens to be best this quarter.

What I built

Lyrn has two parts. Lyrn OS is the operating environment — the layer where applications, tools, and operators run against one shared context. Lyrn Memory is the foundation underneath: persistent organizational memory infrastructure that is LLM-agnostic and hierarchy-aware, so memory is organized the way the business is, from the individual to the team to the division.

Lyrn Memory currently operates as MemoryStack, the first productized form of the memory layer. Lyrn OS is in active development.

How it works

Everything reads from and writes back to the memory layer. When an application does work, the context and the outcome go back into memory, so the next interaction starts from what the last one learned. The models sit on top and stay swappable — the durable asset is the accumulated memory underneath them.

Because the memory is hierarchy-aware, access follows the structure of the business. People and applications see what they should, and knowledge accrues at every level instead of pooling in one place.

The outcome

The work is ongoing and I am building it deliberately. Lyrn Memory is live in its MemoryStack form. Lyrn OS is coming together as the environment that runs on top of it.

What I am learning

The hard part is not the model. It is the memory, the access model, and the discipline to build the foundation before the features. Most AI programs start at the wrong end and stall. Lyrn starts at the foundation on purpose.

See the rest of what I am building.