Ask VaultLens

Same pipeline every time: your demo role decides which documents can be quoted. Retrieval scores both allowed and restricted matches — answers never include text from sources outside your allow list. The public demo uses deterministic retrieval and templated answers (no generative model).

Demo mode (this build)

  • Deterministic retrieval
  • Synthetic documents
  • Role-based access checks
  • Citation-first answers
  • Session audit

Production-style path (future)

  • Supabase/Postgres persistence
  • pgvector (or similar) retrieval
  • Generative answers from allowed chunks only

Engine: deterministic retrieval + citation rules today. Future stack: Supabase + pgvector + optional LLM — only after access filtering selects allowed chunks.

  1. Role
  2. Question
  3. Access filter
  4. Retrieval
  5. Cited answer
  6. Audit

Demo role (not SSO)

Pick a persona → ask a question → VaultLens filters by this allow list before quoting anything. Switching roles is how you compare who may see which citations (demo only, not SSO).

Guided demo (3 steps)

A Allowed answer · B Restricted hold · C Same question with a higher-privilege role → citations.

Suggested for Manager

Ready for a query

Use the guided buttons above, or type your own question. You will always see either cited sources, a permission hold, or insufficient evidence in the allowed corpus — never a silent guess.

Audit log stores each run. Evaluation regression-tests permissions and citations.

Responsible use (demo)

  • Public demo uses synthetic documents only. Do not upload private files in v1.
  • Restricted documents are never revealed to roles that cannot access them.
  • Grounded answers require cited sources; support scores are retrieval heuristics, not guarantees.
  • When in doubt, have a subject-matter expert review the answer in production.