Core Concepts

Routing

At the center of Crucible is the router — Crucinger itself. Every incoming request flows through it. The router doesn't just forward messages; it understands what the work requires and dispatches it accordingly.

Intent Classification

Before routing can happen, the system needs to understand the request. Intent classification analyzes each incoming message by domain, complexity, and urgency. This goes beyond keyword matching — it's a semantic understanding of what the work actually requires.

Context Packaging

Handoffs fail when context is missing. Crucinger automatically bundles relevant memory, constraints, and success criteria with every task. Agents start with what they need, not from zero.

Outcome Tracking

Every routed task produces a result. Crucinger tracks outcomes and learns from corrections, improving routing quality over time through a Thompson Sampling model.

Agent Identity

Each agent has a persistent identity defined by SOUL.md (personality and principles), IDENTITY.md (role and responsibilities), and a dedicated workspace. This isn't stateless — agents accumulate knowledge and context over time.