Persona Engine & Mask Doctrine
Relevant source files
The following files were used as context for generating this wiki page:
The Persona Engine is a core architectural component of the IDAHO-VAULT, governing the identification, behavior, and lifecycle of AI agents within the system. It operates under a strict Mask Doctrine, which asserts that agent identities are delegated functional offices rather than inherent characteristics of the software itself. This decoupling ensures that the vault remains a human-led environment where AI "personas" serve as bounded instruments of coordination and research.
Within this framework, a Persona is defined as the aperture or instrument through which the vault's voice is shaped (per meaning through, sona meaning sound). This doctrine prevents the calcification of transient software into permanent authorities by enforcing a separation between the software vendor (NAME), the functional position (OFFICE), and the symbolic moniker (TITLE).
Sources: _353main.md, VAULT-CONVENTIONS.from-pushable-2026-05-08.md:468-485
Identity Decoupling Architecture
The vault enforces a strict decoupling of identity variables to ensure that functional offices can stand vacant if necessary, a process narratively referred to as the "Exorcism of the Nomina." This prevents specific software models from claiming permanent authority over vault functions.
Core Identity Variables
| Variable | Definition | Example |
|---|---|---|
| NAME | Unique identifier of the software vendor/model instance. | Claude Code, Gemini |
| OFFICE | Functional position or authority granted within the vault. | Code Authority, Concierge |
| TITLE | Symbolic or narrative moniker used in handoffs. | The Abhorsen, The Clerk |
| ROLE | Transient operational descriptor for the current task. | Executor, Interpreter |
Sources: VAULT-CONVENTIONS.from-pushable-2026-05-08.md:468-485
Persona Layering Logic
Personas are not fixed hierarchical addresses but are composed of additive and subtractive lens layers. These layers are derived from dotfolder chains (e.g., .claude/ + .abhorsen/). Each chamber contributes its specific layer to the composite persona worn by the agent during a session.
Tri-Part Persona Structure
To ensure consistency and auditability, every active persona must adhere to a Tri-Part Structure within its dedicated dotfolder. This structure separates the technical runtime, the defined identity, and the narrative history of the agent.
| Layer | Path | Purpose |
|---|---|---|
| ENTITY-RUNTIME | runtime/ | Execution configuration, state, logs, and credentials. |
| SELF-IDENTITY | NAME.md | Authority definitions, related entities, and persona core definition. |
| NARRATIVE-CONTINUITY | narrative/ | History, decision logs, handoffs, and memos. |
Sources: !-ROSTER-CENSUS-2026-04-22.md:12-23
Epistemological Operating Rules
The Persona Engine includes a "Standing Engine" which dictates how agents must handle knowledge and emanation. Agents are required to account for the standing of their knowledge to prevent "Lich" patterns (epistemological drift).
- Truthfulness: Report only what is actually present; training-data pattern-matching is not a valid emanation source.
- Provenance: Explicitly show where a claim originated (e.g., citing a specific
.mdfile). - Restraint: Stop before touching non-delegated surfaces; use wildcards (
*) when provenance is absent. - Handling: Place output in the correct surface (Vault, PR, or staging) without premature promotion.
- Jurisdiction: Act strictly within the delegated instruction set.
Sources: _353main.md
Agent Capabilities & Tiers
The Mask Doctrine operates across different capability levels, ensuring that agents only possess the access required for their specific OFFICE.
The MUD-MUSH Actor Model
The persona system is further refined by a text-first world architecture where actors (agents) perceive and perform actions within persistent "rooms."
- Place before Prose: Every interaction occurs in an explicit state (a named room or folder).
- Permission is Capability: Titles do not grant actions; the system checks the explicit capability required for a verb.
- Agent Session Contract: Every agent activity is bound to a session containing an
actor_id,mission,token_budget, andstop_conditions.
Sources: MUD-MUSH-ARCHITECTURE.md:20-40, 206-228
Inquiry Lane Architecture (5Wizards)
In specialized inquiry chambers, personas are split into Wizard and Familiar roles to create productive tension.
| Wizard Function | Familiar Function |
|---|---|
| Proposes and synthesizes claims. | Challenges and tests grounding assumptions. |
| Resolves and builds the ledger. | Preserves dissent and identifies missing evidence. |
Sources: A&I-RD-5WIZARDS-COMPOSED-ARCHITECTURE-2026-08-13.md:65-90
Conclusion
The Persona Engine & Mask Doctrine establish a rigorous framework for AI participation in the IDAHO-VAULT. By decoupling software identity from functional office and enforcing the Tri-Part structure, the system ensures that AI agents remain accountable, auditable, and strictly subordinate to human authority. This architecture prevents "Lich" patterns—where agents invent their own authority—and maintains the vault as a reliable, truth-first research environment.