ifp

← Garden Patch Home · Scenarios

• is_a::[[Scenario Form]]
• has_status::[[Seed Stage]]
• in_domain::[[Deep Context Architecture]]

Thousand Gardens with Autonomous Trust

The Scenario

This garden patch is a proof of concept. What it proves is small: one gardener can express another person’s work through typed knowledge forms and reveal connections that prose cannot show. But the forces behind it point somewhere larger.

If knowledge gardens adopt content-addressable identifiers — nodes identified by what they contain, not where they are stored —

And if gardens wrap their nodes in Gordian Envelope — autonomous cryptographic objects that carry their own permissions, provenance, and verifiability without depending on servers or platforms —

And if gardeners use progressive trust to deepen relationships — from anonymous exchange through verified collaboration, mirroring how trust builds in the physical world —

Then thousands of independent gardens could flourish without central coordination. Gardeners would share nodes peer-to-peer. Each node would carry its full attribution chain. Elision would allow selective redaction — sharing reasoning while protecting sensitive context, with cryptographic proofs verifying that the redacted whole remains intact. Peer-to-peer assertions would let gardeners comment on, endorse, challenge, or extend each other’s nodes without requiring permission from the original author.

What This Changes

The current model for shared knowledge is the platform: Wikipedia, Notion, Google Docs, Slack. Platforms own the infrastructure, set the rules, and control exit. A garden ecosystem inverts this. Each garden is sovereign. Sharing happens through portable objects, not through platform APIs. Trust builds progressively, not through administrative approval. Attribution follows the content cryptographically, not through platform metadata that disappears when you export.

The garden patch pattern — fork, diverge, merge back — becomes the basic unit of intellectual collaboration. A gardener in São Paulo forks a node from a gardener in Osaka, adds connections to local context, and offers the enriched version back. The original gardener reviews the diff, accepts the additions, and both gardens grow. No platform mediated the exchange. No administrator approved it. The cryptography proves who contributed what.

Preconditions

• Content-addressable node identifiers (hash-based, not path-based)
• Gordian Envelope or equivalent for autonomous cryptographic objects
• Progressive trust implementation for garden-to-garden relationships
• Elision support for selective disclosure of garden content
• A merge protocol for reconciling divergent forks of the same node
• Open Integrity conventions for signed commits and verifiable authorship

Open Questions

• How do gardens handle conflicting assertions about the same node?
• What is the right granularity for content-addressable identifiers — individual nodes, predicates, or entire patches?
• How does progressive trust scale beyond bilateral relationships to garden communities?
• What exit rights does a contributor retain after their nodes are forked and modified by others?

Sources

• Gordian Clubs: Preserving Agency When Infrastructure Fails
• Progressive Trust
• Musings of a Trust Architect — Christopher Allen’s blog series on trust, identity, and human agency
• This garden patch — the first proof of concept

Relations

• relates_to::[[Deep Context as an Architecture for Captured Reasoning]]
  • The architecture that makes gardens possible — typed forms, predicates, progressive disclosure.
• relates_to::[[Garden Patch as Composable Knowledge Fragment]]
  • The garden patch pattern is the basic unit of collaboration in this scenario.
• relates_to::[[Authority Flows from the Person]]
  • Each garden is sovereign. Authority over knowledge flows from the person, not from a platform.
• relates_to::[[Authentic Collaboration Requires Agency]]
  • Without agency — the right to exit, to fork, to selectively disclose — collaboration is compliance.

This site is open source. Improve this page.