soleri-agent-devlisted

# Agent Dev — Vault-First Internal Development Develop the agent's own internals with the vault as the primary source of truth. The vault knows more about the agent than any code scan or model training data. Always search the vault first, extract maximum context, and only then touch code. ## When to Use Any time the work target is the agent's own codebase: adding tools, extending facades, modifying vault operations, brain features, skills, or transport. Not for projects that merely _use_ the agent. ## Core Principle **Vault first. Before code. Before training data. Always.** The vault is the authoritative source for how the agent works. Do not rely on general knowledge from training data — it is outdated and lacks project-specific decisions. Do not scan the codebase to understand architecture — the vault already has it. ## Orchestration Sequence ### Step 1: Search the Vault (MANDATORY — before anything else) Before reading any source file, before making any plan, before offering any advice: ``` YOUR_AGENT_core op:search_intelligent params: { query: "<description of planned work>", type: "pattern" } ``` Search again with architecture-specific terms: the facade name, tool name, or subsystem being modified. ``` YOUR_AGENT_core op:search_intelligent params: { query: "<facade, tool, or subsystem name>", type: "workflow" } ``` If initial results are sparse, search again with broader terms — synonyms, related subsystem names, parent concepts. Exhaust the vault befor