internal-vault-routing

What problem does it solve?

The vault is the local context layer. CRM is system-of-record for live state, while Obsidian notes provide durable memory and cross-medium context. This skill coordinates vault-prefetch, customer roster, and connect hooks to route and enrich local knowledge.

Core Features & Use Cases

• Vault tools and scope: get_vault_context, get_customer_context, oil_get_opportunity_context, oil_get_milestone_context, prepare_crm_prefetch, search_vault, query_notes
• Correlate and promote: resolve_people_to_customers, correlate_with_vault, promote_findings, capture_connect_hook
• Entity sync writes (gated): oil_create_opportunity, oil_update_opportunity, oil_create_milestone, oil_update_milestone, manage_pending_writes
• Vault standards: Entity Icon & Link Standards, MSX record links, and frontmatter requirements
• Vault lifecycle: VAULT-PREFETCH, VAULT-CORRELATE, VAULT-PROMOTE, VAULT-SYNC, and fallback behavior
• References to vault-sync templates for structured notes (customer, opportunity, milestone, people, project)

Quick Start

Run the vault routing workflow to prefetch customer context and align local vault notes with CRM data.