File Vault

Available on Standard tier and above.

What Is the File Vault?

The File Vault is your persistent document storage within Tempreon. While the Knowledge Vault stores facts and insights (text-based records), the File Vault stores complete files — documents, specs, plans, research reports, code snippets, or any other deliverable you want to access across sessions.

How Files Get Stored

Through Your AI

The most natural way to store files is through conversation:

• "Save this migration plan as a spec document" — Saves the content as a file
• "Store this analysis in my File Vault for the marketing project" — Saves with Domain context
• "Save this as 'Q3-roadmap.md'" — Explicit filename

Your AI handles the rest — filename, classification, and storage.

File Attributes

Each file in the vault has metadata:

• Filename — What the file is called (e.g., design-spec.md)
• Category — How the file functions:
  • Reference — Background material
  • Deliverable — Work product
  • State — Snapshot of current status
  • Direction — Decisions and guidance
• Lifecycle Stage — Where the file is in its journey: Working → Review → Final → Archived
• Tags — For organization and discoverability
• Domain — Which Domain the file belongs to (if any)
• Description — What the file contains

Browsing and Searching

The File Vault page lets you:

• Search by filename to find specific documents
• Filter by category (Reference, Deliverable, State, Direction)
• View metadata including size, lifecycle stage, tags, and description

Retrieving Files in Session

Your AI can pull files from the vault during any session:

• "Find my previous GTM documentation" — Semantic search across your files
• "Get the design spec I saved last week" — Retrieve by description
• "What files do I have for the Acme project?" — Browse by Domain

Try Saying...

• "Save this report as a deliverable for the consulting project" — Store with category and Domain
• "Update the project status doc with today's progress" — Modify an existing file
• "What reference documents do I have?" — Browse by category
• "Save this code snippet for future reference" — Quick storage of any content

Use Case: Cross-Session Document Continuity

Jake is a product manager who writes specs across multiple sessions. In session 1, he drafts the problem statement and saves it: "Save this as 'feature-spec-auth-v1.md', it's a working deliverable for the Platform project." In session 2, he picks up where he left off: "Get my auth feature spec." His AI retrieves the file, and Jake continues writing. When it's ready for review, he updates the lifecycle: "Move the auth spec to review stage." The file persists, evolves, and stays organized without leaving the conversation.