The garden precinct is the zone within the deep context architecture where knowledge is curated into typed forms with structural contracts. Each form type (pattern, model, decision, gloss, inquiry, etc.) defines a shape — required sections, a core question, enforceable constraints. Forms are tended through growth stages from Seed to Evergreen, connected by typed predicates, and organized into knowledge domains.
The garden solves the problem of making knowledge retrievable, composable, and trustworthy over time. A pattern form always has a tension, resolution, and consequences. A decision form always records context, alternatives, and consequences. This predictability makes the knowledge graph navigable by both humans and LLMs.
| Garden nodes are [[[Living Documents Over Static Publications | living documents]]↑](../NODES.html#:~:text=Living%20Documents%20Over%20Static%20Publications%7Cliving%20documents). They grow through stages, absorb new connections, and are never “published” in the way an article or book is. Git preserves their history, but the current state is what readers and agents encounter. This distinguishes the garden from publication-oriented knowledge systems where value concentrates in a specific released version. Mutability varies by form type — most nodes are designed to evolve, while cases record immutable history and convictions change only through fundamental shifts. |
The garden and vault precincts share infrastructure — predicates, graph scripts, typed edges — but serve different purposes. The vault captures and organizes operational knowledge (meetings, daily notes, research intake). The garden curates and interconnects durable knowledge. Content may move between precincts: a decision made in a meeting (vault) becomes a Decision Form (garden) via extraction. This graduation is lateral movement between zones that solve different problems, not promotion up a hierarchy.
Term adopted from urban planning via [[Precinct as Organizational Unit]]↑.