How harery/octalume works
OCTALUME is a gate-driven enterprise SDLC framework: a project can begin with the Phase 0 idea pipeline, then progress through eight lifecycle phases, producing traceable artifacts and advancing only when quality gates pass. Users operate it through the CLI, MCP tools, or a web dashboard. The phase engine coordinates state, gates, and agent orchestration; compliance scanning and persistent memory support governance. The graph reflects README-documented capabilities where implementation was not sampled; those links are omitted when wiring is uncertain.
Main entry points: main.py FastAPI Backend · engine.py Phase Engine · cli.py CLI · server.py MCP Server
Components 26
User Interfaces
- CLI
octalume/cli.py - MCP Server
octalume/mcp/server.py
Lifecycle Core
- Phase Engine
octalume/core/engine.py - Quality Gates
octalume/core/gates.py - Project State
octalume/core/state.py - Memory Bank
octalume/core/memory.py
Agent System
- Agent Orchestrator
octalume/core/orchestrator.py - Phase Agents
octalume/agents - Agent Messaging
octalume/a2a/protocol.py - Message Bus
octalume/a2a/messaging.py
Governance
- Compliance Scanner
octalume/compliance/scanner.py - Compliance Catalogs
octalume/compliance
Idea Pipeline
- Idea Parser
octalume/idea/parser.py - 12-Stage Pipeline
octalume/idea/pipeline.py - Plan Artifacts
octalume/idea
Web Dashboard
- Web Frontend
web/frontend/src/App.tsx - API Client
web/frontend/src/lib/api.ts - FastAPI Backend
web/backend/main.py - Phase Routes
web/backend/routers/phases.py - Agent Routes
web/backend/routers/agents.py - Artifact Routes
web/backend/routers/artifacts.py - Compliance Routes
web/backend/routers/compliance.py - Dashboard Routes
web/backend/routers/dashboard.py
Other components
- Project User
- MCP Client
- Browser User
Connections 25
- Project User → CLI: runs commands
- MCP Client → MCP Server: invokes tools
- Browser User → Web Frontend: uses dashboard
- Web Frontend → API Client: requests data
- API Client → FastAPI Backend: calls API
- FastAPI Backend → Phase Routes: routes requests
- FastAPI Backend → Agent Routes: routes requests
- FastAPI Backend → Artifact Routes: routes requests
- FastAPI Backend → Compliance Routes: routes requests
- FastAPI Backend → Dashboard Routes: routes requests
- CLI → Phase Engine: manages phases
- MCP Server → Phase Engine: manages phases
- MCP Server → Compliance Scanner: runs scans
- MCP Server → Memory Bank: stores memory
- Phase Engine → Quality Gates: validates transitions
- Phase Engine → Project State: loads and saves
- Phase Engine → Agent Orchestrator: coordinates agents
- Agent Orchestrator → Project State: saves agent state
- Agent Orchestrator → Agent Messaging: sends messages
- Agent Messaging → Message Bus: dispatches messages
- Agent Orchestrator → Phase Agents: assigns phase work
- Compliance Scanner → Compliance Catalogs: checks controls
- CLI → Idea Parser: parses idea
- CLI → 12-Stage Pipeline: requests stages
- 12-Stage Pipeline → Plan Artifacts: defines outputs