Supervisor (Multi-Agent)
The supervisor subsystem orchestrates multiple agent runs within a single workflow. It supports several coordination patterns — delegate, broadcast, debate, pipeline, map-reduce, voting, and saga — that cover common multi-agent scenarios from simple fan-out to transactional compensation.
Source: internal/supervisor/*
Purpose
Supervisor workflows coordinate multiple agent runs using patterns like delegate, debate, map-reduce, and saga.
Supervisor Flow
Patterns
- Delegate
- Broadcast
- Debate
- Pipeline
- MapReduce
- Voting
- Saga (with compensation)
Trust-Based Delegation
When CRUVERO_TRUST_ENABLED=true, delegate routing can use trust scores to pick agents by inferred capability.
Trust scoring inputs:
- historical success rate
- quality score
- recency factor
Policy controls:
CRUVERO_TRUST_WEIGHT_SUCCESSCRUVERO_TRUST_WEIGHT_QUALITYCRUVERO_TRUST_WEIGHT_RECENCYCRUVERO_TRUST_RECENCY_DECAYCRUVERO_TRUST_REVIEW_THRESHOLD
Low-trust behavior:
- If selected trust falls below threshold, workflow can route through reviewer/human approval paths before committing outcomes.
Capability Manifests
Capabilities describe what an agent can reliably perform.
Operational flow:
- Register/list capabilities via
cmd/agent-capability. - Capability records feed trust lookup for delegation decisions.
- Test-coverage metadata can be tracked as part of capability registration.
Delegation Chain
Delegation chain records provide accountability across multi-agent hops.
Captured fields include:
- delegation id
- parent/child relationship
- selected delegate and capability
- start/completion timestamps
- outcome
Use cases:
- post-mortem analysis
- audit trails
- trust score attribution
Blackboard
Shared state store via internal/blackboard/* (Postgres-backed kv_store).
CLI
cmd/supervisor-runcmd/supervisor-querycmd/supervisor-signalcmd/agent-capability
Examples
docs/examples/supervisor_agents.jsondocs/examples/supervisor_items.jsondocs/examples/supervisor_saga.json