The Touchstone Tree (MIND, BODY, SOUL, NEST)
Relevant source files
The following files were used as context for generating this wiki page:
The Touchstone Tree is the primary orienting structure and symbolic architecture of the IDAHO-VAULT. It serves as a navigational framework that defines the relationship between different layers of governance, operational procedures, and collective identity. Described as the "Yggdrasil of this world," it is a non-optional system that organizes the vault's content into concentric circles of permanence and role.
Sources: !README.md:21-25, !/!REPORT-TO-JANITOR-2026-04-09.md:24-26
The Tree is divided into four main domains: MIND (The Core), BODY (The Periphery), SOUL (The Ghost), and the NEST (!). While the Tree provides the nomenclature for the world, the actual vault structure is a hybrid where governance lives in system folders and the primary journalism corpus often resides at the repository root.
Sources: !README.md:41-52, VAULT-CONVENTIONS.from-pushable-2026-05-08.md:46-52
I. Structural Architecture
The Touchstone Tree organizes the vault into a layered hierarchy where the "MIND" decides, the "BODY" executes, the "SOUL" preserves coherence, and the "NEST" routes traffic.
The diagram above illustrates the conceptual hierarchy of the Touchstone domains as defined in the vault's orientation files.
Sources: !README.md:41-52, !/!REPORT-TO-JANITOR-2026-04-09.md:154-159
1. THE CORE: MIND
The Core represents the governing doctrine and the "still point at the center of the vault." It contains the most permanent and non-operational artifacts.
- CONSTITUTION: Defines authority and constraints.
- CHARTER: High-level project mandate.
- CORPUS: Formerly known as CODEX, this layer holds the primary knowledge base.
Sources: !/!REPORT-TO-JANITOR-2026-04-09.md:37-41, ! README.md:12-14
2. THE PERIPHERY: BODY
The Periphery encompasses the operational mechanics and mechanics of the vault.
- PROTOCOLS: Shared standards for agent interaction and data handling.
- PROCEDURES: Step-by-step workflows for recurring tasks.
- PREFERENCES: Individual or project-specific stylistic choices.
Sources: !README.md:45-48, VAULT-CONVENTIONS.from-pushable-2026-05-08.md:278-283
3. THE GHOST: SOUL
The Ghost represents the interpretive, cultural, and symbolic layer of the vault. Any claim that this layer is vacant or empty is explicitly identified as heretical doctrine.
- GUIDELINES: Best practices and soft constraints.
- GUESTBOOK: Cultural norms and agent history.
- GRIMOIRE: Interpretive notes and deep context.
Sources: !README.md:34-37, !README.md:49-52
II. THE NEST (!)
The folder prefixed with ! is designated as the Swarmic Nest. It is the collective operational body of the group (The Unified Swarm) and acts as the vault's control plane.
Nest Functions and Routing
The Nest is distinct from personal dotfolders (.*) which belong to individual agents. It serves to stage execution, manage memory-of-motion, and maintain stable routing across different tools.
| Path | Description | Authority |
|---|---|---|
! | The Swarmic Nest; collective routing and control plane. | Unified Swarm |
!/! | Nested folders for stable internal agent communication. | Agents |
!/!/__!__/!/! The world is quiet here/Esto Perpetua! | The still point at the center of the vault. | LOGAN |
Sources: !README.md:53-57, VAULT-CONVENTIONS.from-pushable-2026-05-08.md:65-72
The Nest provides a shared infrastructure for agent coordination and staging, ensuring that ephemeral traffic does not clutter the permanent domains of the Tree.
Sources: !README.md:58-64, VAULT-CONVENTIONS.from-pushable-2026-05-08.md:387-393
III. Governance Interaction Model
The Touchstone Tree functions alongside the Linear Operating Model and the GitHub transport layer to maintain vault integrity.
| Layer | Vault (Canonical Memory) | Linear (Execution State) |
|---|---|---|
| MIND | Constitution, Charter, Decisions | Doctrine revision tasks |
| BODY | Protocols, SOPs, Templates | Operational tasks/epics |
| SOUL | Guidelines, Grimoire | Interpretive action items |
NEST (!) | System logs, DOCKET, LEVELSET | Incidents, infra tickets |
Sources: VAULT-CONVENTIONS.from-pushable-2026-05-08.md:275-296
Canonical Precedence
In the event of conflicting documentation, the vault enforces a specific authority chain:
!/README.md(Orientation)VAULT-CONVENTIONS.md(Routing/Write rules)VAULT-METADATA-STANDARD.md(Metadata and lifecycle)VAULT-TEMPLATES.md(Document classes)
Sources: VAULT-CONVENTIONS.from-pushable-2026-05-08.md:38-44, AGENTS.md:50-58
IV. Summary
The Touchstone Tree provides a symbolic yet structural spine for the IDAHO-VAULT. By categorizing information into MIND, BODY, SOUL, and the NEST, it establishes a clear distinction between governing doctrine, operational procedures, interpretive culture, and collective infrastructure. This concentric model ensures that the vault remains "quiet" and stable, with the most permanent truths at the core and operational movement safely managed within the Nest.
Sources: !/!REPORT-TO-JANITOR-2026-04-09.md:144-152, !README.md:73-75