Previously on Lifelog…
The Vampire’s Palette was deployed. OLED black consumed production. 3,887 lines were deleted. The void was pleased.
But in the shadows, something stirred.
The Reluctant Founder’s Lament
“Surely someone has built this already.”
tries Capacities — too rigid
tries Orca — data model says no
tries Timestripe — close, but not flexible enough
“…fine, I’ll do it myself.”
But then: a whisper from the reptile brain.
“What if you… don’t?”
The Wolf-Scaring Revelation
Flashback to the weekend. Between kombucha bottling and a chicken that could intimidate apex predators, the architecture crystallized:
9 AM: “What if lifelogs are entangled?”
9:15 AM: “Wait, that’s basically quantum blockchain”
9:30 AM: “Wait, I invented this 2 years ago and forgot”
10:30 AM: “It’s novel synthesis. Ship it.”
But where to ship it?
Enter Ian: The 90% Prompt Prophet
A friend in Uganda. A non-programmer. Building apps that are 90% prompts, 10% vibes.
The LLM is the logic layer.
The reptile brain nodded. The frontal cortex (augmented by 50,000 GPUs in the cloud) took notes.
The Conspiracy
What if Dialogr v3 doesn’t integrate with Lifelog?
What if Dialogr v3 becomes Lifelog?
You write → Entry appears
↓
Agents wake (background)
↓
┌─────────┼─────────┐
↓ ↓ ↓
Lengthen Connect Parse dates
↓ ↓ ↓
└─────────┼─────────┘
↓
Entry enriched, linked
↓
View as: Chat | Kanban | Timeline | Calendar
Instant capture. Background crystallization. The agent does the work while you keep writing.
But Wait, There’s More
Imagine one of the agents is Claude. With full lifelog access. Able to write plugins in WASM or Go. And load them into the running system.
The agent that builds itself.
You write: “fix sqlgen bug (Saturday)”
Claude:
- Sees the temporal binding
- Clones the repo (Tuesday)
- Writes a design (Tuesday night)
- Creates a task for you to review (Wednesday)
- You approve
- Claude deploys (Thursday)
- Saturday arrives, bug already fixed
- Entry auto-completes
The calendar becomes a command queue. Time becomes agency.
The Business Model
Sell Lifelog? Never.
The plan is simple:
- Build the substrate
- Capture the stories
- Let the agents enrich them
- Wait for Hollywood to call
- Sell the movie rights
“The Vampire’s Palette: A OLED Love Story”
“The Rocket That Flew: An Unlikely Component’s Journey”
“The Chicken That Scared Wolves: A Culinary Thriller”
Coming to theaters 2027.
Status
- Lifelog: becoming unnecessary (in the best way)
- Dialogr v3: absorbing everything
- Agents: soon to be self-extending
- Movie deal: pending
- Vampire: still in charge of palette decisions 🧛
- Reptile brain: validated once again 🦎
The Wisdom
You don’t build the thing you want to build.
You build the thing that teaches you what to build.
Then you build the thing that contains everything.
Then you make a movie about it.
The conspiracy continues…
See also:
The Saga (in which conspiracies unfold):
- The Vampire’s Palette - The OLED darkness that preceded the conspiracy
- The Polishing Daemon - The evening session that followed
- The V3 Saga Of Quantum Blockchains and Wolf-Scaring Chickens - The weekend that started it all
The References (conspiracy validated):
- WebAssembly - Where agents might compile themselves
- Temporal.io - Time as a first-class citizen in computing
- The LLM is the Logic Layer - When 90% prompts becomes architecture