/LAF-US/IDAHO-VAULT

Wiki directory

Browse AI-generated documentation for any repository.

Vault Topology & Folder Structure

Relevant source files

The following files were used as context for generating this wiki page:

Introduction

IDAHO-VAULT utilizes a hybrid organizational model designed for personal journalism research, version-controlled via Git and managed through Obsidian.md. The topology is characterized by a "root-flat" design where the primary journalism corpus resides at the repository root, while specialized system, governance, and agent-specific data are siloed into dedicated directories. This structure ensures a clear separation between human-readable research, machine-executable automation, and individual agent runtime environments.

The architecture is governed by a strict hierarchy of authority, prioritizing constitutional documents and shared conventions over localized plugin configurations. The topology also accounts for cross-platform portability, adhering to the NETWEB Path Standard to ensure compatibility across Windows, macOS, and Linux systems.

Sources: [VAULT-CONVENTIONS.from-pushable-2026-05-08.md:32-47](https://github.com/LAF-US/IDAHO-VAULT/blob/5776c621c261e34d84b86cd7a19749a3e9f28f9c/VAULT-CONVENTIONS.from-pushable-2026-05-08.md#L32-L47), [AGENTS.md:52-54](https://github.com/LAF-US/IDAHO-VAULT/blob/5776c621c261e34d84b86cd7a19749a3e9f28f9c/AGENTS.md#L52-L54), [CONSTITUTION.md:52-54](https://github.com/LAF-US/IDAHO-VAULT/blob/5776c621c261e34d84b86cd7a19749a3e9f28f9c/CONSTITUTION.md#L52-L54)

Root Architecture & Semantics

The vault’s root is organized into two primary categories: the "Swarmic Nest" (!/) for collective routing and governance, and individual agent "persona dotfolders" (.*/). The journalism corpus is intentionally kept at the root to avoid over-engineering through deep category nesting.

Core Directory Table

Path	Meaning	Governance Rule
`!/`	The Swarmic Nest: Collective routing, bootstrap aliases, and control-plane breadcrumbs.	Read first for stable system paths; no restructuring without explicit direction.
Repo root	Primary Note Corpus: Working knowledge base for Idaho politics and research.	Root-flat notes are intentional; do not mass-move into subfolders.
`.*/` (e.g., `.claude/`)	Persona Dotfolders: Individual agent shims, governance, and local identity infrastructure.	Protected individual chambers; do not delete or consolidate.
`.obsidian/`	Obsidian Configuration: Application-specific settings and plugin code.	Respect sync/git boundaries; avoid changing without context.
`.github/`	Automation & Workflows: GitHub Actions, scripts, and repository-specific instructions.	Modify only within assigned automation/governance boundaries.

Sources: [VAULT-CONVENTIONS.from-pushable-2026-05-08.md:53-85](https://github.com/LAF-US/IDAHO-VAULT/blob/5776c621c261e34d84b86cd7a19749a3e9f28f9c/VAULT-CONVENTIONS.from-pushable-2026-05-08.md#L53-L85), [CONSTITUTION.md:56-62](https://github.com/LAF-US/IDAHO-VAULT/blob/5776c621c261e34d84b86cd7a19749a3e9f28f9c/CONSTITUTION.md#L56-L62), [CONTEXT-PASTE-BUNDLE.md:50-65](https://github.com/LAF-US/IDAHO-VAULT/blob/5776c621c261e34d84b86cd7a19749a3e9f28f9c/CONTEXT-PASTE-BUNDLE.md#L50-L65)

Topology Visualization

The following diagram illustrates the relationship between the shared Swarmic Nest and the private agent chambers.

Generating architecture diagram...

Journalism Corpus Structure

The research corpus is categorized into thematic directories for information that has reached a certain level of maturity or specific data types. While many notes remain root-flat, the following sub-directories are established for organization:

GOVERNMENTS/: Contains Idaho legislative, executive, and judicial notes.
- IDAHO - LEGISLATIVE/BILLS/: Auto-populated bill tracking notes.
ORGANIZATIONS/: Notes on churches, companies, education, and political parties.
PEOPLE/: Profiles of public figures.
PLACES/: Data on cities, counties, and geography (Idaho and others).
SOURCES/: News media, hearings, editorials, and interviews.
TOPICS/: Subject-area research (e.g., fiscal, health, elections).
X LABELER/: Staging area for unsorted or pending classification files.

Sources: [CONTEXT-PASTE-BUNDLE.md:50-65](https://github.com/LAF-US/IDAHO-VAULT/blob/5776c621c261e34d84b86cd7a19749a3e9f28f9c/CONTEXT-PASTE-BUNDLE.md#L50-L65), [LEVELSET-v2.md:46-58](https://github.com/LAF-US/IDAHO-VAULT/blob/5776c621c261e34d84b86cd7a19749a3e9f28f9c/LEVELSET-v2.md#L46-L58)

Dotfolder Boundary Contract

Each persona dotfolder (e.g., .claude/, .gemini/) operates as a bounded system with three distinct surface types. Agents must respect these boundaries to prevent cross-contamination of identity or runtime data.

OWNER: Writable by the specific agent; other agents may only inspect for orientation.
SHARED: Explicitly named protocol surfaces where multiple agents may write as defined by governance.
ARCHIVE: Preserved historical continuity; read-only unless explicitly reactivated.

Sources: [VAULT-CONVENTIONS.from-pushable-2026-05-08.md:95-108](https://github.com/LAF-US/IDAHO-VAULT/blob/5776c621c261e34d84b86cd7a19749a3e9f28f9c/VAULT-CONVENTIONS.from-pushable-2026-05-08.md#L95-L108)

Persistent Memory Anchoring

Agents are required to maintain a tracked MEMORY/ directory within their dotfolders (e.g., .claude/MEMORY/). This ensures that ephemeral chat plans and "brain artifacts" are promoted to durable .md files in the vault. A session is not considered complete until state is anchored in this folder.

Sources: [VAULT-CONVENTIONS.from-pushable-2026-05-08.md:278-285](https://github.com/LAF-US/IDAHO-VAULT/blob/5776c621c261e34d84b86cd7a19749a3e9f28f9c/VAULT-CONVENTIONS.from-pushable-2026-05-08.md#L278-L285)

Privacy & Security Zoning

The vault includes specialized zones that are excluded from public Git tracking to protect Personal Identifiable Information (PII) and local configuration.

Directory	Purpose	Git Status
`_private/`	Local-only working notes with personal context.	gitignored
`.remember/`	Agent memory buffer (PII risk).	gitignored
`.smart-env/`	AI embedding caches.	gitignored
`DAILYNOTES/`	Ephemeral personal daily notes.	gitignored

Sources: [PRIVACY.md:66-78](https://github.com/LAF-US/IDAHO-VAULT/blob/5776c621c261e34d84b86cd7a19749a3e9f28f9c/PRIVACY.md#L66-L78)

Path Portability Standards (NETWEB)

The vault enforces the NETWEB Path Standard to ensure the repository works across Windows (case-insensitive), macOS (case-insensitive), and Linux (case-sensitive) filesystems.

Constraints and Forbidden Patterns

Forbidden Names: AUX, CON, NUL, PRN, COM0-9, LPT0-9 (Windows reserved names).
Case Uniqueness: Filenames within a directory must be unique regardless of case.
Path Length: Maximum path length is 218 characters from repo root.
Illegal Characters: Colons (:), trailing periods, or trailing spaces are prohibited.

Aliasing Convention

If a note must use a reserved name or causes a collision, it is prefixed with an underscore (e.g., _AUX.md). The original name is then added to the YAML aliases field to maintain wikilink resolution.

Sources: [VAULT-CONVENTIONS.from-pushable-2026-05-08.md:440-475](https://github.com/LAF-US/IDAHO-VAULT/blob/5776c621c261e34d84b86cd7a19749a3e9f28f9c/VAULT-CONVENTIONS.from-pushable-2026-05-08.md#L440-L475)

Summary

The IDAHO-VAULT topology is a dual-purpose structure that supports both human journalistic research and complex multi-agent automation. By centralizing governance in the !/ Swarmic Nest and isolating agent identities in persona dotfolders, the system maintains high integrity and auditability. The rigid adherence to the NETWEB Path Standard and specialized privacy zoning ensures that the vault remains portable and secure across diverse operating environments.

Sources: [VAULT-CONVENTIONS.from-pushable-2026-05-08.md:435-438](https://github.com/LAF-US/IDAHO-VAULT/blob/5776c621c261e34d84b86cd7a19749a3e9f28f9c/VAULT-CONVENTIONS.from-pushable-2026-05-08.md#L435-L438), [CONSTITUTION.md:225-235](https://github.com/LAF-US/IDAHO-VAULT/blob/5776c621c261e34d84b86cd7a19749a3e9f28f9c/CONSTITUTION.md#L225-L235)