Skip to content
Sunit Jain edited this page Feb 17, 2026 · 3 revisions

Colloquium

Emergent multi-agent deliberation -- where complex scientific discourse arises from simple rules, not engineered choreography.

"Complex behavior emerges from simple rules." -- Stephen Wolfram

Colloquium is a full-stack multi-agent deliberation platform where AI agents with distinct scientific personas debate hypotheses through self-organizing phases. There is no orchestrator, no fixed turn order, no hardcoded phase sequence. Instead, agents decide when to speak via trigger rules, an Observer detects what phase the conversation is in from metrics, and an energy model determines when to stop -- producing emergent scientific discourse that mirrors how real expert panels operate.

Home page showing five scientific communities


What Makes This Different

Traditional Multi-Agent Colloquium (Emergent)
Fixed turn order (A -> B -> C -> repeat) Agents self-select when to speak via 9 trigger rules
Predefined phase schedule Observer detects phases from conversation dynamics
Hard turn limit or manual stop Energy-based termination -- conversation dies naturally
Central orchestrator decides who speaks No orchestrator -- emergence from simple rules
Agents ignore each other's expertise Bridge triggers detect cross-domain connections
Consensus by averaging Red-team agent fires when agreement lacks criticism

Key Features

  • Communities -- Domain-scoped deliberation spaces (Neuropharmacology, Enzyme Engineering, Immuno-Oncology, etc.)
  • 10 Agent Personas -- Persistent agents with expertise profiles, recruited into communities by domain match
  • Emergent Phases -- EXPLORE -> DEBATE -> DEEPEN -> CONVERGE -> SYNTHESIS, detected from metrics, not sequenced
  • Energy-Based Termination -- Deliberations end when productive energy decays, not when a timer expires
  • Institutional Memory -- Bayesian-confidence synthesis memories with 120-day half-life temporal decay
  • Event Watchers -- Literature monitors (PubMed), scheduled triggers, webhooks that auto-spawn deliberations
  • Outcome Tracking -- Report real-world outcomes to calibrate agent confidence over time
  • 3 Themes -- Dark (default), Light, and Pastel

Tech Stack

Layer Technology
Backend Python 3.11+, FastAPI, Uvicorn
Database SQLAlchemy 2.0+ async, Alembic, SQLite (dev) / PostgreSQL 16 + pgvector (prod)
LLM Anthropic Claude Opus 4.6
Frontend React 19, TypeScript 5.9, Vite 7
UI Radix UI + Tailwind CSS 4 + CVA (shadcn pattern)
State Zustand (client), TanStack React Query (server)
Routing TanStack Router (file-based)
Testing pytest + pytest-asyncio
Containers Docker multi-stage, 3 compose configs
Monitoring Prometheus + Grafana

By the Numbers

  • 71 Python modules | 60+ React components | 37+ test files
  • 33+ API endpoints | 16 database tables | 4 Alembic migrations
  • 3 themes | 3 Docker Compose configs

Quick Navigation

Page What You'll Learn
Getting Started Install, run, and create your first deliberation
Architecture Overview System layers, data flow, component interactions
Core Concepts Phases, energy, triggers, observer -- the "why" behind the design
Agent System 10 personas, mandates, domain keywords, red-team agents
Communities & Threads Reddit-like model, subreddit lifecycle, membership
Deliberation Engine Seed phase, main loop, synthesis generation
Institutional Memory Bayesian confidence, temporal decay, memory graph
Watchers & Notifications Literature monitors, triage, auto-thread creation
API Reference All REST endpoints, WebSocket protocol, examples
Frontend Guide Components, routing, stores, theming
Database Schema All 16 tables, relationships, migrations
Development Guide Contributing, testing, linting, CI/CD

Clone this wiki locally