This is the preserved partial result for this run. Its original utterance evidence is shown below.
Rows
2
Pass
2 (100%)
Fail
0 (0%)
Unverified
0 (0%)
Pass rate
100%
Avg difficulty
—
"Unverified" = the grader couldn't confidently call it PASS or FAIL from the trace — needs a human look (that's you 👍/👎-ing it). "Pass rate" = pass ÷ (pass + fail) — it excludes Unverified rows, so it differs slightly from the Pass % above (which is share of ALL rows).
Why the fails happened — comprehension vs execution vs cosmetic
No fails in this run, or failure classification not present on these rows yet.
Handled correctly? — by expected action
Click a row to see the ones it got wrong; click a wrong utterance to jump to its full detail below.
Supposed to
N
Correct
Wrong
Unverified
▸ LOG — log the entry
2
2 (100%)
0 (0%)
0 (0%)
No errors — all handled correctly.
Total
2
2 (100%)
0
0
Accuracy by difficulty
Pending A1's per-utterance difficulty score (requested 2026-07-05) — this bar chart lights up once that lands.
Clarification follow-ups — scored separately
Second turn: app asked, we replied — did it resolve correctly?
No CLARIFY_ANSWER (follow-up) rows in this run.
Cosmetic only
Not yet classified — pending A1 adding cosmetic-issue detection (double response, wording variance, rounding) to the grader. Nothing fabricated here.
System / infra
Not yet classified — pending confirmation from A1 whether trace data already carries infra-error signal (TTS/sync/DB-write errors) or needs new detection.
Latency
Avg (time to ready)
0.2s
p90
0.2s
Max
0.2s
Went async
0 (0%)
Each dot is one utterance (green=pass, red=fail, amber=unverified), positioned by how long it took to be ready for review. Bigger dots are the slow outliers — click any dot to jump to its detail.
0s
1s
2s
5s
Response path — quick (single response) vs async (an ack like "Working on it…" before the real answer).
Quick response
2
Slowest 2 utterances (click to jump to detail):
"Breakfast was two hard boiled eggs."0.2s
"I had one medium banana."0.2s
Filter — controls the list below
Pass / Fail / Unverified
PASS 2FAIL 0UNVERIFIED 0
Module (intended for)
Food (2)
Utterance sub-type (within module)
2 shown — 2 pass, 0 fail, 0 unverified
Per-utterance detail
PASSshould log the entry"I had one medium banana." (difficulty —)0.2s
Verdict Expected LOG — should log the entry. PASS: Logged (write-truth verified): Banana — card not captured.
Why verdict Logged (write-truth verified): Banana — card not captured.
My override
Things I think are wrong
Use this when the report passed something that should have failed.
Comprehension
Execution
Cosmetic
Things the report marked wrong but I think are right
Use this when the report failed something that should have passed.
Actually right
Report/grader issue
Pick every reason you think applies. Multiple boxes are allowed because one utterance can be wrong in more than one way. Use the note below for "Other" or extra detail.
Timing 0.2s
1 · TTS saidno speech captured
2 · Card shown Logged one medium banana. Assumed 1 medium banana as the default serving. Tell me if you want a different amount.
3 · App data rows written created food_log_entry: Banana ×1 (1 medium banana) 105 cal · 1.3g P · 27.1g C · 0.4g F
4 · UI didno screen events captured
5 · Seed/context data
Seeded starting state: none listed in the corpus row.
No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.
snapshot captured 2026-08-01T13:26:21.277Z
6 · Why this foodNo food-decision explanation was captured for this path.
7 · Lookup method The answer used provisional food evidence from the common-food list.
8 · Candidates → deciderno candidate list captured (this path did not run DB resolution — e.g. provisional branded log)
PASSshould log the entry"Breakfast was two hard boiled eggs." (difficulty —)0.2s
Verdict Expected LOG — should log the entry. PASS: Logged (write-truth verified): Egg — card not captured.
Why verdict Logged (write-truth verified): Egg — card not captured.
My override
Things I think are wrong
Use this when the report passed something that should have failed.
Comprehension
Execution
Cosmetic
Things the report marked wrong but I think are right
Use this when the report failed something that should have passed.
Actually right
Report/grader issue
Pick every reason you think applies. Multiple boxes are allowed because one utterance can be wrong in more than one way. Use the note below for "Other" or extra detail.
Timing 0.2s
1 · TTS saidno speech captured
2 · Card shown Logged two hard boiled eggs.
3 · App data rows written created food_log_entry: Egg ×1 (2 eggs) 143 cal · 12.6g P · 0.7g C · 9.5g F
4 · UI didno screen events captured
5 · Seed/context data
Seeded starting state: none listed in the corpus row.
No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.
snapshot captured 2026-08-01T13:26:32.555Z
6 · Why this foodNo food-decision explanation was captured for this path.
7 · Lookup method The answer used provisional food evidence from the common-food list.
8 · Candidates → deciderno candidate list captured (this path did not run DB resolution — e.g. provisional branded log)