Trivia

Some sub-sessions are too short or too quiet to say anything about your work — a stray prompt, a quick look at a file, an aborted start. Scoring those would only add noise. The substance floor catches them and routes them here, to the Trivia bucket.

The screens do not use that name. What this page describes shows up in two places: the score hub’s Trivial sub-sessions card, and the Excluded filter on the Sessions table, where the status reads Trivial.

The rule

A sub-session clears it as soon as any one of these holds:

• 3 or more conversational turns
• 10 or more net lines of code changed
• at least one mutating tool call

Only a sub-session that misses all three lands in Trivia. Missing just one — a long conversation that changed no code, or a one-line fix made in a single turn — is not enough to be excluded.

Each excluded sub-session is stored with a reason. In practice it is one of two: no real work (no turns, no code change, no tool calls at all) or too few turns (some activity, but under every threshold).

Why it matters

Excluded sub-sessions do not pull your grade up or down — they are pulled out of both numerator and denominator. A lot of trivial sub-sessions isn’t bad in itself; it usually just means much of your work is light exploration. Trivia is kept visible so you can spot the rare case where real work was caught by mistake.