Capabilities Overview
Jorvis Capabilities Overview
Status: Active overview
This document is a high-level architecture-facing summary of what Jorvis currently exposes.
For current capability truth, see:
Platform Summary
Jorvis is a data-focused AI platform centered on:
- natural-language Text-to-SQL
- OpenAI-compatible backend routes
- Open WebUI as the canonical chat/auth surface
- local Ollama fallback for resiliency and offline-capable paths
Implemented vs Enabled vs Future
Use the categories below when reading capability status:
| Category | Meaning |
|---|---|
| Implemented | Present in code and documented in current repo truth |
| Enabled | Verified as part of the active production/runtime path |
| Future | Intended direction or approved architecture, but not yet current runtime truth |
Examples:
- Observability stack: implemented; production enablement should be verified per deploy
Current High-Level Capability Map
| Capability Group | Current Status |
|---|---|
| Text-to-SQL | Production |
| GraphRAG / schema-aware retrieval | Production |
| Open WebUI integration | Production |
| Document RAG / Knowledge Base | Production |
| Voice gateway | Production |
| Monitoring / observability stack | Verified current baseline |
Current Runtime Surfaces
Open WebUI / model surfaces
jorvisauto— primary demo/public modeljorvis_local— local Ollama fallbackjorvis-anydb— script-managed custom OpenAI-compatible registration target
Architectural Nuance
Memory
The current memory architecture is described in the knowledge-engine.md document.
Multi-tenancy
Multi-tenancy is not currently active in production. See the historical reference in multi-tenancy.md.
Non-Canonical Historical Surfaces
These are not current architecture truth:
- large historical Open WebUI function bundles
- old
jorvis-brainmodel references - Apache AGE-based GraphRAG claims
- historical “Semantic Memory removed” / “Multi-Tenancy removed” simplifications