The CODE Framework and Its Broken Promise
Tiago Forte's Building a Second Brain introduced the CODE framework — Capture, Organize, Distill, Express — as the lifecycle of personal knowledge management. The idea is elegant: you capture ideas from everywhere, organize them into a trusted system, distill them into actionable summaries, and express them as creative output that reaches an audience. The loop is supposed to compound: more expression leads to more feedback, which leads to better capture.
In practice, the loop breaks at Express. Tools like Notion, Obsidian, and Roam Research excel at the first three stages. They make it easy to clip articles, tag notes, and create linked summaries. But when it comes to turning that knowledge into a blog post, a newsletter, a portfolio piece, or a published page, users hit a wall. The tools that are great for thinking are poor at shipping.
This is not a minor gap. If knowledge never reaches an audience, the feedback loop never starts. Your second brain becomes a write-only archive — comprehensive but inert.
An estimated 92% of digitally saved knowledge is never accessed again. The Express gap turns second brains into digital graveyards.
Where PKM Tools Fail at Express
The Express step requires three capabilities that most PKM tools lack. First, synthesis: combining insights from dozens of scattered notes into a coherent narrative. Second, drafting: transforming bullet points and highlights into polished prose. Third, publishing: getting the finished piece in front of readers without a separate tool and workflow.
Obsidian users face this acutely. Their vaults are rich with interlinked Markdown notes, but creating a publishable article means manually assembling relevant notes, rewriting them into flowing paragraphs, and then either setting up Obsidian Publish ($8/month) or exporting to a separate CMS. The friction is high enough that most people simply do not bother.
Notion users have "Share to Web" but the output is visually constrained and SEO-limited. Roam users have no publishing path at all. The pattern is consistent: PKM tools invest in capture and organization but treat expression as someone else's problem.
How AI Agents Bridge the Express Gap
AI agents change the economics of the Express step. In Moryflow, an agent can scan your notes on a topic, identify the most relevant insights, propose an outline, and draft a complete article — all from a single prompt. You review and refine the output instead of starting from a blank page. This reduces the effort from hours to minutes.
The key difference between an AI agent and a chatbot sidebar is autonomy. A chatbot waits for you to paste text and ask questions. An agent proactively traverses your knowledge graph, pulls in related notes you may have forgotten, and produces structured output. It is the difference between a search engine and a research assistant.
Critically, the agent works with your existing notes. It does not generate content from thin air — it synthesizes what you have already captured, organized, and distilled. This means the output reflects your unique knowledge and perspective, not generic AI-generated content.
AI agents do not replace your thinking — they automate the mechanical work of turning thinking into publishable output.
Moryflow's Capture-to-Publish Workflow
Moryflow closes the entire CODE loop in a single application. Capture notes from any source — manual entry, web clipper, Telegram integration. Organize with tags, folders, and bidirectional links. Distill with AI-powered summarization that extracts key insights. Express with agent-assisted drafting and one-click publishing.
The publishing step is seamless. Once an agent drafts your article and you approve it, one click turns the note into a live, publicly accessible web page with automatic SEO metadata, clean typography, and a shareable URL. Updates are instant — edit the note and the published page reflects the change immediately.
This integrated workflow means knowledge flows from capture to audience without switching tools, without manual export, and without infrastructure management. The friction that killed the Express step is simply gone.
Building an Express Habit
The biggest barrier to expression is not tooling — it is habit. Even with frictionless publishing, you need a rhythm of turning captured knowledge into shared output. Start small: commit to publishing one note per week. It does not need to be a polished essay; a curated list of insights, a book summary, or a how-to note all count.
Digital gardens embrace this philosophy by design. Unlike blogs that demand finished posts, digital gardens encourage publishing work-in-progress notes that grow over time. Moryflow's note-based publishing model is inherently garden-friendly: each note is an independent page, and imperfection is not just acceptable — it is expected.
Over time, the Express habit creates a compounding asset. Published notes attract readers, generate feedback, and spark new ideas that feed back into your capture process. This is the flywheel that Tiago Forte envisioned — and it only spins when you Express.
Start with one published note per week. Digital gardens thrive on imperfect, evolving content — not polished essays.