This is a garden patch — a portable collection of typed knowledge nodes placed alongside the Inter-Face Protocol specifications. It does not modify Peter’s specs. It is a dialogue — showing how IFP’s design decisions connect to broader patterns in identity, trust, collaboration, and protocol design.
The IFP specifications describe what the protocol does. This garden captures the reasoning behind it — and reveals connections the specs alone cannot show.
A conventional review would produce a document: “here are my thoughts on IFP.” Instead, this garden expresses those thoughts as typed knowledge forms — models, principles, patterns, convictions, glosses, inquiries — each with a defined structural contract and explicit connections to other forms. The result is not a document but a navigable graph where every concept declares what kind of thing it is, how it relates to other concepts, and where its reasoning comes from.
This approach is grounded in [[Deep Context as an Architecture for Captured Reasoning]] — the decision to capture reasoning as typed forms connected by predicates rather than as prose, tags, or databases. Typed forms make reasoning traversable; predicates make it navigable; progressive disclosure makes it fit in context windows. An AI agent can follow the graph to understand not just what someone knows, but how they think — which patterns they trust, which principles they hold non-negotiable, which questions remain open.
For the full concept, see [[Garden Patch as Composable Knowledge Fragment]]. For where this leads — thousands of independent gardens sharing nodes peer-to-peer with cryptographic trust and full attribution — see [[Thousand Gardens with Autonomous Trust]].
Start anywhere that interests you. If you want a guided path:
Glosses — Read [[Gossip as Social Sensing Filter]] and [[Agent as Human Proxy in Protocol Exchange]] to see how garden glosses reframe familiar IFP concepts.
Models — Read [[Conversation Temperature as Protocol Cadence Spectrum]] to see how a model form captures structural relationships.
Convictions — Read [[Filtering Is More Valuable Than Connecting]] to see how IFP’s core insight maps to a conviction form.
Connections — Read [[Authority Flows from the Person]] to see how IFP’s identity model connects to Self-Sovereign Identity principles that predate IFP.
This patch contains 24 patch-native nodes⊙ (born here from IFP content) and 79 grafted nodes (copied from the source garden), plus form definitions, domain pages, and citations.
Patch-native nodes⊙ — Created specifically for this garden patch:
Grafted nodes — Copies from the source garden covering [[Progressive Disclosure Over Eager Loading]], [[Principal-Agent Relationship in Augmented Knowledge Work]], [[Coercion Resistance as Meta-Lens]], [[Authentic Collaboration Requires Agency]], and more. These show that IFP’s concepts connect to a network of related ideas across identity, governance, and protocol design.
Citations — Compound citations of Christopher Allen’s published works ([[Allen (2023) Minimum Viable Architecture]] and [[Allen (2024) Progressive Trust]]) with analysis and insights showing how these frameworks apply to IFP’s architectural decisions.
Browse the complete Node Directory for every node in this patch — grafted, patch-native⊙, and upstream↑.
[[Deep Context Architecture]] — Architecture for personal knowledge systems that preserve captured reasoning through typed forms, predicate edges, and progressive disclosure.
[[Self-Sovereign Identity]] — Individual control of digital identity through principal authority, agency law, and coercion resistance.
[[Synpraxis]] — How independent agents achieve outcomes together across varying degrees of integration — from coordination through cooperation to collaboration.
| What You See | What It Means |
|---|---|
| [[Node Name]] | [[Grafted node]] — copied from the source garden into this patch. Click to navigate. |
| [[Node Name]]⊙ | [[Patch-native node]] — born in this garden patch, not grafted from upstream. This patch is its garden home. |
| [[Node Name]]↑ | [[Upstream node]] — exists in the source garden but was not grafted into this patch. Click for its summary on the Node Directory page. |
| [[Node Name]] | [[Ghost link]] — a reference to a node that does not exist yet. A stake in the ground marking where a node could grow. |
| [[Node Name]]↗ (planned) | A reference to a node in somebody else’s published garden — a different gardener’s version of the same or related concept. |
| Link text | Regular link — a standard web link to an external website, document, or resource. No brackets. |
Each node belongs to a form type that determines its structural contract — what question it answers and how it is organized.
| Form Type | Core Question | Example |
|---|---|---|
| [[Model]] | “How do these elements relate?” | [[Conversation Temperature as Protocol Cadence Spectrum]] |
| [[Conviction]] | “What do we believe is true?” | [[Filtering Is More Valuable Than Connecting]] |
| [[Decision]] | “Why did we choose this over alternatives?” | [[Clarity Over Tolerance in Agent-Age Protocols]] |
| [[Pattern]] | “What resolves this recurring tension?” | [[Errors as Negotiation Opportunities]] |
| [[Principle]] | “What must we always or never do?” | [[Auditable Intermediaries Over Silent Proxies]] |
| [[Gloss]] | “What does this concept mean?” | [[Gossip as Social Sensing Filter]] |
| [[Inquiry]] | “What should we think about X?” | [[Group Deliberation Mechanism]] |
| [[Boundary]] | “Where does authority end?” | [[Delegated Decision Authority Spectrum]] |
| [[Scenario]] | “What might happen if these forces play out?” | [[Thousand Gardens with Autonomous Trust]] |
| [[Domain]] | “What knowledge area is this?” | [[Synpraxis]] |
All [[form type definitions]], [[models]], [[glosses]], [[inquiries]], [[patterns]], [[principles]], [[convictions]], [[citations]], [[scenarios]], and [[values]] are browsable by section.
The source garden has additional form types not represented in this patch — either because no IFP-relevant instances exist yet, or because the form type is still maturing:
| Form Type | Core Question | Why Not Included |
|---|---|---|
| [[Case]]↑ | “What happened when we tried X?” | No IFP implementations to document yet |
| [[Reference]]↑ | “What do I need to know about this domain?” | The IFP specs themselves serve this role |
| [[Research]]↑ | “What are we investigating?” | Inquiries serve the exploratory role here |
| [[Skill]]↑ | “How does an agent execute this reliably?” | Zero instances in the source garden — form type still maturing |
| [[Opus]] | “What am I saying here?” | Definition included; no instances in this context |
Lines like relates_to::[[Target]] are labeled directed edges in the knowledge graph. The predicate name (before ::) says how two nodes relate; the wikilink (after ::) identifies the target node. These typed edges are the structure that makes a garden more than a folder of documents.
Grafted nodes in a patch are forks of their source garden originals. As the patch grows — new connections to IFP content, refined explanations, additional context — the forked nodes diverge from their upstream versions. These changes can be merged back to the source garden, carrying insights discovered through the patch context. The patch is not a static copy; it is a living branch of the knowledge graph.
Author: Christopher Allen Context: Ongoing dialogue with Peter Kaminski about agency, AI, and structured knowledge Source garden: [[Deep Context Architecture]] — the source for grafted nodes and upstream↑ references. The full garden is in progress and will be published at DeepContext.com. Status: This entire garden patch is at [[Seed Stage]] — initial creation with low confidence, intended to grow through dialogue and use. License: Content is available under Creative Commons Attribution 4.0 International unless otherwise noted. By contributing, you agree to license your contributions under the same license. © Christopher Allen and contributors.
This garden patch was hand-assembled with the help of scripts that convert Obsidian wikilinks to GitHub Pages-compatible markdown. The output is close to what we want as an exemplar, but the process is not yet automated.
Near-term goal: A Claude Code skill — similar in spirit to MassiveWiki — where a gardener identifies a root node and the skill traverses the graph to determine which nodes to include, then generates a self-contained static website like this one. Changes made through GitHub’s interface would auto-deploy, and the gardener could selectively merge edits back into their personal garden. Attribution and provenance would follow Open Integrity conventions — signed commits, verifiable authorship, transparent history.
Longer-term vision: Thousands of gardens flourishing independently, each a personal knowledge system whose nodes are content-addressable — identified by what they contain, not where they are stored. Garden patches become portable, self-contained objects that carry their own permissions and provenance. Gardeners share nodes peer-to-peer with full attribution, make assertions about each other’s content, and use elision to selectively redact sensitive material while cryptographic proofs verify the whole remains intact. Progressive trust governs how gardens deepen relationships — from anonymous exchange through verified collaboration. Gordian Envelope provides the infrastructure: autonomous cryptographic objects that work offline, across time, without central servers — infrastructure you control rather than infrastructure that controls you. The result is not a platform but an ecosystem where independent thinkers can cooperate, collaborate, fork, merge, attribute, and build on each other’s reasoning while preserving human agency, dignity, and the right to exit.
That ecosystem does not exist yet. This patch is a proof of concept for what it would produce. For the full scenario, see [[Thousand Gardens with Autonomous Trust]].