Digital Garden Cultivator

Table of Contents

• What It Is
• Quick Start
• Calculate Garden Metrics
• Output Formats
• When to Use
• Content Maturity Levels
• Core Workflow
• Garden Layout Template
• Maintenance Cadence
• Success Metrics
• Detailed Resources
• Integration

Digital Garden Cultivator

Design, manage, and evolve digital gardens as living knowledge bases. Digital gardens are interconnected note collections that grow organically, emphasizing evolution over perfection.

What It Is

A digital garden approach to knowledge management that:

• Builds dynamic knowledge bases that evolve over time
• Connects notes through bidirectional links
• Incubates ideas before formalizing as documentation
• Creates discovery paths for information navigation
• Tracks content maturity and maintenance needs

Quick Start

Calculate Garden Metrics

python scripts/garden_metrics.py path/to/garden.json --format brief

Verification: Run python --version to verify Python environment.

Output Formats

• json - Full metrics as JSON
• brief - One-line summary
• prometheus - Prometheus exposition format

When To Use

• Building dynamic knowledge bases that evolve over time
• Connecting notes, skills, and palaces through bidirectional links
• Incubating ideas before formalizing as documentation
• Creating discovery paths for navigating information
• Managing content lifecycle (seedling → growing → evergreen)

When NOT To Use

• Creating memory palace

structures - use memory-palace-architect

• Evaluating new knowledge
• use knowledge-intake
• Creating memory palace

structures - use memory-palace-architect

• Evaluating new knowledge
• use knowledge-intake

Content Maturity Levels

Core Workflow

1. Collect Sources - Gather notes, bookmarks, ideas 2. Plan Structure - Define garden organization 3. Create Links - Build bidirectional connections 4. Schedule Maintenance - Establish tending cadence 5. Document Outputs - Convert mature ideas to formal docs

Garden Layout Template

garden:
  sections: ["research", "patterns", "experiments"]
  plots:
    - name: "My First Note"
      purpose: "reference"  # reference | evergreen | lab
      maturity: "seedling"  # seedling | growing | evergreen
      inbound_links: []
      outbound_links: []
      last_tended: "2025-11-24T10:00:00Z"

Verification: Run the command with --help flag to verify availability.

Maintenance Cadence

Success Metrics

• Link density - Average links per piece of content
• Bidirectional coverage - % of links that are reciprocal
• Freshness - Time since last update per area
• Maturity ratio - Evergreen content / total content

Detailed Resources

• Linking Patterns: See modules/linking-patterns.md
• Maintenance Guide: See modules/maintenance.md
• Metrics Integration: See modules/maintenance.md

Integration

• memory-palace-architect - Host garden within palace structure
• knowledge-locator - Search garden content
• session-palace-builder - Seed garden from session insights

Troubleshooting

Common Issues

Pre-commit hooks failing Run SKIP=... git commit to bypass temporarily, then fix issues

Merge conflicts Use git merge --abort to reset, then resolve conflicts carefully

Commit rejected Check hook output and fix reported issues before committing again

Linking Patterns

Effective linking creates a navigable knowledge network that supports both focused retrieval and serendipitous discovery.

Link Types

Direct Links

Explicit connections between related content.

• Use when: Clear topical relationship exists
• Example: "OAuth" → "Authentication Methods"

Contextual Links

Links embedded within explanatory sentences.

• Use when: Connection needs context to understand
• Example: "This pattern uses [dependency injection] for testability"

Hub Links

Central nodes that connect many related topics.

• Use when: Topic serves as organizing principle
• Example: "API Design" as hub for REST, GraphQL, RPC topics

Bridge Links

Connections between seemingly unrelated domains.

• Use when: Cross-domain insight exists
• Example: "Memory Palace techniques" → "Software Architecture"

Linking Guidelines

1. Always bidirectional - If A links to B, B should link to A 2. Contextual anchors - Explain why the link exists 3. Avoid orphans - Every note should have at least one inbound link 4. Limit outbound - 3-7 outbound links per note is optimal 5. Review regularly - Remove stale or unhelpful links

Anti-Patterns

• Link dumping - Adding links without context
• Self-linking - Circular references within same note
• Overconnection - Linking everything to everything
• Stale links - Links to archived or deleted content

Garden Maintenance

Regular maintenance keeps your digital garden healthy and navigable.

Maintenance Schedule

Daily (5 minutes)

• Add new seeds from today's work
• Quick link to related existing content
• Tag with maturity level

Weekly (30 minutes)

• Review seedlings for promotion to growing
• Fix broken or stale links
• Merge duplicate concepts
• Update timestamps

Monthly (2 hours)

• Promote growing content to evergreen
• Archive inactive content (>30 days)
• Restructure sections if needed
• Review and update hub pages
• Generate metrics report

Tending Actions

Health Indicators

Healthy Garden

• Regular new seeds (1-3 per week)
• Link density > 2 per note
• Minimal orphan notes
• Active tending timestamps

Unhealthy Garden

• No new content for weeks
• Many orphan notes
• Broken links
• Unclear organization