Wiki communities spent 25 years developing explicit governance for living documents — when to split a page, when to merge two pages, when to redirect, when to delete. These heuristics transfer to garden nodes and agent context files, with adaptations for the differences in authorship, readership, and cost.
Wikipedia codified five core lifecycle operations:
Splitting — When readable prose exceeds 50-60kB, or when a subtopic has enough substance to stand alone. The notability test applies: if the subtopic isn’t notable on its own, trim it rather than split. In the garden, the equivalent is the [[Standalone Document Test for Form Candidacy]]↑ — a section that passes the test should become its own node.
Merging — Five conditions: duplicate content forks, topical overlap, stubs unlikely to grow, insufficient notability (merge as alternative to deletion), and short articles requiring context from a broader page. In the garden, merge when two nodes are better understood as one — the distinction they claim doesn’t hold in practice.
Redirecting — When a page moves or merges, the old title becomes a redirect. In the garden, wikilink aliases serve this function. In agent context, skill pointers (load: path) serve as redirects.
Deletion — Not binary but graduated: speedy deletion (obvious violations), proposed deletion (7-day window), community debate. Alternatives always considered first: merge, redirect, draftify. Wikipedia deletes roughly 1,000-1,500 pages daily. The garden equivalent is pruning — superseded_by:: preserves the chain while removing the node from active use.
Draftification — Moving provisional content to a staging namespace where it can improve without polluting the main corpus. Structurally analogous to [[Seed Stage]] — seed nodes are provisional, visible but signaling low confidence.
The append-only trap — Documents that grow by accretion without consolidation. New content is added; nothing is revised, reorganized, or removed. The document becomes a chronological log wearing a topic’s name. Detectable via commit patterns: monotonically increasing length, many edit sessions, no refactoring commits (large deletions paired with additions). The trap is worse for agent context files, where every line consumed on every invocation makes bloat actively costly.
Structure ossification — Note systems that calcify and resist reorganization over time. Links accumulate, dependencies form, and the cost of restructuring a well-connected node exceeds the perceived benefit. The result: nodes that everyone knows are poorly organized but no one wants to touch. This is the opposite failure from the append-only trap: where append-only fails to consolidate, ossification fails to restructure. Both are failures of gardening — one from neglect, the other from inertia.
The wiki heuristics suggest operations the garden currently lacks explicit guidance for:
brief_summary can no longer capture its scope in 350 characterssuperseded_by::) or when it hasn’t been referenced or tended in multiple review cycles