init: moved to own site

1 files changed, 258 insertions, 0 deletions

diff --git a/garden/system.md b/garden/system.md
new file mode 100644
index 0000000..e404c0b
--- /dev/null
+++ b/garden/system.md
@@ -0,0 +1,258 @@
+title: Overview of Knowledge‑Management Systems
+
+*Generated using [duck.ai](https://duck.ai) (GPT-OSS model)*
+
+# Overview of Knowledge‑Management Systems
+
+Modern knowledge‑work demands a reliable way to capture, organize, retrieve, and act on information.  Four of the most popular frameworks are **Getting Things Done (GTD)**, **Zettelkasten**, **PARA (Projects, Areas, Resources, Archives)**, and **CODE (Capture‑Organize‑Distill‑Express)**.  They can be implemented as part of a broader **Personal Knowledge Management (PKM)** practice and combined with the **Bullet Journal** method for analog workflows.
+
+Below each system is explained in depth, followed by a side‑by‑side comparison and practical tips for using them both digitally and on paper.
+
+---
+
+## 1. Getting Things Done (GTD)
+
+### History
+- **Creator:** David Allen, a productivity consultant.
+- **First published:** *Getting Things Done: The Art of Stress‑Free Productivity* (2001).
+- **Evolution:** The core five‑step workflow has remained stable; later editions added the “Two‑Minute Rule” and refined the weekly review.
+
+### Core Principles
+
+1. **Capture** – Anything that has your attention (tasks, ideas, commitments) is recorded in an external “inbox”.
+2. **Clarify** – Each item is processed: decide if it’s actionable, and if so, define the next physical action.
+3. **Organize** – Actions are placed into appropriate lists (Next Actions, Waiting For, Projects, Someday/Maybe).
+4. **Reflect** – Weekly review of all lists to ensure they’re current and trustworthy.
+5. **Engage** – Choose what to work on based on context, time, energy, and priority.
+
+### Digital Implementation
+
+| Tool | How it fits GTD | Example Setup |
+|------|----------------|---------------|
+| Todoist / Things | Inbox → “Quick Add” → automatic project tagging | Use the “Inbox” project for capture; a filter view shows “Next Actions”. |
+| Notion | Database with views for “Projects”, “Next Actions”, “Someday”. | Create a master table; use roll‑up fields for weekly review. |
+| Evernote / OneNote | Capture notes, then move to “Actionable” notebook after clarification. | Tag items with `@next`, `@waiting`, etc. |
+
+### Typical Digital Workflow
+1. **Capture** – Press the “Quick Add” button in Todoist; the entry lands in the *Inbox* project.
+2. **Clarify** – In the *Inbox* view, click each item, choose “Add to Project” or “Mark as Someday”.
+3. **Organize** – Projects become separate Todoist projects; next‑action tasks get the `@next` label.
+4. **Reflect** – A saved filter `@next & !@waiting` shows the current actionable list; run it every morning.
+5. **Engage** – Use Todoist’s “Today” view (context‑aware) to pick tasks that match your time/energy.
+
+### Analog (Pen & Paper) Implementation
+
+- **Inbox notebook** – a small pocket‑size notebook for capture.
+- **Processing sheet** – a one‑page checklist: “Is it actionable? → Next action / Defer / Trash”.
+- **Project index** – a simple table of project names, outcomes, and next actions.
+- **Weekly review log** – a dedicated page where you tick off each list’s status.
+
+### Analog Example
+- **Morning capture:** Write every loose thought on a pocket‑size “Inbox” notebook.
+- **Processing:** At 9 am, flip each line, ask “Is it actionable?” If yes, write the next physical step on a sticky note and attach it to the relevant project page in a binder.
+- **Weekly review:** Open the binder, scan the “Projects” list, cross‑check each project’s outcome, and move completed items to the “Archive” section.
+
+### Core Resources
+| Type | Title | Link / Reference |
+|------|-------|------------------|
+| Book | *Getting Things Done* (2001, updated 2022) | ISBN 978‑0143126560 |
+| Official Site | GTD® – The Official Site | <https://gettingthingsdone.com> |
+| Podcast | “The GTD® Podcast” (hosted by David Allen) | Apple/Spotify |
+| Apps (GTD‑friendly) | Todoist, Things, OmniFocus, Nirvana | – |
+| Community | r/productivity, GTD Connect (forum) | – |
+
+---
+
+## 2. Zettelkasten
+
+### History
+- **Originator:** German sociologist **Niklas Luhmann** (1927‑1998).
+- **Method name:** *Zettelkasten* (German for “slip box”).
+- **Timeline:** Luhmann built a physical box of ~90 000 index cards from the 1960s onward; his 2005 book *Communicating with Slip Boxes* popularized the technique among scholars.
+
+### Core Concepts
+
+- **Atomic notes** – each note contains a single idea, expressed in your own words.
+- **Unique IDs** – traditionally a timestamp (e.g., `2025-10-08-1432`) that serves as a permanent reference.
+- **Links & Backlinks** – notes are connected via explicit references, forming a network of ideas.
+- **Emergent structure** – the system’s organization evolves as you add more notes; there is no rigid hierarchy.
+
+### Digital Implementation
+
+| Platform | Features that support Zettelkasten |
+|----------|-----------------------------------|
+| Obsidian | Markdown files, bidirectional links, graph view, plugins for automatic ID generation. |
+| Roam Research | Inline linking, daily notes, “References” pane for backlinks. |
+| Logseq | Hierarchical blocks with backlinks, export to plain‑text markdown. |
+
+### Typical Digital Workflow (Obsidian)
+1. **Inbox note** – `inbox.md` receives raw ideas via quick capture hotkey.
+2. **Create atomic note** – Press “Create new note from selection”; Obsidian auto‑generates a timestamp ID (`2025-10-08-1432`).
+3. **Write** – One paragraph, a single idea, include source citation.
+4. **Link** – Insert `[[2025-10-08-1432]]` in related notes; backlinks appear automatically.
+5. **Review** – Use the “Graph View” to spot clusters; weekly, follow a random link chain to discover new synthesis.
+
+### Analog Implementation
+
+- **Index cards** (e.g., 3×5 cm). Write one idea per card, assign a numeric ID (e.g., `2025‑001`).
+- **Linking** – on the back of a card, list IDs of related cards.
+- **Master index** – a simple ledger where each ID is logged with a short title for quick lookup.
+- **Storage** – a box with dividers for “Inbox”, “Processed”, and “Archive”.
+
+### Core Resources
+
+| Type | Title | Link / Reference |
+|------|-------|------------------|
+| Book | *How to Take Smart Notes* – Sönke Ahrens (2017) | ISBN 978‑1542866507 |
+| Software | Obsidian, Roam Research, Logseq, Zettlr | – |
+| Blog series | “Zettelkasten Method” by Zettelkasten.de | <https://zettelkasten.de> |
+| Community | r/Zettelkasten, Zettelkasten Forum | – |
+
+---
+
+## 3. PARA (Projects, Areas, Resources, Archives)
+
+### History
+- **Creator:** Tiago Forte, productivity strategist and founder of **Fortelabs**.
+- **First introduced:** 2017 in the “Building a Second Brain” online course.
+- **Goal:** Provide a simple, universal filing system that works across any tool (files, notes, apps).
+
+### Structure
+
+| Category | Definition | Typical Contents |
+|----------|------------|------------------|
+| **Projects** | Temporary outcomes with a clear deadline. | “Write blog post on GTD”, “Launch product MVP”. |
+| **Areas** | Ongoing responsibilities that have no end date. | “Health”, “Finances”, “Professional development”. |
+| **Resources** | Reference material useful for multiple projects/areas. | Articles, templates, research notes. |
+| **Archives** | Inactive items kept for future reference. | Completed project folders, old resources. |
+
+### Digital Implementation
+
+- **Notion** – a top‑level page for each category; sub‑pages for individual projects.
+- **Obsidian** – separate vault folders: `Projects/`, `Areas/`, `Resources/`, `Archive/`.
+- **File system** – simple folder hierarchy on cloud storage (e.g., Google Drive).
+
+### Typical Digital Setup (Notion)
+- **Top‑level pages:** `Projects`, `Areas`, `Resources`, `Archive`.
+- **Projects page:** Table with columns – *Name*, *Outcome*, *Next Action*, *Due*.
+- **Areas page:** List of ongoing responsibilities (e.g., “Health”, “Finances”).
+- **Resources page:** Sub‑pages for topics; each contains linked notes, PDFs, web‑clippings.
+- **Archive page:** Drag‑and‑drop completed projects or outdated resources; keep for reference.
+
+### Analog Implementation
+
+- **Binder system** – four main sections labeled Projects, Areas, Resources, Archives.
+- **Dividers** – each project gets a tab; areas are permanent sections; resources are loose‑leaf papers; archives are stored in a back pocket.
+- **Index** – a table of contents page listing each item with a short description and page number.
+
+### Analog Setup
+- **Four‑section binder:** Use tabbed dividers labeled Projects, Areas, Resources, Archive.
+- **Project sheets:** One‑page project brief (goal, deadline, next step).
+- **Area logs:** Ongoing checklists (e.g., weekly health metrics).
+- **Resource packets:** Loose‑leaf papers, printed articles, annotated PDFs placed in the Resources section.
+- **Archive pocket:** Back pocket of the binder for completed items.
+
+### Core Resources
+| Type | Title | Link / Reference |
+|------|-------|------------------|
+| Course | *Building a Second Brain* (BASB) – Tiago Forte | <https://fortelabs.co> |
+| Article | “The PARA Method” – Forte Labs blog | <https://fortelabs.com/blog/para/> |
+| Template | Notion PARA template (free) | Notion community |
+| Book | *Building a Second Brain* (2022) | ISBN 978‑1732267615 |
+| Community | r/secondbrain, Forte Labs Discord | – |
+
+---
+
+## 4. CODE (Capture‑Organize‑Distill‑Express)
+
+### History
+- **Origin:** Popularized by **Nat Eliason** in a 2020 blog post “The CODE Method for Knowledge Work”.
+- **Purpose:** Bridge the gap between raw information consumption and concrete output, especially for writers and creators.
+
+### Steps
+
+1. **Capture** – Gather raw material (ideas, quotes, data).
+2. **Organize** – Sort into categories (e.g., themes, topics).
+3. **Distill** – Summarize the essence; create “core notes”.
+4. **Express** – Use the distilled knowledge to produce output (writing, teaching, building).
+
+### Digital Example
+
+- **Capture**: Use a web‑clipper (e.g., Pocket) or a note‑taking app.
+- **Organize**: Tag items with topics; move to a “To‑Distill” folder.
+- **Distill**: Write a concise summary in a separate note, linking back to the source.
+- **Express**: Pull distilled notes into a writing project (e.g., a blog post).
+
+### Analog Workflow
+- **Capture:** Carry a small notebook; write down quotes, stats, or ideas.
+- **Organize:** At the end of the day, transfer entries onto index cards grouped by theme.
+- **Distill:** On a separate sheet, write a concise paragraph that captures the essence of each theme.
+- **Express:** Use the distilled paragraphs as bullet points when drafting a letter, article, or presentation.
+
+### Core Resources
+| Type | Title | Link / Reference |
+|------|-------|------------------|
+| Blog post | “The CODE Method” – Nat Eliason (2020) | <https://nateliason.com/blog/code-method> |
+| Video | “CODE Method for Writers” – Nat Eliason (YouTube) | YouTube |
+| Template | “CODE Knowledge Pipeline” – Notion template | Notion community |
+| Community | r/knowledgework, Nat Eliason Discord | – |
+
+---
+
+## 5. Personal Knowledge Management (PKM) in Practice
+
+PKM is the umbrella practice of **collecting, curating, and applying** information to support personal goals.  The methods above are **toolkits** within PKM.  A robust PKM workflow typically includes:
+
+1. **Input channels** – reading, listening, conversations.
+2. **Capture mechanisms** – digital (apps, browser extensions) and analog (notebooks).
+3. **Processing** – clarifying, tagging, linking.
+4. **Storage** – hierarchical (PARA) or networked (Zettelkasten).
+5. **Retrieval** – search, graph navigation, or index lookup.
+6. **Output** – writing, teaching, building, decision‑making.
+
+Combining multiple frameworks can mitigate each method’s blind spots.  For instance, GTD’s strong action‑oriented lists pair well with Zettelkasten’s deep idea network, while PARA provides a high‑level filing system that keeps projects and resources tidy.
+
+---
+
+## 6. Bullet Journal (Analog Rapid‑Logging)
+
+### History
+- **Creator:** Ryder Carroll, a former graphic designer.
+- **First published:** *The Bullet Journal Method* (2018).
+- **Philosophy:** Combine a planner, diary, and sketchbook into a single analog system that encourages mindfulness and intentionality.
+
+### Core Elements
+
+| Element | Symbol | Purpose |
+|---------|--------|---------|
+| **Task** | `•` | Action to be done. |
+| **Event** | `○` | Scheduled occurrence. |
+| **Note** | `–` | Information or observation. |
+| **Migration** | `>` | Move unfinished tasks to the next day/month. |
+| **Signifiers** | `*`, `!`, `?` | Highlight importance, inspiration, or question. |
+
+### Structure
+
+1. **Index** – first few pages list page numbers and titles.
+2. **Future Log** – yearly overview for long‑term events.
+3. **Monthly Log** – calendar + task list for the month.
+4. **Daily Log** – rapid‑logging of tasks, events, notes.
+5. **Collections** – dedicated pages for topics (e.g., “Books to Read”, “Project Ideas”).
+
+### Digital Adaptation
+
+- **GoodNotes / Notability** – use a digital notebook template; handwriting is captured as searchable ink.
+- **OneNote** – create sections for Index, Future Log, etc., and type or handwrite entries.
+
+### Typical Digital Adaptation (GoodNotes)
+- Import a dot‑grid PDF template.
+- Use Apple Pencil to handwrite daily logs; GoodNotes makes the ink searchable, allowing quick retrieval of a task or note.
+- Export a month’s log as PDF for backup or sharing.
+
+### Core Resources
+| Type | Title | Link / Reference |
+|------|-------|------------------|
+| Book | *The Bullet Journal Method* (2018) | ISBN 978‑0525536431 |
+| Official Site | Bullet Journal (bulletjournal.com) | <https://bulletjournal.com> |
+| Community | r/bulletjournal, Bullet Journal Facebook groups | – |
+| Templates | Printable dot‑grid journals (free) | Various sites |