The vault precinct is the zone within the deep context architecture for operational knowledge work. Meetings get captured, contacts get tracked, daily notes record what happened, research gets clipped and filed, reference material gets organized. The vault solves the problem of not losing things — capturing information at the speed of work and making it findable later.
Vault content uses the same predicate infrastructure as garden nodes (is_a::, has_status::, attendee::, derived_from::) but follows lighter conventions. A meeting note has a template and expected sections, not a structural contract with enforceable constraints. The priority is capture speed and retrieval, not compositional rigor.
Meetings/, People/, Daily/, Research/, Notes/, Clippings/, References/The vault precinct uses typed predicates now — is_a::[\[\[Meeting Note\]\]↑](../NODES.html#:~:text=Meeting%20Note), attendee::[\[\[Person Name\]\]↑](../NODES.html#:~:text=Person%20Name), derived_from::[\[\[Parent Note\]\]↑](../NODES.html#:~:text=Parent%20Note). The current lighter adoption is a tactical sequencing choice: learning the pattern in the garden first, then extending it vault-wide. Predicates are shared infrastructure, not a garden-only feature. The [[Classification via Predicates Not Tags]]↑ decision applies across both precincts.
Both precincts share the deep context infrastructure and coexist as peers. The vault handles fast capture and daily operations; the garden handles slow curation and durable knowledge. Content moves between them — a meeting decision becomes a Decision Form, a research thread becomes an Inquiry — but this is lateral movement between zones with different purposes, not promotion from informal to formal.
Term adopted from urban planning via [[Precinct as Organizational Unit]]↑.