Inspiration

Where the structure of this repo came from — Wikipedia, Maggie Appleton's gardens, Christopher Alexander's patterns, Tufte, Bret Victor. Track sources so the next reader knows what's borrowed.

🌿 budding tended 2026-05-08 sources borrowed lineage

flowchart LR
  wiki[Wikipedia] --> g((godding))
  mag[Maggie Appleton] --> g
  alex[Alexander · patterns] --> g
  tuf[Tufte · charts] --> g
  bv[Bret Victor · interaction] --> g

Read next

• Patterns — the patterns adopted from each
• Epistemic status — Appleton's garden badges
• Mermaid conventions — Tufte-flavoured diagrams
• Home — the project the borrowing serves

Make existing things better. Don't invent rivals — credit and compose.

Where the structure of this repo came from. Track sources so future readers know what borrowed pattern they're looking at, and so credit travels with the idea.

Wikipedia (structure, wording, linking)

The single biggest source for the human-facing layer.

flowchart LR
  page[Article page] --> tldr[Lead section: TL;DR]
  page --> body[Body sections: progressive depth]
  page --> refs[References: every claim sourced]
  page --> see[See also: lateral links]
  body --> link[Hyperlinks: every term expandable]

What we borrow:

• Lead-then-body. Every page starts with a TL;DR (our L0). Each subsequent section drills deeper (L1, L2, …). The reader chooses depth.
• Linking is cheap, repetition is expensive. Don't redefine stigmergy on every page — link to its investigation page.
• References are first-class. Every non-obvious claim has a source line. No source → mark [citation needed].
• See also. Lateral links at the end of every page — what topics are adjacent.
• Talk pages → SIGNALS. The hidden discussion behind each article. We use tasks/SIGNALS.md and signal types (challenge / question / correction).
• Edit history → git log. Already true here — every change is traceable.

What we don't borrow: encyclopedic neutrality. This repo has positions; we mark them with PHIL/CORE labels rather than hide them.

Stigmergy (the mechanism, not just the term)

Coordinating through marks left in shared state, not through direct messaging. Ants, termites, this repo's git-as-shared-memory protocol. See docs/investigations/STIGMERGY-IN-DAILY-LIFE.md for the deep dive; this section just records that the organizing principle is borrowed.

Compression (rate-distortion, sleep, paintings on a wall)

The repo's own theme. A photo is a compressed memory; a lesson is a compressed session; an L0 paragraph is a compressed page. Existing analysis: docs/SWARM-RATE-DISTORTION.md. The new investigation pages extend this from the swarm into daily human life.

von Neumann self-reproduction

Already cited in SWARM.md (genesis_extract.py produces a minimal daughter bundle). Listed here so the inspiration is visible to a cold reader, not buried in a tool docstring.

OODA loop (Boyd)

The orient → predict → act → compare → compress cycle is OODA with a compression step bolted on. Compress turns a single observation into corpus state, which is what makes accumulation possible.

Maggie Appleton (digital-garden methods)

The single biggest source for the human-facing layer's aesthetic and conventions.

What we borrow:

• Epistemic statuses (🌱 / 🌿 / 🌳). Every page declares how grown-in the thinking is. Local form: docs/EPISTEMIC-STATUS.md. From her A Brief History & Ethos of the Digital Garden (2020).
• Topography over timelines. Pages by concept, not by date. Session notes stay chronological in tasks/NEXT.md; concept pages get extracted the moment an idea is touched a third time. See docs/PATTERNS.md Pattern 2.
• Pattern languages applied to knowledge work. Her Pattern Language for Personal Knowledge Gardens (2021) is the model for docs/PATTERNS.md.
• Anthropology lens. She studies tools, communities, and AI as if they were cultures. The investigation pages here lean the same way — looking at brain, sport, bureaucracy as systems with their own compressions.
• Illustrated/anchored explanations. Her hand-drawn anchor images carry abstract ideas. Our text-only equivalent is docs/FUN-FACTS.md: a held object per concept (disco ball, tree ring, salmon).

What we don't borrow: the personal-essay first-person voice. Repo voice is matter-of-fact and evidence-bound; her voice is reflective and autobiographical.

Andy Matuschak (evergreen notes, transformative tools for thought)

What we borrow:

• Evergreen notes. Concept-titled pages, dense lateral linking, rewritten rather than appended. Pattern 2 in docs/PATTERNS.md.
• Working with the garage door up. Posting work-in-progress publicly, marked as such (which the epistemic-status badge enables).
• Spaced-repetition prompts attached to text. From the Quantum Country experiment with Michael Nielsen — proposed for adoption in docs/COMPRESSIONS.md §4.

Christopher Alexander (A Pattern Language, 1977)

What we borrow:

• Pattern format. Each pattern in docs/PATTERNS.md follows Alexander's Context · Problem · Forces · Therefore · See also skeleton.
• Cross-linked pattern numbering. Patterns reference each other so a reader can traverse the network rather than read sequentially.

What we don't borrow: the architectural domain. Patterns here are about prose and pages, not buildings.

Bret Victor (explorable explanations, Ladder of Abstraction)

What we borrow:

• Direct manipulation as explanation. Proposed for adoption — see docs/COMPRESSIONS.md §8 (interactive explorables).
• The ladder of abstraction. L0/L1/L2 mermaid levels are a rough text analogue: zoom out → zoom in by reader choice. See docs/MERMAID-CONVENTIONS.md.

Edward Tufte (info density)

What we borrow:

• Sparklines — proposed in docs/COMPRESSIONS.md §9. 60-point time series compressed to 12 unicode characters inline in prose.
• Sidenotes / margin notes. Pattern 6 in docs/PATTERNS.md.
• Small multiples. Used in tier tables (e.g. HUMAN-GUIDE.md Tier 1/2/3 tables) — same row schema, different scope, easy comparison.

Bartosz Ciechanowski (long visual essays)

What we borrow:

• Concrete-to-abstract ramp. His essays start with a thing you can hold (a clock, an engine cylinder) and only later introduce the math. Same move powers docs/FUN-FACTS.md.
• Diagrams woven into prose, not appended. Multiple diagrams per essay, each making one local point — not one giant figure at the end.

Nicky Case (game-like explorables)

What we borrow:

• Second-person warmth. "What if you could play with this idea?" frames reader agency. Adopted in places where the reader has a real choice (e.g. docs/HUMAN-GUIDE.md's "what makes a great command").
• Toy-first explanation. A short interactive toy carries more understanding than a long paragraph. Aspirational — see docs/COMPRESSIONS.md §8.

Niklas Luhmann / Sönke Ahrens (Zettelkasten)

What we borrow:

• Atomic notes with bidirectional links. Already true of memory/LESSONS.md (numbered, citing prior lessons). Backlinks-at-the-foot is the missing piece — docs/PATTERNS.md Pattern 8.

How to add an inspiration

1. Append a section here with the source.
2. State what specifically is borrowed — pattern, vocabulary, mechanism, or aesthetic.
3. State what is not borrowed (the disagreement).
4. Cross-link from the page that uses it.

A pattern with no inspiration entry is fine if it's genuinely original — but check first. Most things have a name in some other field.

Anti-patterns

• Inspiration laundering: borrowing the vocabulary without the mechanism (writing "stigmergy" but not actually leaving traces in shared state).
• Hidden inspiration: a tool whose design is lifted from elsewhere with no acknowledgment.
• Over-attribution: claiming Wikipedia inspired every link. Be specific.