Knowledge Vaults
Four-Tier Knowledge
Architecture
Institutional knowledge that compounds. Every observation becomes a rule, every rule becomes knowledge, every knowledge file shapes agent behavior. Persistent across sessions and tool switches.
Architecture
Layered Knowledge, Unified Access
Each tier builds on the one below. The materialization pipeline merges all layers at runtime, with higher tiers overriding lower.
Platform Knowledge
Core platform knowledge shared across all Flexor installations. Defines agent behavior, skill specifications, system rules, and domain best practices. The foundation layer - every other tier overrides it.
Company Knowledge
Organization-specific knowledge that differentiates your operations. Brand guidelines, pricing frameworks, competitive intelligence, SOPs, and team structure - version-controlled and merged on top of L1.
Personal Knowledge
Individual context that follows you across projects. Voice, writing style, decision patterns, and working preferences. Layers on top of company knowledge - overrides L2 and L1 for the same entity.
Project Knowledge
Active context for the current engagement. Materialized from all lower tiers then extended with project-specific rules, task memory, and session observations. The most specific layer - overrides everything below.
How It Works
Materialization Pipeline
At task time, the vault engine merges relevant knowledge from all layers into a unified context window for the active agent.
Observe
Agent notices a pattern, preference, correction, or new insight during daily work.
Record
Observation is written to the appropriate vault layer as structured, searchable knowledge.
Promote
Recurring patterns are promoted upward: observations become rules, rules become knowledge files.
Materialize
At runtime, all layers merge. Higher tiers override lower. Agent behavior shaped automatically.
Features
Built for Teams That Need Knowledge They Can Trust
Every feature designed for version-controlled, auditable, scalable institutional knowledge.
Version-Controlled
Every knowledge file is a git-tracked file. Full history, rollback, diff, and audit. Knowledge management with the same toolchain as code.
Override Composition
L4 wins over L3 wins over L2 wins over L1. Same entity in two tiers? Higher tier is used. Unique entity in one tier? Included as-is. No conflicts - just precedence.
Section Merge
Rules files with complementary sections can opt into H2-level deep merge instead of whole-file replacement. Add merge-strategy: section to frontmatter.
Provenance Tracking
Every entity in the materialized view records which vault it resolved from. flexor why <entity> shows exactly where the active version came from.
Compounding Knowledge
A System That Compounds Institutional Intelligence
Flexor's knowledge vaults form a continuous learning loop. Every interaction generates observations. Observations become rules. Rules become knowledge. Knowledge shapes future behavior.
The result: a system that preserves what works across sessions and surfaces lessons where the work happens - not in a separate documentation tool that nobody reads.
Knowledge That Compounds
See how Flexor's four-tier vault architecture turns your team's expertise into permanent organizational intelligence.