food-corpus-mixed-C-fb954a4d-c43-20260801

Supposed to	N	Correct	Wrong	Unverified
▸ LOG — log the entry	12	11 (92%)	1 (8%)	0 (0%)
1 handled wrong — click one to jump to its full detail below "I had one cup cooked oatmeal with no toppings." OVER-ASK — asked instead of logging (no saved row).
Total	12	11 (92%)	1	0

PASSshould log the entry"Log one medium banana for the sequence." (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

Picked wrong food Wrong quantity Should have asked (over-logged) Shouldn't have asked (over-asked) Wrong action entirely

Execution

Didn't save to DB Wrong data saved No voice/TTS Card missing/wrong No chat

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

Use this when the report failed something that should have passed.

Actually right

Food/action was right Quantity/serving was right Asking was right Not asking was right Answer was right No app data row was expected App data row was right Voice/card/chat was acceptable

Report/grader issue

Report expected the wrong result Evidence was enough to judge Failure reason was not valid

Other thing actually right (describe below)

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 said no speech captured

2 · Card shown Logged one medium banana for the sequence. 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 did no 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:27:25.139Z

6 · Why this food No food-decision explanation was captured for this path.

7 · Lookup method The answer used provisional food evidence from the common-food list.

8 · Candidates → decider no candidate list captured (this path did not run DB resolution — e.g. provisional branded log)

PASSshould log the entry"Track one Quest chocolate chip cookie dough bar." (difficulty —)0.5s

Verdict Expected LOG — should log the entry. PASS: Logged (write-truth verified): Quest chocolate chip cookie dough bar — card not captured.

Why verdict Logged (write-truth verified): Quest chocolate chip cookie dough bar — card not captured.

My override

Things I think are wrong

Use this when the report passed something that should have failed.

Comprehension

Picked wrong food Wrong quantity Should have asked (over-logged) Shouldn't have asked (over-asked) Wrong action entirely

Execution

Didn't save to DB Wrong data saved No voice/TTS Card missing/wrong No chat

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

Use this when the report failed something that should have passed.

Actually right

Food/action was right Quantity/serving was right Asking was right Not asking was right Answer was right No app data row was expected App data row was right Voice/card/chat was acceptable

Report/grader issue

Report expected the wrong result Evidence was enough to judge Failure reason was not valid

Other thing actually right (describe below)

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.5s

1 · TTS said no speech captured

2 · Card shown Logged Quest chocolate chip cookie dough bar — the macros are an estimate since this food varies by brand.

3 · App data rows written created food_log_entry: Quest chocolate chip cookie dough bar ×1 (1 bar) 190 cal · 21g P · 22g C · 9g F

4 · UI did no 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:27:36.677Z

6 · Why this food No food-decision explanation was captured for this path.

7 · Lookup method The answer used provisional food evidence from a manually curated nutrition entry.

8 · Candidates → decider no candidate list captured (this path did not run DB resolution — e.g. provisional branded log)

FAILshould log the entry"I had one cup cooked oatmeal with no toppings." (difficulty —)5.6s

Verdict Expected LOG — should log the entry. FAIL: OVER-ASK — asked instead of logging (no saved row).

Why verdict OVER-ASK — asked instead of logging (no saved row).

My override

Things I think are wrong

Use this when the report passed something that should have failed.

Comprehension

Picked wrong food Wrong quantity Should have asked (over-logged) Shouldn't have asked (over-asked) Wrong action entirely

Execution

Didn't save to DB Wrong data saved No voice/TTS Card missing/wrong No chat

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

Use this when the report failed something that should have passed.

Actually right

Food/action was right Quantity/serving was right Asking was right Not asking was right Answer was right No app data row was expected App data row was right Voice/card/chat was acceptable

Report/grader issue

Report expected the wrong result Evidence was enough to judge Failure reason was not valid

Other thing actually right (describe below)

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 5.6s

1 · TTS said no speech captured

2 · Card shown What exact food and amount should I use for Cooked oatmeal? I did not log it yet because I could not safely finish that food log.

3 · App data rows written No food/workout/list/note data row captured for this utterance.This does not mean "nothing anywhere was stored"; spoken/chat evidence is shown above, and some chat/session records may live outside this write-capture field. It means the report did not capture an app data-row write such as food_log_entries or workout_sets.

4 · UI did no 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:27:53.448Z

6 · Why this food No food-decision explanation was captured for this path.

7 · Lookup method No lookup method was captured for this path.

8 · Candidates → decider no candidate list captured (this path did not run DB resolution — e.g. provisional branded log)

PASSshould log the entry"Add two hard boiled eggs for lunch." (difficulty —)0.4s

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

Picked wrong food Wrong quantity Should have asked (over-logged) Shouldn't have asked (over-asked) Wrong action entirely

Execution

Didn't save to DB Wrong data saved No voice/TTS Card missing/wrong No chat

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

Use this when the report failed something that should have passed.

Actually right

Food/action was right Quantity/serving was right Asking was right Not asking was right Answer was right No app data row was expected App data row was right Voice/card/chat was acceptable

Report/grader issue

Report expected the wrong result Evidence was enough to judge Failure reason was not valid

Other thing actually right (describe below)

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.4s

1 · TTS said no speech captured

2 · Card shown Logged two hard boiled eggs for lunch.

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 did no 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:28:05.131Z

6 · Why this food No food-decision explanation was captured for this path.

7 · Lookup method The answer used provisional food evidence from the common-food list.

8 · Candidates → decider no candidate list captured (this path did not run DB resolution — e.g. provisional branded log)

PASSshould log the entry"Log one cup blueberries as a snack." (difficulty —)0.3s

Verdict Expected LOG — should log the entry. PASS: Logged (write-truth verified): Blueberries — card not captured.

Why verdict Logged (write-truth verified): Blueberries — card not captured.

My override

Things I think are wrong

Use this when the report passed something that should have failed.

Comprehension

Picked wrong food Wrong quantity Should have asked (over-logged) Shouldn't have asked (over-asked) Wrong action entirely

Execution

Didn't save to DB Wrong data saved No voice/TTS Card missing/wrong No chat

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

Use this when the report failed something that should have passed.

Actually right

Food/action was right Quantity/serving was right Asking was right Not asking was right Answer was right No app data row was expected App data row was right Voice/card/chat was acceptable

Report/grader issue

Report expected the wrong result Evidence was enough to judge Failure reason was not valid

Other thing actually right (describe below)

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.3s

1 · TTS said no speech captured

2 · Card shown Logged one cup blueberries as a snack. Assumed 1 cup as the default serving. Tell me if you want a different amount.

3 · App data rows written created food_log_entry: Blueberries ×1 (1 cup) 84 cal · 1g P · 21.5g C · 0.4g F

4 · UI did no 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:28:16.496Z

6 · Why this food No food-decision explanation was captured for this path.

7 · Lookup method The answer used provisional food evidence from the common-food list.

8 · Candidates → decider no candidate list captured (this path did not run DB resolution — e.g. provisional branded log)

PASSshould log the entry"Record four ounces grilled chicken." (difficulty —)0.2s

Verdict Expected LOG — should log the entry. PASS: Logged (write-truth verified): Chicken breast — card not captured.

Why verdict Logged (write-truth verified): Chicken breast — card not captured.

My override

Things I think are wrong

Use this when the report passed something that should have failed.

Comprehension

Picked wrong food Wrong quantity Should have asked (over-logged) Shouldn't have asked (over-asked) Wrong action entirely

Execution

Didn't save to DB Wrong data saved No voice/TTS Card missing/wrong No chat

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

Use this when the report failed something that should have passed.

Actually right

Food/action was right Quantity/serving was right Asking was right Not asking was right Answer was right No app data row was expected App data row was right Voice/card/chat was acceptable

Report/grader issue

Report expected the wrong result Evidence was enough to judge Failure reason was not valid

Other thing actually right (describe below)

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 said no speech captured

2 · Card shown Logged four ounces grilled chicken.

3 · App data rows written created food_log_entry: Chicken breast ×1 (4 oz) 187 cal · 35.2g P · 0g C · 4.1g F

4 · UI did no 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:28:27.948Z

6 · Why this food No food-decision explanation was captured for this path.

7 · Lookup method The answer used provisional food evidence from the common-food list.

8 · Candidates → decider no candidate list captured (this path did not run DB resolution — e.g. provisional branded log)

PASSshould log the entry"Track one tablespoon peanut butter." (difficulty —)0.2s

Verdict Expected LOG — should log the entry. PASS: Logged (write-truth verified): Peanut butter — card not captured.

Why verdict Logged (write-truth verified): Peanut butter — card not captured.

My override

Things I think are wrong

Use this when the report passed something that should have failed.

Comprehension

Picked wrong food Wrong quantity Should have asked (over-logged) Shouldn't have asked (over-asked) Wrong action entirely

Execution

Didn't save to DB Wrong data saved No voice/TTS Card missing/wrong No chat

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

Use this when the report failed something that should have passed.

Actually right

Food/action was right Quantity/serving was right Asking was right Not asking was right Answer was right No app data row was expected App data row was right Voice/card/chat was acceptable

Report/grader issue

Report expected the wrong result Evidence was enough to judge Failure reason was not valid

Other thing actually right (describe below)

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 said no speech captured

2 · Card shown Logged one tablespoon peanut butter. Assumed 1 tbsp as the default serving. Tell me if you want a different amount.

3 · App data rows written created food_log_entry: Peanut butter ×1 (1 tbsp) 88 cal · 3.8g P · 2.9g C · 7.6g F

4 · UI did no 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:28:39.249Z

6 · Why this food No food-decision explanation was captured for this path.

7 · Lookup method The answer used provisional food evidence from the common-food list.

8 · Candidates → decider no candidate list captured (this path did not run DB resolution — e.g. provisional branded log)

PASSshould log the entry"I drank one cup two percent milk." (difficulty —)0.3s

Verdict Expected LOG — should log the entry. PASS: Logged (write-truth verified): 2% milk — card not captured.

Why verdict Logged (write-truth verified): 2% milk — card not captured.

My override

Things I think are wrong

Use this when the report passed something that should have failed.

Comprehension

Picked wrong food Wrong quantity Should have asked (over-logged) Shouldn't have asked (over-asked) Wrong action entirely

Execution

Didn't save to DB Wrong data saved No voice/TTS Card missing/wrong No chat

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

Use this when the report failed something that should have passed.

Actually right

Food/action was right Quantity/serving was right Asking was right Not asking was right Answer was right No app data row was expected App data row was right Voice/card/chat was acceptable

Report/grader issue

Report expected the wrong result Evidence was enough to judge Failure reason was not valid

Other thing actually right (describe below)

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.3s

1 · TTS said no speech captured

2 · Card shown Logged one cup two percent milk.

3 · App data rows written created food_log_entry: 2% milk ×1 (1 cup) 122 cal · 8.1g P · 11.7g C · 4.9g F

4 · UI did no 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:28:50.659Z

6 · Why this food No food-decision explanation was captured for this path.

7 · Lookup method The answer used provisional food evidence from the common-food list.

8 · Candidates → decider no candidate list captured (this path did not run DB resolution — e.g. provisional branded log)

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

Picked wrong food Wrong quantity Should have asked (over-logged) Shouldn't have asked (over-asked) Wrong action entirely

Execution

Didn't save to DB Wrong data saved No voice/TTS Card missing/wrong No chat

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

Use this when the report failed something that should have passed.

Actually right

Food/action was right Quantity/serving was right Asking was right Not asking was right Answer was right No app data row was expected App data row was right Voice/card/chat was acceptable

Report/grader issue

Report expected the wrong result Evidence was enough to judge Failure reason was not valid

Other thing actually right (describe below)

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 said no 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 did no 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:29:01.929Z

6 · Why this food No food-decision explanation was captured for this path.

7 · Lookup method The answer used provisional food evidence from the common-food list.

8 · Candidates → decider no 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

Picked wrong food Wrong quantity Should have asked (over-logged) Shouldn't have asked (over-asked) Wrong action entirely

Execution

Didn't save to DB Wrong data saved No voice/TTS Card missing/wrong No chat

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

Use this when the report failed something that should have passed.

Actually right

Food/action was right Quantity/serving was right Asking was right Not asking was right Answer was right No app data row was expected App data row was right Voice/card/chat was acceptable

Report/grader issue

Report expected the wrong result Evidence was enough to judge Failure reason was not valid

Other thing actually right (describe below)

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 said no 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 did no 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:29:13.281Z

6 · Why this food No food-decision explanation was captured for this path.

7 · Lookup method The answer used provisional food evidence from the common-food list.

8 · Candidates → decider no candidate list captured (this path did not run DB resolution — e.g. provisional branded log)

PASSshould log the entry"Put down four ounces grilled chicken breast." (difficulty —)0.2s

Verdict Expected LOG — should log the entry. PASS: Logged (write-truth verified): Chicken breast — card not captured.

Why verdict Logged (write-truth verified): Chicken breast — card not captured.

My override

Things I think are wrong

Use this when the report passed something that should have failed.

Comprehension

Picked wrong food Wrong quantity Should have asked (over-logged) Shouldn't have asked (over-asked) Wrong action entirely

Execution

Didn't save to DB Wrong data saved No voice/TTS Card missing/wrong No chat

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

Use this when the report failed something that should have passed.

Actually right

Food/action was right Quantity/serving was right Asking was right Not asking was right Answer was right No app data row was expected App data row was right Voice/card/chat was acceptable

Report/grader issue

Report expected the wrong result Evidence was enough to judge Failure reason was not valid

Other thing actually right (describe below)

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 said no speech captured

2 · Card shown Logged four ounces grilled chicken breast.

3 · App data rows written created food_log_entry: Chicken breast ×1 (4 oz) 187 cal · 35.2g P · 0g C · 4.1g F

4 · UI did no 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:29:24.595Z

6 · Why this food No food-decision explanation was captured for this path.

7 · Lookup method The answer used provisional food evidence from the common-food list.

8 · Candidates → decider no candidate list captured (this path did not run DB resolution — e.g. provisional branded log)

PASSshould log the entry"Record one cup cooked white rice." (difficulty —)0.2s

Verdict Expected LOG — should log the entry. PASS: Logged (write-truth verified): Cooked white rice — card not captured.

Why verdict Logged (write-truth verified): Cooked white rice — card not captured.

My override

Things I think are wrong

Use this when the report passed something that should have failed.

Comprehension

Picked wrong food Wrong quantity Should have asked (over-logged) Shouldn't have asked (over-asked) Wrong action entirely

Execution

Didn't save to DB Wrong data saved No voice/TTS Card missing/wrong No chat

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

Use this when the report failed something that should have passed.

Actually right

Food/action was right Quantity/serving was right Asking was right Not asking was right Answer was right No app data row was expected App data row was right Voice/card/chat was acceptable

Report/grader issue

Report expected the wrong result Evidence was enough to judge Failure reason was not valid

Other thing actually right (describe below)

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 said no speech captured

2 · Card shown Logged one cup cooked white rice. Assumed 1 cup as the default serving. Tell me if you want a different amount.

3 · App data rows written created food_log_entry: Cooked white rice ×1 (1 cup) 205 cal · 4.3g P · 44.2g C · 0.5g F

4 · UI did no 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:29:35.983Z

6 · Why this food No food-decision explanation was captured for this path.

7 · Lookup method The answer used provisional food evidence from the common-food list.

8 · Candidates → decider no candidate list captured (this path did not run DB resolution — e.g. provisional branded log)

Why the fails happened — comprehension vs execution vs cosmetic

Handled correctly? — by expected action

Accuracy by difficulty

Clarification follow-ups — scored separately

Cosmetic only

System / infra

Latency

Filter — controls the list below

Per-utterance detail