Integrity

Three anti-gaming detectors run against your scored sessions. Each raises a flag when something looks off. The headline is the count of flags raised — lower is better, zero is clean.

Headline

integrity_total = substance_floor_breach + median_substance_outlier + fragmentation_merge

The three detectors

Flag	What triggers it
Substance floor breach	A session was scored despite too few turns, no edits, or no mutating tool calls.
Median substance outlier	A session sat far below the team’s typical substance level for that intent.
Fragmentation merge	Several short sessions inside a short window were merged into one — looks like a single task was split across many starts.

Bands

0 clean · 1–2 fair · 3–5 weak · 6+ poor.

How to read flags

• 0 flags: Nothing looked off.
• 1–2 flags: Worth a glance, not a problem.
• 3–5 flags: A pattern is forming — pick one to investigate.
• 6 or more: Several detectors firing — review what’s changed.

What to do when flags appear

1. Open the flag detail to see which session triggered it and why.
2. If the session was real but small, that’s fine — flags don’t punish your score directly, they just mark sessions the substance check skipped.
3. If you see fragmentation merges often, try keeping a task in one session instead of restarting Claude Code mid-task.