Vault Routing
Vault routing analyzes the content of each knowledge item and automatically sends it to the most appropriate vault. Security findings go to the security vault, architecture decisions to the architecture vault, project gotchas to the project vault. Rules are configurable in plain English.
How it works
Routing rules are defined in your KnowzCode configuration using natural language: 'Security vulnerabilities and authentication patterns go to vault security-patterns', 'Database schema decisions go to vault data-architecture'. When knowledge is created (via /knowz save, the Closer agent, or MCP tools), the content is analyzed against all rules. The best-matching vault receives the entry. If no rule matches or multiple rules match equally, the system asks for clarification.
Vault routing rules matching content to appropriate vaults
Screenshot coming soon
Why it matters
Without routing, all knowledge ends up in a single vault, making it hard to find and manage. With routing, each vault develops a coherent focus: security patterns, architecture decisions, project conventions, debugging tips. This structure makes search more effective (searching the right vault yields better results), browsing more intuitive, and maintenance easier (vault owners can curate their domain).
Organized vaults with clearly categorized knowledge items
Screenshot coming soon