Skip to content

Vaults overview

The four-tier vault model - L1 through L4 - and how tier inheritance resolves configuration conflicts.

Last updated: 2026-04-30

Vaults overview

A vault is the fundamental organizational unit in Flexor. It is a directory with a defined structure, a tier designation, and a configuration file (vault.json). Everything Flexor knows about how to behave in your environment lives in a vault.

The four-tier model

Flexor uses four vault tiers. Each tier has a defined scope and ownership model:

L1 - Platform tier

The platform vault is managed by PLEXI. It contains:

  • The standard skill library (data catalog queries, notification dispatchers, audit writers, report formatters)
  • System-level configuration and defaults
  • The base knowledge index (Flexor documentation, skill reference)

You do not write to L1. You read from it when your skills invoke standard library actions.

L2 - Company tier

The company vault is managed by your organization. It contains:

  • Shared skills written for your firm’s specific data environment
  • Agents that run across the firm (firm-wide monitoring, shared reporting)
  • Company-level rules and policies (SLA thresholds, notification routing, compliance constraints)
  • Shared knowledge documents (data dictionaries, fund parameters, escalation contacts)

All operators in a firm share L2. Changes to L2 affect everyone. Apply the same change-management discipline here that you would to any shared infrastructure.

L3 - Personal tier

The personal vault is specific to one operator. It contains:

  • Personal configuration overrides (preferred output formats, Slack notification routing)
  • Experimental skills being tested before promotion to L2
  • Personal agents for individual use cases

L3 overrides L2 for the operator who owns it. If a company-level skill defines a default output format but an operator prefers a different one, they override it in their personal vault.

L4 - Project tier

The project vault is scoped to a specific workflow, initiative, or engagement. It contains:

  • Agents and skills specific to one project
  • Temporary configurations (e.g., a custom data connection for a migration project)
  • Project-specific knowledge documents

L4 overrides L3, L2, and L1 within its scope. When the project ends, the L4 vault is archived or deleted.

Tier resolution order

When Flexor needs a configuration value, a skill, or a knowledge document, it searches tiers in this order:

L4 (project) → L3 (personal) → L2 (company) → L1 (platform)

The first match wins. This means:

  • A project-level skill with the same name as a company-level skill overrides it for that project
  • A personal rule overrides a company rule for that operator only
  • If nothing is found at L4 through L2, the platform default (L1) applies

Vault sync

Vaults are synchronized from source to the Flexor runtime using flexor sync. After any change to a vault source directory, run sync before running agents that depend on the changed content.

flexor sync --vault company

Important: Agents load vault state at startup. Vaults that have been modified but not synced will run against the previous state. Always sync after structural changes (new skills, new agents, modified rules).

Was this page helpful?

Edit on GitHub