Central meta-project for the Bodai ecosystem, providing configuration, documentation, and operations for all components.
ORB: Orchestrated Reasoning Brain
Perceive. Reason. Orchestrate.
Etymology: From Sanskrit bodhi (awakening, enlightenment) - the state of supreme understanding.
Bodai (Sanskrit: bodhi, "awakening") is the meta-project that ties together:
- mahavishnu — Multi-repo workflow orchestration and worker pools
- akosha — Cross-system intelligence, embeddings, semantic search
- dhara — Persistent object storage with ACID transactions
- session-buddy — Session lifecycle and knowledge graphs
- crackerjack — Quality gates and CI/CD validation
- oneiric — Component resolution and runtime foundation
When run together, these components form the Bodai Orb (Orchestrated Reasoning Brain) — an integrated development environment for AI-native engineering. Each component is also fully usable on its own.
ORB: Orchestrated Reasoning Brain
Perceive. Reason. Orchestrate.
- Ecosystem Components
- Mahavishnu - The Orchestrator
- Akosha - The Seer
- Dhara - The Curator
- Session-Buddy - The Builder
- Crackerjack - The Inspector
Crackerjack is the Bodai ecosystem's standard quality-control and CI/CD runner. Repo-level quality gates should align with Crackerjack workflows unless a repo documents an exception.
The Bodai ecosystem consists of six interconnected components, each with a distinct role. Five are network services with MCP servers, while Oneiric serves as a shared library.
| Component | Role | Port | GitHub | Description |
|---|---|---|---|---|
| Mahavishnu | Orchestrator | 8680 | lesleslie/mahavishnu | Multi-engine workflow orchestration |
| Akosha | Seer | 8682 | lesleslie/akosha | Cross-system intelligence & vector embeddings |
| Dhara | Curator | 8683 | lesleslie/dhara | Persistent object storage with ACID |
| Session-Buddy | Builder | 8678 | lesleslie/session-buddy | Session lifecycle & knowledge graphs |
| Crackerjack | Inspector | 8676 | lesleslie/crackerjack | Quality gates & CI/CD validation |
| Oneiric | Foundation | N/A | lesleslie/oneiric | Component resolution, lifecycle management, adapter system, action kits, domain bridges, runtime orchestration, remote delivery |
From Sanskrit maha (great) + Vishnu (the preserver in Hindu trinity)
The central workflow engine that routes tasks to appropriate execution engines, coordinates multi-step processes across components, and manages workflow definitions and templates.
- Routes tasks to Akosha for intelligence operations
- Persists state to Dhara for recovery
- Tracks context in Session-Buddy
- Validates with Crackerjack before execution
From Sanskrit akasha (sky, ether, space) - the fifth element, medium of consciousness
Provides cross-system intelligence through vector embeddings, semantic search, pattern detection, and knowledge graphs. Enables predictive analysis and recommendations across all sessions.
- Receives session data from Session-Buddy for embedding
- Stores patterns in Dhara
- Provides intelligence to Mahavishnu
- Receives code analysis from Crackerjack
From Sanskrit dhara (firm, constant, unchanging) - also the Pole Star
The single source of truth for persistent data. Provides ACID transaction guarantees, data versioning, backup/recovery, and efficient querying.
- Stores state for Mahavishnu
- Persists patterns for Akosha
- Backs up sessions for Session-Buddy
- Stores quality reports for Crackerjack
The session lifecycle manager that tracks conversation history, builds knowledge graphs, and enables context switching between sessions.
- Sends data to Akosha for embedding
- Stores backups in Dhara
- Provides context to Mahavishnu
- Receives quality metrics from Crackerjack
The quality enforcer that runs automated test suites, manages CI/CD pipelines, provides code analysis and linting, and tracks quality metrics over time.
- Validates workflows for Mahavishnu
- Sends code analysis to Akosha
- Stores reports in Dhara
- Records metrics in Session-Buddy
From Greek oneiros (dream) - relating to dreams, the abstract and complex
The platform foundation library that provides explainable component resolution, lifecycle management, an adapter system spanning 18+ domains, action kits for automation, domain bridges (services/tasks/events/workflows), runtime orchestration, and remote delivery via signed manifests. Every other Bodai component builds on top of Oneiric's patterns.
- Used by Mahavishnu for layered configuration and lifecycle management
- Used by mcp-common as the Oneiric-native foundation for all MCP servers
- Used by Dhara for configuration, logging, and secrets management
- Used by Session-Buddy for storage adapters, configuration, and lifecycle
- Used by Crackerjack for runtime orchestration and health snapshots
- Used by Akosha for universal storage abstraction and adapter resolution
uv syncBodai provides a unified CLI for managing the ecosystem:
| Command | Description |
|---|---|
bodai health |
Check health status of all ecosystem components |
bodai start |
Start all ecosystem services |
bodai stop |
Stop all ecosystem services |
bodai restart |
Restart all ecosystem services |
bodai dashboard |
Launch the interactive monitoring dashboard |
bodai shell |
Open an interactive management shell |
bodai config show |
Display current configuration |
bodai config validate |
Validate configuration files |
For detailed architecture documentation, see docs/architecture.md.
pytestcrackerjack run- Architecture - System overview and data flow
- Component Roles - Detailed descriptions of each component
- Symbiosis - How components work together
- Port Map - Port allocation and rationale
The five Bodai MCP-server plugins are distributed via the bodai-plugins marketplace:
claude plugin marketplace add https://github.com/lesleslie/bodai-plugins
claude plugin install mahavishnu
claude plugin install session-buddy
claude plugin install crackerjack
claude plugin install akosha
claude plugin install dharaEach plugin ships its own slash commands under the <server>:<command> namespace (e.g. /mahavishnu:status, /session-buddy:checkpoint).