AevoraeXAevoraeXSign inStart free trial
Understanding scores

Reading the score anatomy

Components, drivers, ordered adjustments, confidence, percentile, tier, caveats and rationale.

Updated Sep 26, 20261 min read

Every score opens into the anatomy returned by the engine.

On public pages the header shows rank, percentile and tier within the city pool, for example "#1 of 2,567 in Orlando, top tier", plus a confidence bar.

Components and drivers

Each component shows its weight and sub-score. Expand it to see plain-English drivers and the engine field behind each value. A zero sub-score reads Not triggered.

Adjustments

Multipliers, caps, bonuses and penalties appear in engine order. Unapplied adjustments remain visible. Confidence shrink is the final step toward 50.

Caveats and rationale

Caveat chips state missing or proxy data. “Why this score, in plain English” is the engine rationale, not generated marketing copy.

The test invariant is recompose(breakdown) == score within 0.01.

Was this helpful?

Read next.

Understanding scoresThe five lensesThe engine's five lenses, who uses them, and the component families each one blends.Understanding scoresConfidence and city percentilesHow confidence shrink and city-percentile tiers help you read where a property ranks.Understanding scoresModel versions and what changes between themEvery score names the model version that produced it. What a version is, where the release notes live, and what happens to old scores when a model changes.

Keep reading.