A short meta-essay on what happened to article writing when the writer started reading their own archive.
The Old Loop and the New Loop
For most of the history of the web, an article was a one-way object. You wrote it, you published it, somebody read it, and then it sat there forever as a frozen artifact. The writer rarely went back to their own work. The archive existed for the audience, not for the author. If you were a prolific blogger you might link back to an old post occasionally, but the act of reading your own writing was either nostalgia or housekeeping. It was never the point.
The point was downstream: the article existed so that other people could learn something.
That loop is breaking.
Here is what happens at Tygart Media now when an article gets written. Step one: the thinking happens in a chat with Claude, usually messy and stream-of-consciousness. Step two: that thinking gets shaped into an article. Step three: the article gets published to the appropriate WordPress site for the audience that needs it. Step four — and this is the new part — the same article, sometimes restructured, sometimes verbatim, gets written into the Notion command center as a knowledge node. Step five, weeks or months later: a future version of Claude, asked a question that touches the same territory, retrieves that knowledge node and uses it to think.
The article is no longer a one-way broadcast. It is a two-way object. Outward-facing for the audience. Inward-facing for the operator’s own future intelligence.
What This Quietly Changes About Writing
Once you notice that you are writing for two audiences instead of one, every editorial decision shifts a little.
You start including the reasoning, not just the conclusion. The audience might only need the conclusion, but future-you needs to know why you concluded what you concluded, because future-you is going to be applying the same reasoning to a different problem and the conclusion alone will not transfer. So you leave the work in. Not the entire scratch pad, but the structure of the argument. The objections you considered. The version that did not work. The footnote that says “this only holds when X is also true.”
You start writing in patterns instead of in lists. A list is great for a reader who wants to skim. A pattern is better for a retrieval system that wants to match a future situation against a past one. So you write things like “when the situation looks like A, do B, except when C, in which case do D.” That is a lousy listicle. It is a great knowledge node.
You start tagging on the way out the door. Not just SEO tags for Google. Tags for your own retrieval. Tags that future-you would type into a search bar. The first article we published this week has a section literally titled “Knowledge Node Notes” containing the tags we want to be findable by. The tags are not for the reader. They are for the next conversation.
And you start being honest in writing about things you used to keep verbal. Half-formed opinions. Things that did not work. Things you tried and bailed on. The stuff that used to live in your head as “I should remember this” suddenly has a place to live where it can actually be remembered. The cost of writing it down went to zero, because the writing-it-down was already happening for the audience.
The Dual Publish
The mechanical version of this is simple. Every meaningful article gets published twice. Once to the public WordPress site where the audience reads it. Once to the Notion knowledge base where future operations can retrieve it. The two versions are not always identical. The public one is usually narrative, prose-first, optimized for a human reader who is not in a hurry. The internal one is usually structured, table-and-bullet-first, optimized for a retrieval system that is in a tremendous hurry.
Both versions exist simultaneously. Neither is the canonical one. They are two faces of the same crystallized thinking.
The interesting thing about doing this for a while is that the internal version starts being the more valuable one. Not for the audience, obviously. For the operator. The public article gets read once, maybe twice, and then it does its SEO work passively in the background. The internal node gets retrieved over and over, in conversations the writer did not anticipate, applied to problems the article was not originally about. The audience-facing version is the one that pays the bills. The internal version is the one that compounds.
The Speculation Worth Sitting With
If this pattern is real — if articles are quietly turning into two-faced objects, one face for the audience and one for the writer’s own retrieval — then the next question is whether websites themselves are about to change in the same way.
The traditional website is a marketing object. It exists to attract, persuade, and convert. The structure reflects that: a homepage that pitches, service pages that explain, a blog that proves expertise, a contact form that captures leads. Every page serves the visitor. The website is a storefront.
What if the future website is a brain instead of a storefront?
Imagine a website where every page is simultaneously a public artifact and an entry in the operator’s externalized knowledge base. The “About” page is the operator’s actual self-description, the same one their AI uses to introduce them in other conversations. The “Services” page is the operator’s actual taxonomy of what they do, the same one their AI uses to figure out whether a given inquiry is a fit. The “Blog” is the operator’s actual thinking journal, the same one their AI retrieves from when answering questions in client meetings. The “FAQ” is the operator’s actual answer repository, public-facing because there was never a reason to hide it.
In this version, the website is not a thing the operator built for the audience. It is a thing the operator built for themselves, that they happened to leave the door open on. The audience is welcome to read it. So is every AI in the world. So is the operator’s own future AI. The same artifact serves all of them.
This is not a hypothetical aesthetic choice. It is what happens by default if you commit to the dual-publish pattern long enough. After two years of every article being written into both the public site and the internal knowledge base, the public site is the internal knowledge base, just with a nicer template on top of it. The wall between marketing site and operator’s brain dissolves because there was never any reason for the wall to exist in the first place. It only existed because the technology to dissolve it had not arrived yet.
Why This Might Actually Be How Websites Work in Five Years
A few forces are pushing in this direction at the same time.
AI retrieval changes what a webpage is for. Google is no longer the only reader. ChatGPT, Claude, Perplexity, and Gemini all crawl, summarize, and cite. If your page is structured for human skim-reading, it loses to the page next door that is structured for AI ingestion. The pages that win the next decade are pages written to be retrieved, not pages written to be browsed.
The cost of writing well dropped to almost zero. If writing a 2,000-word article used to take six hours and now takes one, the marginal cost of also writing an internal version is approximately nothing. The dual-publish pattern was not viable when writing was expensive. It is viable now. So it will spread, because the operators who do it accumulate a compounding advantage that the operators who do not cannot catch up to.
The audience for any given page is no longer just humans. The most important reader of your services page in 2027 is probably going to be an AI shopping agent on behalf of a buyer who never personally visits your site. That AI does not care about your hero image. It cares about whether your services taxonomy is structured cleanly enough to match against its user’s request. The website that wins that match is the website that was already structured like a knowledge base, because it was the operator’s actual knowledge base.
Operators are starting to see their websites as extensions of themselves. Not as marketing assets. As externalized memory. The same way a notebook is an extension of a writer’s mind. The website-as-brain framing only feels weird because we are used to the website-as-storefront framing. There is nothing inevitable about the storefront framing. It was just the dominant pattern of a particular era.
The Practical Move
If any of this is correct, the practical move is to start treating every article as a deposit in two places at once: the public face that the audience reads, and the internal face that future operations retrieve. Not as a workflow chore. As the entire point of writing the article.
The audience gets value either way. The compounding only happens for the operator who treats the second deposit as non-negotiable.
And if it turns out that websites in five years really are knowledge bases with marketing skins, the operator who started the dual-publish habit two years early will have a knowledge base with two years of compound interest on it. The operator who did not will be starting from scratch, in a market where everyone else has a head start.
That is a bet worth making even if the speculation turns out to be wrong. The dual-publish pattern is already valuable on its own terms, today, with no future hypothesis required. The future hypothesis is just the upside.
Knowledge Node Notes
This section exists so this article is more useful as a knowledge node when scanned later.
Core Claim
Articles are quietly becoming two-faced objects. One face is the public broadcast for the audience. The other face is an entry in the writer’s own retrievable knowledge base. The dual-publish pattern (WordPress + Notion, in our case) makes every article do double duty: pay the bills via SEO/audience reach, and compound internal intelligence via future retrieval.
What Changes About How You Write
- Include the reasoning, not just the conclusion — future-you needs the why, not just the what.
- Write in patterns, not lists — “when X, do Y, except when Z” beats “5 tips for X” for retrieval.
- Tag on the way out — for your own future search, not just for Google.
- Be honest in writing about half-formed things — the cost of writing them down is now zero because writing is already happening.
The Speculation
If the dual-publish pattern is real, websites themselves may be heading toward a knowledge-base-with-a-marketing-skin model. Storefront framing is a particular era’s convention, not a permanent truth. Forces pushing this way:
- AI retrieval changes what a page is for (retrieved, not browsed)
- Cost of writing well dropped to ~zero, making dual-publish viable
- Most important reader of a services page may soon be an AI shopping agent, not a human
- Operators starting to see websites as externalized memory rather than marketing assets
Connection to Tygart Media Stack
This article is itself an example of the pattern. It exists on tygartmedia.com as a public artifact for the audience and in the Notion Knowledge Lab as a structured retrieval node for future Claude conversations. The two versions are not identical — the public one is prose-first, the internal one is structured-first — but they are the same crystallized thinking, deposited in two places.
Connection to The Other Article
This pairs naturally with the “Will’s Second Brain as an API” piece. That article asked: could we sell access to our context layer? This article asks: how does our context layer get built in the first place? The answer is: every article is a deposit. The dual-publish pattern is the deposit mechanism.
Tags
dual publish · knowledge base as website · website as brain · externalized memory · article as knowledge node · AI retrieval · GEO · AEO · content compounding · operator intelligence · context engineering · Notion + WordPress · Tygart Media methodology · future of websites · AI shopping agents · writing for retrieval · pattern writing vs list writing
Last updated: April 2026.
Leave a Reply