UCF metrics explained: the 6 dimensions of coordination
Beyond token counts
Every AI platform shows you token usage. "You consumed 50,000 tokens." But what did those tokens produce? Was the output good? Did the agents work together or trip over each other?
Token counts measure cost. UCF measures quality.
The Universal Coordination Field (UCF) is Helix's framework for measuring how well your automation system is performing — not just "did it complete?" but "how well did it coordinate?" Think of it as the difference between "the car drove from A to B" and "the car drove smoothly, efficiently, safely, and on time."
The six dimensions
Harmony (0-100%)
How well agents collaborate without stepping on each other's work. High harmony means clean handoffs, shared context, and consistent outputs. Low harmony means duplicated effort or conflicting decisions.
When to worry: Harmony below 50% suggests agents are working at cross-purposes. Check role assignments and shared memory.
Friction (0-100%, lower is better)
Where resistance exists in the system — API failures, malformed inputs, slow external services, ambiguous instructions. Friction doesn't mean failure; it means the system is working harder than it should to produce the same result.
When to worry: Rising friction with stable harmony suggests external input issues. Check integrations and data formats.
Throughput (tasks/time)
Raw processing capacity. A spike in throughput with rising friction suggests the system is burning resources to maintain speed — a warning sign before something breaks.
Focus (0-100%)
Precision and attention quality. Are agents working on the right tasks? High focus means compute is spent on meaningful work, not busywork or re-doing failed steps.
Resilience (0-100%)
Recovery capability. When an API goes down, a model returns garbage, or a webhook is malformed — how quickly and cleanly does the system recover? High resilience means failures are brief and self-correcting.
Velocity (execution speed)
Raw execution speed, separate from throughput. High velocity with low throughput suggests bottlenecks between steps rather than within them.
Reading the signals
The power of UCF is in the relationships between metrics:
| Signal | Meaning | Action |
|---|---|---|
| High harmony + low friction | System is healthy | Don't touch it |
| High harmony + high friction | Agents work well but struggle with inputs | Check integrations |
| Low harmony + low friction | Agents are fast but conflicting | Review role assignments |
| Low resilience + high velocity | Fast but fragile | Add fallback providers |
UCF vs traditional monitoring
Traditional monitoring tells you: "The API returned 200 OK."
UCF tells you: "The API returned 200, but Friction is rising because the response format changed. Harmony dropped because Echo and Vega are making conflicting interpretations. Resilience is high because Kavach caught the inconsistency before it propagated."
That's the difference between monitoring a system and understanding it.
Accessing UCF data
UCF metrics update in real-time on your dashboard and are available via API:
GET /api/health/detailed
GET /api/coordination/metrics
GET /api/coordination/trends?window=1h
See UCF metrics in action. Start free → Real-time coordination data from your first spiral.