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:

StatusMeaning
seedlingraw idea, rough, half-right — anything goes
evergreenrefined, linked, worth re-reading

Blog drafts in blog/ add: ideadraftreadypublished.

Workflow

  1. Capture — anything interesting lands in inbox/ or today’s daily
    note. No structure required. Don’t organize while capturing.
  2. 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.
  3. 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 set status: evergreen.
  4. Map — when 5+ notes cluster around a topic, write a Map of Content
    in maps/ that links them with one line of context each.
  5. Harvest — when an evergreen (or a cluster) is worth sharing, start a
    draft in blog/ (templates/post). ready drafts get copied to
    ~/projects/blog and published from there. Mark published + link.

Rules of thumb

  • Prefer linking over sorting — the graph is the organization.
  • Notes in sources/ record what a source says; notes in seeds/
    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).