Architecture Overview
Understand how Crucible Community Edition is structured and how components interact.
Core Components
API Server (FastAPI)
RESTful API handling session management, Agent operations, and artifact generation. Built with FastAPI and Python.
Debate Engine
Orchestrates the debate process: research, claims, challenges, convergence. Manages Agent interactions and enforces debate rules.
Frontend (Next.js)
Web interface for creating sessions, monitoring debates, and viewing artifacts. Built with Next.js and React.
Database (PostgreSQL)
Stores sessions, Agents, users, and metadata. All debate content and artifacts are persisted here.
Data Flow
- User creates session via frontend
- API stores session in database
- User starts session
- Debate Engine orchestrates Agent interactions
- Agents call model APIs (OpenAI, Anthropic, etc.)
- Debate events streamed via WebSocket
- Artifacts generated and stored
- User views Decision Brief and Minutes
Security Model
- JWT-based authentication
- User session isolation
- No data transmission to external services (except model APIs)
- All prompts and data stay within your infrastructure
- Optional S3 for artifact storage (your bucket)