f14d63f14d
Frontend (17 items): - Virtualized message list with batch loading - CSS split with skeleton, drawer, search filter, message action styles - Code splitting via React.lazy + Suspense for Admin/Ethics/Settings pages - Skeleton loading components (Skeleton, SkeletonCard, SkeletonGrid) - Debounced search/filter component (SearchFilter) - Error boundary with fallback UI - Keyboard shortcuts (Ctrl+K search, Ctrl+Enter send, Escape dismiss) - Page transition animations (fade-in) - PWA support (manifest.json + service worker) - WebSocket auto-reconnect with exponential backoff (10 retries) - Chat history persistence to localStorage (500 msg limit) - Message edit/delete on hover - Copy-to-clipboard on code blocks - Mobile drawer (bottom-sheet for consensus panel) - File upload support - User preferences sync to backend Testing (8 items): - Component tests: Toast, Markdown, ChatMessage, Avatar, ErrorBoundary, Skeleton - Hook tests: useChatHistory - E2E smoke tests (5 tests) - Accessibility audit utility Backend (12 items): - Vector memory with cosine similarity search - TTS/STT adapter factory wiring - Geometry kernel with orphan detection - Tenant registry with CRUD operations - Response cache with TTL - Connection pool (async) - Background task queue - Health check endpoints (/health, /ready) - Request tracing middleware (X-Request-ID) - API key rotation mechanism - Environment-based config (settings.py) - API route documentation improvements Infrastructure (4 items): - Grafana dashboard template - Database migration system - Storybook configuration Documentation (3 items): - ADR-001: Advisory Governance Model - ADR-002: Twelve-Head Architecture - ADR-003: Consequence Engine 552 Python tests + 45 frontend tests passing, 0 ruff errors. Co-Authored-By: Nakamoto, S <defi@defi-oracle.io>
40 lines
1.5 KiB
Markdown
40 lines
1.5 KiB
Markdown
# ADR-002: Twelve-Head (Dvādaśa) Architecture
|
|
|
|
## Status
|
|
Accepted
|
|
|
|
## Context
|
|
Multi-agent systems typically use 2-5 agents with fixed roles. FusionAGI needed a system that could analyze problems from many perspectives simultaneously while maintaining coherent output.
|
|
|
|
## Decision
|
|
The orchestrator decomposes every query across **12 specialized heads**:
|
|
|
|
| Head | Role |
|
|
|------|------|
|
|
| Logic | Logical reasoning and consistency |
|
|
| Research | Source evaluation and synthesis |
|
|
| Systems | Architecture and integration |
|
|
| Strategy | Long-term planning |
|
|
| Product | User experience and design |
|
|
| Security | Threat analysis |
|
|
| Safety | Risk observation (advisory) |
|
|
| Reliability | Fault tolerance |
|
|
| Cost | Resource optimization |
|
|
| Data | Statistical reasoning |
|
|
| DevEx | Developer experience |
|
|
| Witness | Audit and observation |
|
|
|
|
The Witness head is special: it observes but doesn't contribute to the consensus.
|
|
|
|
## Consequences
|
|
- Comprehensive analysis from 12 angles on every query
|
|
- Higher latency (12 parallel LLM calls) but better quality
|
|
- The InsightBus enables cross-head learning
|
|
- Each head has a unique color identity in the UI for visual distinction
|
|
- The consensus mechanism must handle disagreement gracefully
|
|
|
|
## Alternatives Considered
|
|
1. **3-5 heads** — Rejected: insufficient perspective diversity
|
|
2. **Dynamic head count** — Future consideration: some queries don't need all 12
|
|
3. **Hierarchical heads** — Rejected: flat structure promotes equal consideration
|