Integrity
Three anti-gaming detectors run against your scored sub-sessions, guarding the score against inflation or gaming. Each raises a flag on the sub-session when something looks off.
These guards run in the background. The one you see directly is Fragmentation merge, counted on the score hub’s Merges card. Whenever a guard is the reason a sub-session left your score, the exclusion reason on its Sessions row says so.
The three detectors
Section titled “The three detectors”| Flag | What triggers it |
|---|---|
| Substance floor breach | A sub-session was scored despite too few turns, no edits, or no mutating tool calls. |
| Median substance outlier | A sub-session sat far below the team’s typical substance level for that intent. |
| Fragmentation merge | Several short sub-sessions inside a short window were merged into one — looks like a single task was split across many starts. |
Good to know
Section titled “Good to know”- Flags don’t cut your score directly — they just mark sub-sessions that may be worth a look.
- If Fragmentation merge shows up often on the hub’s Merges card, try keeping a task in one sub-session instead of restarting Claude Code mid-task.