Compatibility Scoring

Mortar produces a score from 0 to 100.

Classification

• 90–100: SAFE
• 70–89: CONDITIONAL
• <70: BREAKING

What affects the score

Mortar scoring starts deterministic:

• removed operations
• removed required fields
• type changes
• narrowed enums

Over time, scoring incorporates runtime evidence:

• error distribution shifts
• latency shifts
• behavioral drift

The promise

A score is only useful if it is enforced.