Product model
How Lamarck works
Lamarck keeps your history continuous while the software around it changes. The complete product model is one Timeline and one evolving System Shape.
Two sides of one personal system
Your Timeline is the durable history of what happened. Your System Shape is the current arrangement that can observe, understand, and act on that history.
Timeline
Events from the world around you and meaningful activity inside Lamarck.
System Shape
Sources, Apps, Documents, Tables, and the permissions between them.
Timeline
The Timeline is a local, append-only sequence of Events. Events come from Sources and from meaningful activity inside Lamarck, including Apps and the system itself.
Because new software reads the same continuous Timeline, it can begin with earlier context rather than treating installation day as the beginning of your life. Replacing an App changes what happens next; it does not rewrite what already happened.
System Shape
System Shape describes what Lamarck can currently perceive, what software it can run, and the human-readable and structured state that software maintains. It is made from four primitives.
Source
Where Lamarck can observe or interact with the world around you.
App
Software that queries your Timeline and performs authorized effects.
Document
Human-readable current state, represented as plain Markdown.
Table
Structured current state, represented as real SQLite tables.
Connector / Source
A Connector is how Lamarck observes and interacts with the external world—the devices, services, and interfaces around you. Mac AX captures your desktop work context, Oura collects health and recovery data, and a Telegram bot brings conversations into your Timeline and lets Lamarck respond. Configuring a Connector creates a Source; new integrations can be added through the same Connector interface.
App
Create full-stack web apps, long-running processes, Event-triggered automations, and AI agents inside Lamarck’s secure App sandbox. Apps can query the personal data in your Timeline. Explicit permissions control the durable Tables and Documents they can change, while the sandbox prevents broken or hostile code from reaching host files, credentials, other Apps, devices, or unrestricted network access.
Document / Table
Timeline holds history. Documents and Tables hold current state that people, AI, and Apps can update as work continues.
Document
Human-readable state such as a weekly review, project brief, or long-term plan. Every Document is a normal Markdown file you can read and edit with Obsidian, VS Code, or any editor you like; changes sync both ways with Lamarck.
plain Markdown · .md · two-way syncTable
Structured state such as habits, contacts, or health summaries. It remains directly queryable with ordinary SQL.
SQLite · SQLHow the pieces work together
A new observation grows the Timeline. Software queries that history, then produces useful actions or current state through authorized effects. Adding that software changes the System Shape.
Use Lamarck with any AI
You do not need to manage Lamarck's Sources, Apps, Documents, Tables, schemas, or permissions by hand. Install Lamarck Skills, then use ChatGPT, Claude, Gemini, Grok, or whichever AI you prefer to manage and use Lamarck.
Ask for what you want in natural language: “Build a weekly review that connects my sleep, work, and commitments.” Lamarck Skills teach your AI how to query your Timeline, understand your System Shape, and use Lamarck's interfaces to reuse or create what the request needs.
Your AI handles the system mechanics. Lamarck still enforces every query and change through its System APIs, sandbox, and Guard.
Need exact guarantees and implementation status? Continue to the System model documentation.