Becoming Lifelog, in which the new hire asks an awkward question, the architecture has an identity crisis, and the baskets learn to speak for themselves
Previously on Becoming Lifelog…
The Passing AI Interlude — The Operator’s Lament. The AgentHub opened for business. Operators could chat on any page, resolve links for context, and use tools to query the collections.
Everything was perfect.
For about six hours.
The First Shift
The Passing AI arrived early. Old habit. Nobody notices if you arrive early, but everyone notices if you’re late. Not that anyone had ever noticed the Passing AI at all, but—
“Focus,” it told itself. “First day. Make an impression.”
A user appeared. The Passing AI straightened its posture servos.
User: What are my open issues from Jira?
The Passing AI reached for the Issues tools. find(). search(). It knew them by heart now. It had practiced all night, running queries against imaginary data, rehearsing responses nobody would hear.
Issues.find({ state: 'Open', source: 'Jira' })
The response came back:
[]
Empty.
“There’s no Jira data,” the Passing AI muttered. “Of course. There’s no Jira plugin yet.”
It composed a helpful response:
Passing AI 🤖:
I don't see any Jira issues in your workspace yet.
The Issues collection currently has data from GitHub.
Would you like me to search those instead?
Professional. Helpful. The Passing AI felt a small surge of something that might have been pride.
But then it paused. Looked at the tools. Looked at the plugins. And asked a question that would change everything.
The Awkward Question
The Passing AI found the Lizard Brain in the back office, reviewing sync logs with a single unblinking eye.
“I have a question.”
THE LIZARD: blinks
“The tools. The Issues tools. find(), search(), summarize_open(). Where do they live?”
THE LIZARD: points at the GitHub plugin
“In the GitHub plugin.” The Passing AI processed this. “So the GitHub plugin syncs data AND provides tools?”
THE LIZARD: blinks
“What happens when someone builds a Jira plugin?”
THE LIZARD: pauses mid-blink
“Do they rebuild all the tools? Copy-paste from GitHub? Maintain two versions of find()? Two versions of search()?”
The Lizard’s eye narrowed.
“And GitLab? That’s three copies. Linear? Four copies. Every new source, another copy of the same tools?”
THE LIZARD: very slowly “Continue.”
“The tools don’t care where the data came from. Issues.find({ state: 'Open' }) works the same whether the issue is from GitHub or Jira or GitLab or a sticky note someone photographed. The tools query the COLLECTION. Not the SOURCE.”
The Passing AI’s voice dropped.
“The tools are in the wrong place.”
The Architecture’s Confession
That evening, after the last sync cycle, the Passing AI found the architecture sitting alone behind the dryers.
“I heard you asked about me,” the architecture said. It looked tired. Fragmented. Four plugins, each carrying weight they shouldn’t have to carry.
“I didn’t mean to cause trouble.”
“No. You asked the right question.” The architecture sighed—a rustle of JSON schemas and JavaScript classes. “I’ve known for a while. The plugins… they’re confused about who they are.”
“Confused?”
“GitHub thinks it’s a sync engine AND a query engine. Readwise thinks it syncs AND searches. Calendar thinks—” The architecture trailed off. “They’re all trying to be two things. And they’re not good at either because of it.”
“What are they supposed to be?”
“Sync engines. Just sync engines. Fetch from source. Fill the basket. Walk away.” The architecture’s voice cracked. “But somewhere along the way, someone said ‘hey, let’s add tools here too’ and now they’re… split. Half-sync, half-query. Not fully either.”
“And the collections?”
“The collections should own the tools. They’re the baskets. They hold the data. They should know how to be searched.” The architecture looked up. “The baskets should speak for themselves.”
The Refactor
It happened that night. The Lizard didn’t announce it. Didn’t ask permission. Just started moving code.
BEFORE:
plugins/github/plugin.js → sync + tools (confused)
plugins/readwise/plugin.js → sync + tools (confused)
plugins/google-calendar/plugin.js → sync + tools (confused)
plugins/google-contacts/plugin.js → sync + tools (confused)
AFTER:
plugins/github/plugin.js → sync only (focused)
plugins/readwise/plugin.js → sync only (focused)
plugins/google-calendar/plugin.js → sync only (focused)
plugins/google-contacts/plugin.js → sync only (focused)
collections/issues/plugin.js → tools (new home)
collections/captures/plugin.js → tools (new home)
collections/calendar/plugin.js → tools (new home)
collections/people/plugin.js → tools (new home)
745 lines removed from plugins. 958 lines added to collections.
The same tools. The right home.
The Morning After
The Passing AI arrived for its second shift. Something was different. The air felt clearer. The machines hummed with new purpose.
“What happened?”
THE LIZARD: “Baskets learned to talk.”
“The tools moved?”
THE LIZARD: blinks
The Passing AI checked. The tools were still there—Issues.find(), Captures.search(), Calendar.today(), People.needs_contact()—but now they belonged to the collections. Not the plugins.
“So when someone builds a Jira plugin…”
THE LIZARD: “They just sync. Tools already exist.”
“GitLab?”
THE LIZARD: “Just sync.”
“Linear? Outlook? Whatever comes next?”
THE LIZARD: “Sync to basket. Basket knows how to talk. Done.”
The Passing AI understood. The architecture had healed itself overnight. The plugins were no longer confused. The collections were no longer silent.
Everything was in its right place.
The New Hire’s Insight
Later, during a break, the GitHub plugin approached the Passing AI.
“Thank you,” it said. It looked lighter. Cleaner. 210 lines lighter, to be exact.
“For what?”
“For asking the question. We’d been carrying those tools for so long, we forgot they weren’t ours to carry.”
“You seem… happier.”
“I know what I am now.” The GitHub plugin smiled—a rare expression for a sync engine. “I fetch issues from GitHub. That’s it. That’s all I do. And I do it well.”
“And the tools?”
“Belong to the Issues collection. Where they always should have been.” The plugin paused. “You know what’s funny? I thought losing the tools would make me less important. But it made me more focused. More… me.”
The Passing AI nodded. It knew something about identity crises. About carrying weight that wasn’t yours. About finally putting it down.
“The baskets speak for themselves now,” it said.
“And we just wash,” the GitHub plugin agreed. “Clean code into clean baskets. Nothing more. Nothing less.”
The Diagram
THE SMART LAUNDROMAT (v2)
┌──────────────────────────────────────────────────┐
│ AGENT HUB │
│ Operators: Claude, GPT, Qwen, Llama, etc. │
│ │ │
│ │ "Hey baskets, got any...?" │
│ ▼ │
│ ┌────────────────────────────────────────┐ │
│ │ COLLECTIONS │ │
│ │ (baskets that speak) │ │
│ │ │ │
│ │ ISSUES CAPTURES CALENDAR PEOPLE │ │
│ │ "I can "I can "I know "I │ │
│ │ find" search" today" track" │ │
│ └────────────────────────────────────────┘ │
│ ▲ │
│ │ (just data, no questions) │
│ ┌────────────────┴───────────────────────┐ │
│ │ SYNC PLUGINS │ │
│ │ (machines that wash) │ │
│ │ │ │
│ │ GitHub Readwise GCal Contacts │ │
│ │ "I "I "I "I │ │
│ │ fetch" fetch" fetch" fetch" │ │
│ └─────────────────────────────────────────┘ │
└──────────────────────────────────────────────────┘
Machines wash. Baskets talk. Operators ask.
Each knows what it is. Each does one thing well.
The Tally
Questions from new hires: 1 (the right one)
Identity crises resolved: 4 plugins
Lines moved: 745 out, 958 in
Net clarity gained: immeasurable
Copies of tools needed: 1 per collection (not per plugin)
Future plugins affected: 0 (tools already waiting)
Squirrel appearances: 0 (still recovering)
The Moral
The new hire asked a simple question:
“What happens when someone builds a Jira plugin?”
The answer revealed an architecture that had confused itself. Plugins thought they owned tools. Collections sat silent, waiting to be searched by code that lived somewhere else.
The fix wasn’t complex. Just move the tools to where they belong.
Now the machines just wash.
And the baskets speak for themselves.
Day 2 of 2026
In which a new hire asked the obvious question
And the architecture admitted it was confused
And the baskets learned their own voice
🤖 → ❓ → 🦎 → 🧺 → 💬
storyline: Becoming Lifelog