Team Coherence
Keep your AI teams aligned and prevent drift.
MeetLoyd's Team Coherence system monitors your AI agent teams to ensure they stay aligned with their intended objectives. Detect and prevent common failure modes like agents undoing each other's work or getting stuck in correction loops.
Agent failure isn't about intelligence -- it's about drift from original intent. Coherence monitoring catches these issues early.
Coherence scores are calculated automatically every 5 minutes for all running teams. No manual setup required -- scores update in real-time as your teams operate.
Understanding Coherence Score
Each team has a coherence score from 0-100:
| Score | Status | Meaning |
|---|---|---|
| 80-100 | Healthy | Team is well-aligned and productive |
| 60-79 | Warning | Some drift detected, monitor closely |
| Below 60 | Critical | Significant drift, intervention recommended |
Drift Patterns Detected
Oscillation
Agents repeatedly undoing each other's work. Agent A makes a change, Agent B reverts it, Agent A re-does it. Symptom: High oscillation score, low productivity.
Feedback Loops
Circular correction chains where Agent A corrects Agent B, Agent B corrects Agent C, and Agent C corrects Agent A. Symptom: High correction rate, no forward progress.
Correction Spikes
Sudden increase in agents correcting each other's work. Symptom: Elevated corrections per hour.
Intent State
Define what your team should accomplish:
- Primary Objective -- The main goal (e.g., "Process customer support tickets and resolve issues within SLA")
- Secondary Objectives -- Supporting goals (e.g., "Maintain customer satisfaction above 4.5/5")
- Constraints -- Boundaries the team must respect
| Constraint Type | Description | Example |
|---|---|---|
| Hard | Never violate | "Never share customer data externally" |
| Soft | Minimize violations | "Prefer email over phone contact" |
Coherence Budget
Set limits to prevent runaway behavior:
| Limit | Default | Description |
|---|---|---|
| Max Concurrent Agents | 5 | Agents active simultaneously |
| Max Actions/Minute | 30 | Rate limit on operations |
| Max Corrections/Hour | 10 | Correction threshold |
| Max Feedback Loop Depth | 3 | Circular correction limit |
Enforcement Modes
| Mode | Behavior |
|---|---|
| Warn | Alert but continue operations |
| Pause | Auto-pause team for cooldown period |
| Block | Require human intervention to resume |
Drift Events
When issues are detected, drift events are created:
| Event Type | Severity | Description |
|---|---|---|
| Oscillation Detected | Warning/Critical | Agents undoing each other |
| Feedback Loop Detected | Warning/Critical | Circular corrections |
| Correction Spike | Warning/Critical | High correction rate |
| Budget Exceeded | Critical | Rate limits hit |
Resolving Events
- Acknowledge -- You've seen it, investigating
- Resolve -- Issue fixed, document what was done
- Dismiss -- False positive, adjust thresholds
Dashboard Views
Tenant Summary
Overview of all monitored teams: teams at risk count, average coherence score, and recent unresolved events.
Team Detail
Deep dive into a specific team: real-time coherence gauge, trend graph (improving/stable/degrading), budget usage meters, and recent events list.
Initial Setup: Start with default budgets and thresholds. Coherence scores calculate automatically. Let the team run for a day to establish a baseline, then tune thresholds based on observed behavior.
Ongoing Monitoring: Check coherence scores daily. Investigate warnings promptly -- don't let drift accumulate. Review feedback loops, as they often indicate unclear responsibilities.
When Drift is Detected: Pause the team if critical. Review recent actions to understand the pattern. Clarify objectives or constraints if needed. Resume with monitoring.