Vault Governance & Doctrine
Relevant source files
The following files were used as context for generating this wiki page:
Vault Governance & Doctrine defines the foundational laws, operational protocols, and architectural standards for IDAHO-VAULT. It establishes a human-centric authority model where Logan Finney (The Architect) directs a "swarm" of AI agents to maintain a journalism research repository. This doctrine ensures that all committed content is "on the record" and publishable while maintaining a strict separation between human creative product and machine procedural output.
The governance framework is distributed across several canonical files, primarily located in the !/ (Swarmic Nest) directory. These files govern note metadata, agent identities, and the lifecycle of vault artifacts, providing a stable "control plane" for a system that is version-controlled via Git and visualized through Obsidian.md.
Sources: CONSTITUTION.md:16-25, VAULT-CONVENTIONS.from-pushable-2026-05-08.md:32-37
Core Principles and Authority
The IDAHO-VAULT operates under a set of non-negotiable core principles that define the relationship between human and machine entities.
Precedence of Authority
When rules or metadata guidance overlap, the vault follows a specific hierarchy:
- Human Direction: Logan's explicit instruction is the highest authority.
- Constitution:
CONSTITUTION.mddefines core identity and constraints. - Vault Conventions:
VAULT-CONVENTIONS.mdgoverns shared routing and write conventions. - Metadata Standard:
VAULT-METADATA-STANDARD.mdoutranks templates for metadata fields. - Templates:
VAULT-TEMPLATES.mddefines specific document classes.
Sources: VAULT-CONVENTIONS.from-pushable-2026-05-08.md:46-55, AGENTS.md:39-49
The Human-Agent Boundary
The doctrine strictly distinguishes between the human owner and the software agents. Logan is the sole human decision-maker; agents are infrastructure that execute his will. This is reinforced by the "Markdown vs. Python" rule: Markdown represents natural-language products (attributable to humans), while Python represents machine-code/procedural products (attributable to agents).
Sources: CONSTITUTION.md:37-43, LEVELSET-v2.md:204-205
Agent Architecture and Identity
The vault utilizes a "Swarm Coordination" model where multiple AI personality-instances (voices) operate within defined capability levels.
Identity Decoupling (Exorcism of the Nomina)
Agents are decoupled from their software names to prevent transient software from becoming permanent authorities. Identity is broken down into four variables:
| Variable | Definition | Example |
|---|---|---|
| NAME | Unique identifier of the vendor/model instance | Claude Code |
| OFFICE | Functional position granted within the vault | Code Authority |
| TITLE | Symbolic moniker used in handoffs | The Clerk |
| ROLE | Transient operational descriptor for a task | Executor |
Sources: VAULT-CONVENTIONS.from-pushable-2026-05-08.md:300-315
The Capability Level Flow
Authority flows outward from the human owner through doctrine and registry, degrading at each downstream step. No lower-layer artifact silently inherits authority from a higher layer.
The diagram represents the "Emanation Rule," showing how authority originates with Logan and is delegated through successive architectural strata.
Sources: CONSTITUTION.md:104-122
Vault Structure and Routing
The vault employs a hybrid structure of root-flat notes and specific system folders.
Root Folder Semantics
| Path | Meaning | Agent Rule |
|---|---|---|
!/ | The Swarmic Nest | Read first for stable system paths; do not restructure. |
Root .md | Primary note corpus | Flat layout is intentional; do not mass-move. |
.*/ | Persona dotfolders | Protected agent chambers; do not delete or clean up. |
.obsidian/ | Obsidian config | Respect sync/git boundaries. |
Sources: VAULT-CONVENTIONS.from-pushable-2026-05-08.md:65-85
Portable Path Standard (NETWEB)
All files must be cross-platform compatible. This standard targets the lowest common denominator between Windows (NTFS), macOS (APFS), and Linux (ext4).
- Case Uniqueness: Filenames must be case-unique within directories.
- Forbidden Patterns: No trailing periods/spaces; no Windows reserved names (AUX, CON, NUL).
- Path Length: Maximum 218 characters from repo root.
Sources: VAULT-CONVENTIONS.from-pushable-2026-05-08.md:468-500
Operational Protocols
Agents must follow standardized lifecycle and orientation protocols to ensure auditability.
LEVELSET Protocol
LEVELSET is a permanent, auditable checkpoint protocol. It is used to synthesize reports from multiple agents into a canonical record before major milestones or session closures. Reports are additive and are never deleted or overwritten.
Sources: LEVELSET-v2.md:15-18, CONSTITUTION.md:130-135
Lifecycle Vocabulary
The vault names intended endings for artifacts to ensure state discipline:
- Live: Operative and authoritative.
- Staged: Active work not yet promoted to canon.
- Superseded: Replaced by newer truth but retained for history.
- Abandoned: Work stopped without promotion; presence confers no legitimacy.
Sources: CONSTITUTION.md:188-198
Sequence of Agent Awakening
The sequence below illustrates the "Binding of Memory" and orientation process.
This diagram shows the "Awaken" and "Orient" protocol flow, ensuring agents establish context before acting.
Sources: VAULT-CONVENTIONS.from-pushable-2026-05-08.md:320-330, CONSTITUTION.md:140-155
Metadata and Template Standards
Standardization of note headers and footers is critical for machine readability and automation.
Frontmatter Requirements
Every governed markdown file must contain YAML frontmatter fenced by ---.
---
title: "<document title>"
updated: YYYY-MM-DD
status: active
authority: "LOGAN"
doc_class: news_media
template_id: tpl-news-media-v1
---
Sources: VAULT-METADATA-STANDARD.md:46-56, VAULT-TEMPLATES.md:104-114
Document Class Registry
| Class | Purpose | Naming Pattern |
|---|---|---|
news_media | Reported stories | YYYY-MM-DD - Outlet - Title.md |
bill | Legislative tracking | (YYYY) Bill Type Number.md |
person | Public figure profile | Full Name.md |
hearing_note | Meeting notes | YYYY-MM-DD - Committee or Meeting.md |
Sources: VAULT-TEMPLATES.md:20-35
Conclusion
Vault Governance & Doctrine provides the "Wizard's Rules" for IDAHO-VAULT, ensuring the integrity of journalism research through rigid identity decoupling, portable path standards, and additive lifecycle logging. By maintaining Logan Finney as the sole decision-maker, the system leverages AI swarms while preventing agentic drift or unauthorized restructuring. The core of this system is the persistence of memory anchored in a version-controlled repository, where chat is ephemeral but the vault is the permanent record.
Sources: CONSTITUTION.md:37-43, VAULT-CONVENTIONS.from-pushable-2026-05-08.md:320-330