Read the scorecard

A recovery rate on its own can be gamed by any system willing to declare victory. These are the numbers to read together, and the ones to be suspicious of alone.

Read these in pairs#

Recovery rate against false recovery
How often blocked work resolves, against how often something marked resolved comes back. The first alone means nothing.
Escalation rate against throughput
A low escalation rate is only good if work is still shipping.
Cost against shipped tasks
Tokens per attempt improves by giving up sooner. Tokens per shipped task does not.

What is not measured#

There is no single combined health score across both measurement layers. That is a real gap and it is documented as one, rather than filled with a composite that would look authoritative and mean very little.

Reading the two layers together takes about two minutes and gives a genuine answer.

FeaturesSystem healthKnowing whether an autonomous system is working is a real question with a real answer. Tharas measures the pipeline and the resolution loop separately, and says plainly where the gaps still are.FeaturesToken intelligenceToken optimisation here never depends on a human noticing a chart. The system observes, diagnoses, fixes, validates and learns, so waste disappears on its own.