After the Framework Stood Up, I Realized I Had No “Shared Workshop”
The five-part Info-to-Creation series got the framework standing: information gets collected and denoised, records settle into half-finished goods, knowledge gets structured into capability, creation reorganizes it for an audience. But after writing that line in Layer 3: Knowledge — “your knowledge base is the workshop you share with your AI” — something kept nagging at me.
I didn’t actually have such a workshop.
My methodologies were scattered across four places: principles written into blog posts, fragments in note apps, project material in several Obsidian vaults, and a large amount of muscle memory that existed only as “I think this worked last time.” Every time I wanted to write a serious 小红书 post or plan a new platform, I had to reconstruct from scratch how I pulled it off the previous time.
So I did one thing: I turned the knowledge layer from a concept into an entity — a private repository, codename arsenal. These field notes document its design, and the handful of things I only truly figured out while building it.
Internal and External Are Two Systems
The first thing I got clear on was separating “internal” and “external” completely.
The external side everyone can see: the blog, 小红书, someday X and short video. They are battlefields — audience-facing, platform-driven, judged by whether people receive you and connect with you. That’s the creation layer of the framework.
The internal side only I (and my AI) can see: a combat playbook per platform, verified title formulas, my own voice rules, the potholes I’ve hit. They are the arsenal — self-facing, judged by reusability, solving exactly one problem: make the next shot land closer. That’s the knowledge layer.
Internal (private repo: arsenal)
┌─────────────────────────────────────────┐
│ identity/ who I am: voice, red lines │
│ playbooks/ one combat manual per platform│
│ methods/ hooks, structures, SOPs │
│ swipe/ unverified zone (mess allowed)│
│ retro/ review & reflow workshop │
└──────────────┬──────────────────────────┘
│ ammunition flows out
▼
External (platform battlefields)
Blog / 小红书 / X / short video
│
└── feedback flows back ──▶ retro/
Once separated, several long-standing frictions simply vanished. Writing for a platform no longer carries the worry of “should I be hiding this method” — the method was never on the battlefield to begin with. Distilling a method no longer involves fussing over presentation — there is no audience inside an arsenal. Mixing the two ruins both — this is the physical-isolation version of the series’ founding claim that knowledge solves your problems while creation solves other people’s.
Battle Records Are the Admission Ticket
The second design decision installed a gate my knowledge systems never had: every method card carries an evidence field in its frontmatter recording its real-world track record. No record, no admission.
This is the vaccine against hoarder’s disease. I wrote in Layer 3 that the surest way a knowledge base degenerates is into a bookmarks folder — see a good method, save it, done. This time the gate is structural: conclusions imported from external research (say, “小红书 click-through above 3% is the passing line” or “the thread sweet spot is 5–7 tweets”) are all tagged maturity: imported. Imports may sit there for reference, but they are second-class citizens — only what I have personally used, measured, and confirmed gets promoted to proven.
This forced a very healthy side effect: the hook library is deliberately empty. I did not port over the hundred “proven hooks” from my research, because that was someone else’s proof, not mine. The first hook card in this library must come from deconstructing my own first published piece.
Better an empty arsenal than a fake one. An empty one pushes you toward real combat; a fake one only hands you the illusion of “I have so many methods” — and that illusion is exactly what killed the last bookmarks folder.
The Directory Is a Map: Constitution, Index, Log
The third design comes straight from a judgment in Layer 3: the directory structure you give your AI is essentially a map. This time I drew the map all the way down.
Three control files sit at the repo root. CLAUDE.md is the constitution: what each directory is responsible for, how frontmatter is written, what qualifies for admission where, and the AI’s permission boundary at each layer. index.md is the master map: the AI reads it first and navigates by it instead of crawling the whole tree. log.md is the journal: append-only, one line per admission or retirement.
On top sit three fixed workflows: ingest (new material enters the unverified zone; only field-tested material gets distilled and admitted), query (a creation task auto-assembles its context), and lint (monthly: cards unused for sixty days get archived, conclusions overturned by new data get rewritten in place rather than appended, orphan cards get merged or deleted).
You may recognize this as the full landing of the “elimination mechanism” from Layer 3 — but with one insight I hadn’t fully absorbed back then: the most tedious part of a knowledge base is maintenance, and maintenance is precisely what AI is best at. Hunting contradictions, clearing dead cards, refreshing indexes — a human doing this quits within three months; an AI does it for free. Only after outsourcing maintenance did “a knowledge base needs metabolism” turn from a nice principle into a sustainable reality.
Knowledge Turns from Documents into Actions
The fourth design is, I believe, the longest lever in the whole system: the repository ships with executable skills.
When the “write a 小红书 post” skill fires, it auto-assembles my voice rules, the 小红书 combat manual, the matching hook cards, and the corresponding topic card — then drafts under those constraints, with acceptance criteria hard-coded into the skill itself (three title candidates, a cover proposal, a banned-word self-check).
This deserves spelling out. In even the best traditional knowledge base, knowledge is consulted: you must remember to look, find it, read it, then apply it — leaking at every step. A skill makes knowledge executed: the methodology no longer waits for you to recall it; it is forcibly injected into every single generation.
In Layer 3 I said that every bit of structure you add makes your AI understand you a bit more. Now I’ll add a sharper line: structure makes the AI understand you; executability makes the AI become you. That is the true watershed between an AI-era knowledge base and every note system that came before — and the one direction in personal knowledge management I’d bet on for the next few years.
Voice Is Excavated from Old Work, Not Defined from Scratch
The fifth design targets a concrete fear: AI slop.
The most important file in the arsenal is the voice spec. But I did not sit down to “define my style” — styles defined from scratch are all adjectives. “Sincere,” “deep,” “authentic”: hand those to an AI and it can do nothing with them.
What I did was reverse engineering: take the published pieces I’m most satisfied with and derive observable rules of action from them. For instance: section headings must be complete judgment sentences, not noun phrases; abstract claims must be paired with firsthand cases, never invented characters; punchlines may only appear at the end of an argument — they are results, not decoration; every method must end with a bucket of cold water. Plus a banned-word list — the words that instantly announce “an AI wrote this” get named and shot.
The voice spec and the deconstructed hit patterns are the two lines of defense against AI slop. The former tells the AI “I never talk like this”; the latter tells it “this is how I succeeded last time.” Both are drawn from things that actually happened — which is the only reason they work.
The Flywheel’s Axle: Reflow Beats Hoarding
The last design answers the content flywheel from the series finale. Flywheels are easy to draw; the hard part is finding the axle — the one concrete action that makes “feedback becomes new insight” actually happen instead of living on in a diagram.
My answer is a mandatory review card. For every significant publication, pull the numbers on day 3 and day 7, write the card, then follow a fixed fork: overperformers get deconstructed — their hook and structure become new cards, admitted with this run’s data as their battle record; duds get an honest cause of death written into that platform manual’s counter-example section.
This action outranks adding any new knowledge to the library. Hoarding makes a library bigger; only reflow makes it more accurate. A library that keeps ingesting knowledge but never reflows battle records is still a bookmarks folder — no matter how beautiful its structure.
Cold Water: Don’t Build the Whole System First
As is the custom here, the method ends with cold water. This bucket goes to myself from three days ago.
While designing this system I briefly wanted to build everything at once — every platform playbook, every structure card, a fully stocked topic pipeline. That is precisely the trap the series finale warned about: turning “building a cool system” into the goal, fondling the hammer endlessly, driving zero nails.
The actual cold start needs four files: a constitution, a voice spec excavated from old work, a manual for the one platform you most want to break through, and one writing skill. Then go publish something real. Let every other directory grow out of actual publishing and actual reviews. A system is a crop, not a building.
The Test Remains the Same One
The thing is freshly built, and its current state is: structure complete, magazine mostly empty. By my own rules it doesn’t yet deserve the name “knowledge base” — right now it is only a promise.
Whether it’s any good will not be judged by how well this essay reads, but by two months from now: whether the hook library has grown cards with battle records, whether the counter-example sections hold honest corpses, whether my content numbers have moved.
Information is worthless, and methodology is worthless too — what’s worth something is methodology that has been verified by battle records, can be executed by AI, and is still metabolizing. The arsenal is built. Time to open fire.
These are field notes appended to the Info-to-Creation series. Return to the framework for the four-layer overview, or revisit Layer 3: Knowledge for the theory this design departs from.
Responses