How this garden works
One note, one idea. Notes grow; they are never “finished” — an evergreen is
just a note worth keeping tended.
Lifecycle
status in frontmatter:
| Status | Meaning |
|---|---|
seedling | raw idea, rough, half-right — anything goes |
evergreen | refined, linked, worth re-reading |
Blog drafts in blog/ add: idea → draft → ready → published.
Workflow
- Capture — anything interesting lands in
inbox/or today’s daily
note. No structure required. Don’t organize while capturing. - Plant — turn a capture into a note in
seeds/(template:
templates/seed). One idea per note, a working title, a first pass in
your own words. - Tend — revisit, revise, split, merge. Add wikilinks to related
notes. When a note holds together and says one thing well, move it to
evergreens/and setstatus: evergreen. - Map — when 5+ notes cluster around a topic, write a Map of Content
inmaps/that links them with one line of context each. - Harvest — when an evergreen (or a cluster) is worth sharing, start a
draft inblog/(templates/post).readydrafts get copied to
~/projects/blogand published from there. Markpublished+ link.
Rules of thumb
- Prefer linking over sorting — the graph is the organization.
- Notes in
sources/record what a source says; notes inseeds/
record what I think — keep them separate, link heavily. - Deleting is fine: compost a note by stripping it back to the one sentence
that was true. - Repo machinery (
_specs/,_questions/, …) is not garden content —
those are project-management folders for agents. - Commit after every tending session (git repo under the vault).