Product essay / 001
Introducing Lamarck
A personal system that can evolve without forgetting you.
Personal software has an odd failure mode: every new tool asks you to become a new person. The habit tracker begins at day one. The journal has never met you. The new AI assistant remembers nothing that happened before the first prompt.
You can export the old data, learn an API, or spend a weekend rebuilding context. Most people do none of those things. They start over, keep the old app forever, or stop recording altogether.
Every app starts empty
Personal apps become useful slowly. A sleep dashboard matters after months of sleep. A journal becomes meaningful after years of entries. A planning assistant improves as it learns how work, health, and commitments affect one another.
Yet all of that accumulated usefulness is usually trapped inside the application that collected it. Choosing better software means abandoning context or attempting a migration that was never designed to be complete.
Today
Each app owns its own slice of you.
With Lamarck
Apps come and go above one continuous personal history.
Interfaces are becoming disposable
AI is making software dramatically cheaper to create. A tracker for one particular condition, a dashboard for one project, or an agent for one recurring task no longer needs to justify a large market before it can exist.
That should make personal software more adaptable. Instead, the old ownership model turns every new interface into another silo. We can generate an app in an afternoon and still spend days teaching it what the previous app already knew.
Interfaces are becoming disposable. Your history is not.
History should outlive the app
Lamarck begins with a different boundary: durable personal history belongs to the system beneath the apps, not to any one app above it. A dashboard can be replaced without replacing the years that made it useful. An automation can disappear without taking its evidence with it.
This is also why Lamarck is local-first. Continuity should not depend on one interface remaining fashionable, one company remaining available, or one cloud account continuing to exist. The durable layer should live on a machine you control.
New software should inherit you
A weekly review should be able to begin with the work, sleep, plans, and conversations that shaped the week. A travel planner should not need your preferences explained from scratch. A new AI agent should be able to continue a job without turning the first conversation into onboarding.
This does not require one permanent super-app. It makes smaller, more specific software viable: the interface can be temporary because the context beneath it remains continuous.
A personal system that keeps changing
Lamarck calls the durable record of what happened your Timeline. The software currently arranged around it is your System Shape. One accumulates as life continues; the other can change as your needs change.
That is the reason Lamarck exists: software should become easier to replace without making your life easier to lose.
How it works
This essay stops at why. Continue with How Lamarck works for the complete product model, or read the System model documentation for exact contracts and implementation status.