How albertoracerro/jarvisos_v1 works
JarvisOS is a local-first engineering R&D workspace that brings project records, AI assistance, simulation, CAD/CAE, and evidence into one operator workflow. An engineer works from the frontend, manages project knowledge and engineering inputs, runs studies or engineering tools, and inspects results and provenance. AI requests pass through JarvisOS execution and egress policy before reaching a local model or an approved external provider. The README documents several additional product branches; their internal wiring is not established by the sampled excerpts, so those links are kept broad or omitted.
Main entry points: main.py Application API · gateway.py AI execution · App.tsx Operator UI · routes.py AI request routes
Components 22
Operator workstation
- Operator UI
frontend/src/App.tsx - UI routing
frontend/src/app/useAppRouter.ts - API client
frontend/src/api/client.ts
Project knowledge
- Engineering records
backend/app/modules/modeling/routes.py - Project knowledge
backend/app/modules/project_knowledge/routes.py - Literature
backend/app/modules/memory/literature_routes.py - Project search
backend/app/modules/project_search/routes.py
Engineering workflow
- Run execution
backend/app/modules/runner/routes.py - Process models
backend/app/modules/process_kernel/flowsheet.py - Engineering studies
backend/app/modules/engineering/studies.py - BLUECAD
backend/app/modules/bluecad/routes.py - Run evidence
backend/app/modules/bluecad/evidence.py
AI and agents
- AI request routes
backend/app/modules/ai/routes.py - AI execution
backend/app/modules/ai/gateway.py - Egress policy
backend/app/modules/ai/egress_service.py - Provider registry
backend/app/modules/ai/provider_registry.py - Hermes agent
backend/app/modules/agents/hermes/routes.py
Runtime integrations
- Application API
backend/app/main.py - SQLite state
backend/app/core/database.py - Local model runtime
backend/app/modules/local_ai/runtime/routes.py
Other components
- Engineer
- External AI provider
Connections 23
- Engineer → Operator UI: operates
- Operator UI → UI routing: resolves routes
- Operator UI → API client: requests data
- API client → Application API: calls API
- Application API → Engineering records: dispatches records
- Application API → Project knowledge: dispatches knowledge
- Application API → Literature: dispatches literature
- Application API → Project search: dispatches search
- Engineering records → SQLite state: reads and writes
- Project knowledge → SQLite state: reads and writes
- Literature → SQLite state: reads and writes
- Application API → Run execution: dispatches runs
- Run execution → Process models: executes models
- Application API → Engineering studies: dispatches studies
- Application API → BLUECAD: dispatches CAD
- BLUECAD → Run evidence: produces evidence
- Application API → AI request routes: dispatches AI
- AI request routes → AI execution: executes request
- AI execution → Egress policy: checks egress
- AI execution → Provider registry: selects provider
- AI execution → Local model runtime: runs locally
- AI execution → External AI provider: approved external call
- AI request routes → Hermes agent: routes agent turns