How bhuvaneshkumar1/jarvis works
JARVIS is a Windows-focused autonomous AI operating system. Its principal workflow starts with a user request entering the application kernel, which initializes and coordinates runtime components; security authentication and policy governance control operations, while the kernel can use LLM providers and task services. Tasks are persisted and supported by crash recovery, with an asynchronous event bus for dispatch. The README documents these major capabilities; source excerpts and the index confirm selected calls, but several subsystems were not sampled, so their links rely on README statements.
Main entry points: application.py Application Kernel · manager.py Task Manager · bus.py Priority Event Bus · auth_manager.py PIN Authentication
Components 22
Runtime Kernel
- Application Entry
main.py - Application Kernel
jarvis/core/runtime/application.py - Runtime Context
jarvis/core/runtime/context.py - Priority Event Bus
jarvis/core/events/bus.py - Workflow Orchestrator
jarvis/core/orchestration/orchestrator.py
Security Governance
- PIN Authentication
jarvis/security/auth_manager.py - Persistent Lockout
jarvis/security/lockout_manager.py - Policy Engine
jarvis/security/policy/engine.py - Audit Logging
jarvis/core/audit_log.py - Secret Redaction
jarvis/core/logging.py
LLM Intelligence
- LLM Router
jarvis/core/llm_router.py - Provider Factory
jarvis/llm/factory.py - LLM Contracts
jarvis/llm/contracts.py - NVIDIA Provider
jarvis/llm/providers/nvidia.py - OpenRouter Provider
jarvis/llm/providers/openrouter.py
Tasks Persistence
- Task Manager
jarvis/core/tasks/manager.py - Task Repository
jarvis/core/tasks/repository.py - Crash Recovery
jarvis/core/recovery/coordinator.py - Task Outbox
jarvis/core/tasks/outbox.py - SQLite Store
jarvis/database/manager.py
Other components
- User
- LLM Service
Connections 26
- User → Application Entry: submits request
- Application Entry → Application Kernel: starts runtime
jarvis/core/runtime/application.py - Application Kernel → Runtime Context: shares context
jarvis/core/runtime/application.py - Application Kernel → Priority Event Bus: initializes
jarvis/core/runtime/application.py - Application Kernel → Task Manager: initializes
jarvis/core/runtime/application.py - Application Kernel → Workflow Orchestrator: initializes
jarvis/core/runtime/application.py - Application Kernel → Crash Recovery: initializes
jarvis/core/runtime/application.py - PIN Authentication → Persistent Lockout: uses lockout
jarvis/security/auth_manager.py - PIN Authentication → Policy Engine: authorizes through
- Policy Engine → Priority Event Bus: publishes decisions
- Priority Event Bus → Task Manager: dispatches events
- PIN Authentication → Audit Logging: records security events
jarvis/security/auth_manager.py - LLM Router → Provider Factory: selects provider
- Provider Factory → NVIDIA Provider: creates provider
- Provider Factory → OpenRouter Provider: creates provider
- NVIDIA Provider → LLM Contracts: uses contracts
jarvis/llm/providers/nvidia.py - OpenRouter Provider → LLM Contracts: uses contracts
jarvis/llm/providers/openrouter.py - NVIDIA Provider → LLM Service: calls inference
- OpenRouter Provider → LLM Service: calls inference
- Workflow Orchestrator → Task Manager: coordinates tasks
jarvis/core/orchestration/orchestrator.py - Task Manager → Task Repository: persists tasks
jarvis/core/tasks/manager.py - Task Manager → Task Outbox: uses outbox
jarvis/core/tasks/manager.py - Task Manager → Crash Recovery: runs recovery
jarvis/core/tasks/manager.py - Task Repository → SQLite Store: stores task state
- Crash Recovery → SQLite Store: restores task state
- Priority Event Bus → Secret Redaction: redacts event history
jarvis/core/events/bus.py