Lyra — The AI Pipe
What the AI in this system actually does — and what it doesn't. Obsidian holds the knowledge. Lyra moves it.
Obsidian holds the knowledge. Lyra moves it.
That distinction is the whole post. But it’s worth unpacking, because most people assume the AI in a system like this is generating the content — synthesising from training data, producing polished thoughts on demand. That’s not what’s happening here.
Lyra is not the source. She’s the pipe.
What She Does When a Message Arrives
When I send a WhatsApp message, Lyra receives it. She reads it, infers where it belongs, and writes it to the right place in the knowledge base.
Short observation → appended to today’s journal under the right section. Decision made under pressure → a note in the active project’s Decisions folder. Achievement worth recording → a file in Career/Achievements. Incident that taught me something → tagged under Notable Moments.
She responds with a brief confirmation — “Logged.” or “Added to decisions.” — and that’s it.
No interface to open. No folder to choose. No title to write. The thought went in. It’s in the vault.
The Routing Intelligence
Most messages don’t have a prefix. I just write the way I’d text a colleague, and Lyra reads the signal in the content.
A message about a mistake that happened becomes a journal entry. A message weighing a technical tradeoff becomes a decision note. The routing isn’t keyword matching — it’s reading comprehension. When something is ambiguous, it defaults to the journal. That’s the right default. The journal is where everything lands before it finds its permanent home.
Prefixes exist for when I want to be explicit — journal:, achieve:, decision:, incident:, p: — but I rarely use them. The friction-free path is to just write. The capture layer post covers this in detail.
The Output Direction
When a blog post or LinkedIn draft needs writing, the flow reverses.
Lyra doesn’t write from her training data. She reads the vault first — journals, decision notes, incident logs, achievement records — and drafts from what’s already there. The knowledge is in the files. Her job is to find the thread, surface the pattern, and give it shape in prose.
That’s why the content doesn’t feel generic. It isn’t assembled from “what does the internet say about software architecture.” It’s assembled from specific decisions, specific incidents, and specific patterns I noticed in real work. Lyra is expressing that, not replacing it.
What She Doesn’t Do
She doesn’t know what happened in a meeting I didn’t describe.
She can’t surface an insight I never captured. She can’t invent the pattern — she can only recognise it across the notes that exist. If the raw material isn’t in the vault, the output layer has nothing to work with.
This is the part people miss when they assume AI is generating the knowledge. The model is extraordinarily capable at structure, synthesis, and expression. It is useless as a source of lived experience. It doesn’t know what it felt like to watch the same architectural mistake happen across three different projects. I do. That’s in the journal. Lyra just knows how to read it.
Always On
Lyra runs in a NanoClaw container with the knowledge base mounted as a file system. She has no idea what time it is in Colombo. She doesn’t care.
When I send a message at 11pm, it gets routed. When I’m at a client site without a laptop, it gets routed. When I’m between meetings and have thirty seconds to describe what just happened — it gets routed.
There’s no session to start. No app to open. No login. The pipe doesn’t have office hours.
The Role in One Line
Lyra doesn’t write the blog post. She’s the reason the blog post has something real to say.
The knowledge worker who couldn’t write for sixteen years now has a system where the expression layer is always open, always listening, and always knows where to put things. The intelligence is in the vault. The pipe just makes sure nothing gets lost on the way there.
That’s what the output layer builds on.
Signal 4 of 7 in The Second Brain That Publishes Itself.