← Garden Patch Home · Inquiries
IFP-11 describes the Library platform as spanning a spectrum from personal knowledge management to group knowledge to public encyclopedia — “a continuum from private notes to shared wisdom.” The default temperature is cool. The analogue is “personal wikis, shared knowledge bases, Wikipedia.”
This framing treats knowledge storage as a single activity that varies by sharing scope. But there are at least two distinct paradigms hiding inside “Library”:
Living knowledge — documents that grow, split, merge, and evolve through active tending. A garden node, a wiki page under active editing, a research note accumulating findings. These are never “done.” Their value increases through ongoing maintenance. They need version awareness, merge semantics, and conflict resolution.
Static archives — curated captures preserved for reference. A cited paper, a clipped article, a meeting transcript. These are append-only or immutable. Their value is in faithful preservation, not evolution. They need provenance tracking, retrieval optimization, and format stability.
These two paradigms require different protocol behaviors from an agent:
| Dimension | Living Knowledge | Static Archive |
|---|---|---|
| Mutability | Evolves continuously | Append-only or immutable |
| Agent role | Tend, update, connect | Retrieve, cite, preserve |
| Sharing semantics | Version-aware collaboration | Faithful reproduction |
| Conflict model | Merge and resolve | No conflicts (immutable) |
| Temperature | Warm when active, cool when resting | Always cool |
| Quality signal | Freshness, connection density | Provenance, citation count |
The March 5, 2026 conversation. Christopher Allen and Peter Kaminski identified this collision directly. Christopher’s Deep Context Architecture distinguishes living garden nodes (typed forms that grow through tending stages: Seed → Growing → Evergreen → Pruned) from static captures (clippings, citations, transcripts that are curated but not rewritten). Peter’s Library platform collapses both into a single sharing-scope spectrum.
Agent behavior differs. An agent tending a living knowledge base needs to recognize staleness, propose updates, merge contributions, and resolve conflicts. An agent managing a static archive needs to preserve provenance, optimize retrieval, and resist modification. Using the same protocol behaviors for both risks either over-maintaining archives (wasting agent effort on immutable content) or under-maintaining living documents (treating evolving knowledge as static).
The Wikipedia analogy is misleading. Wikipedia articles look like static reference pages but are actually living documents under continuous collaborative editing with sophisticated governance (talk pages, edit wars, protection levels, featured article review). A “Library” that treats Wikipedia as the same kind of thing as a personal bookmark collection misses the governance complexity that makes Wikipedia work.