How to Turn Notes Into Posts: The Life = Content Loop

If it happened, it can become a note. If it is a note, it can become a skill, a post, or a build. That loop is the whole method. I call it Life = Content.

This page is a short how-to. It is for people who already take notes and still publish nothing. It is also for people who built a second brain and then stopped feeding it.

The loop

Three steps. Do them in order.

1. Capture. Write the raw thing down while it is still in your head. A call, a bug, a rant, a link. Do not file it yet. Speed beats structure at this step.
2. Distill. Later, cut the note to what you would tell a skilled friend. One claim. One example. One next action. Throw the rest away.
3. Publish. Put the distilled note where other people can use it. A post. A skill file. A checklist. A small product.

The public site is the last edge of that loop. The private vault is the first edge. They are not the same pile.

Why most second brains die

The tool is not the failure. The upkeep is the failure.

A note system that needs perfect tags, perfect folders, and a weekly review will lose to a busy week. When you stop, the archive becomes a graveyard of good intentions. That is not a character flaw. It is a cost problem. The cost of keeping the system alive exceeded the benefit.

The fix is not a better app. The fix is a smaller loop. Capture fast. Distill on purpose. Publish only what helps.

A 20-minute weekly pass

Do this once a week. Set a timer.

1. Open the week's raw captures.
2. Pick three notes that still matter.
3. Distill each one to a short page: title, claim, steps or examples, source if you used one.
4. Choose a destination for each: keep private, turn into a skill, or publish.
5. Ship at least one public artifact. A post can be 400 words. A skill can be one procedure.

If you cannot name a destination, the note is not ready. Leave it. Do not build a taxonomy to hide the indecision.

A worked example

Raw capture: "Agent skipped the footer four times. Memory did not help. A pre-call reminder did not help. A post-response hook did."

Distill:

• Claim: A reminder is a nudge. Code that rewrites the reply is enforcement.
• Steps: If the model must produce a format every time, do not ask it to remember. Append the format after it finishes.
• Publish: a short how-to, or a skill named "nudge vs enforcement."

That is the loop. The scar becomes a procedure. The procedure becomes a page other people can use.

What to publish vs what to keep

Publish the method, the checklist, the worked example, the failure you already paid for.

Keep the private names, the keys, the client files, the paths on your machine, and anything that would let a stranger map your life.

If a sentence only helps you, it stays in the vault. If a sentence would save a stranger an hour, it can leave the vault.

Skills are distilled notes with a trigger

A skill is a procedure you want an agent (or a future you) to run again. It needs a name, a when-to-use line, and steps. It does not need a memoir.

If you solved a nasty problem once, write the steps while the scar is fresh. That is how a second brain compounds. The next session starts with the procedure, not with the same confusion.

FAQ

What does Life = Content mean?

It means you treat lived work as raw material. You capture it, you cut it down, and you publish the parts that other people can reuse. It is a loop, not a slogan.

How do I start a second brain without it dying?

Start with capture and a weekly distill pass. Do not start with a folder taxonomy. Publish one small artifact a week. If the system needs more than 20 minutes a week to stay alive, cut the system.

Should I publish my private notes?

No. Publish the method and the reusable example. Keep names, keys, client work, and local file paths private.

How is this different from a daily journal?

A journal stores the day. This loop stores the reusable part of the day. Most journal lines never become a skill or a post. That is fine. The weekly pass is how you find the few that should.

What tool should I use?

Use the tool you will actually open. The loop does not care. I use Markdown in git for public posts and a private vault for capture. The tool is not the method.

Sources

• Tiago Forte. Building a Second Brain. The capture-and-organize tradition this loop sits next to. I do not copy Forte's PARA system here. The public step is my addition.
• This site's own working rule: capture privately, distill on purpose, publish what helps.