food-corpus-mixed-D-7c039dd0-c16-2…

Supposed to	N	Correct	Wrong	Unverified
▸ LOG — log the food	104	64 (62%)	39 (38%)	1 (1%)
39 handled wrong — click one to jump to its full detail below "I had one cup steel cut oats with water only." OVER-ASK — asked instead of logging (no saved row). "Count twenty cashews." OVER-ASK — asked instead of logging (no saved row). "Lunch included four ounces roast turkey." WRITE-TRUTH FAIL — WRONG/MISSING item "roast turkey" — no saved row with matching identity (rows: Turkey breast) "I drank eight ounces apple juice." OVER-ASK — asked instead of logging (no saved row). "Supper was one cup chickpeas." WRITE-TRUTH FAIL — MACROS off for "chickpeas": logged 926 kcal vs expected ~269 (§14 15pct/25cal band) "Ate a half cup dried cranberries." WRITE-TRUTH FAIL — MACROS off for "dried cranberries": logged 246 kcal vs expected ~185 (§14 15pct/25cal band) "Put in one hundred fifty grams skyr yogurt." OVER-ASK — asked instead of logging (no saved row). "Breakfast was three quarters cup ricotta." WRITE-TRUTH FAIL — MACROS off for "ricotta": logged 273 kcal vs expected ~180 (§14 15pct/25cal band) "Count two small flour tortillas." WRITE-TRUTH FAIL — MACROS off for "flour tortillas": logged 279 kcal vs expected ~150 (§14 15pct/25cal band) "I had eight ounces 90 percent lean ground beef." OVER-ASK — asked instead of logging (no saved row). "Log three whole wheat pancakes." OVER-ASK — asked instead of logging (no saved row). "I ate one plain bagel." WRITE-TRUTH FAIL — MACROS off for "plain bagel": logged 350 kcal vs expected ~270 (§14 15pct/25cal band) "Record six ounces scallops." WRITE-TRUTH FAIL — MACROS off for "scallops": logged 214 kcal vs expected ~150 (§14 15pct/25cal band) "Log one medium russet potato." OVER-ASK — asked instead of logging (no saved row). "I had one cup butternut squash soup." WRITE-TRUTH FAIL — MACROS off for "butternut squash soup": logged 270 kcal vs expected ~110 (§14 15pct/25cal band) "Track two tablespoons guacamole." OVER-ASK — asked instead of logging (no saved row). "Put down one cup couscous." OVER-ASK — asked instead of logging (no saved row). "Record five ounces chicken sausage." OVER-ASK — asked instead of logging (no saved row). "Log my usual bedtime tea." WRITE-TRUTH FAIL — WRONG/MISSING item "bedtime tea" — no saved row with matching identity (rows: Chamomile Tea) "Add the same ricotta as yesterday." WRITE-TRUTH FAIL — MACROS off for "ricotta": logged 273 kcal vs expected ~180 (§14 15pct/25cal band) "Log the same soup I had last night." OVER-ASK — asked instead of logging (no saved row). "Add the same salmon I had earlier." OVER-ASK — asked instead of logging (no saved row). "Log the tofu I had last time." OVER-ASK — asked instead of logging (no saved row). "Snack was one chocolate Chip's Ahoy cookie pack mini." OVER-ASK — asked instead of logging (no saved row). "Finished one Fairlife Core Power vanilla shake." WRITE-TRUTH FAIL — expected food write missing — local foodEntries delta is 0 for this turn (proven no food write, not a capture gap) "Track one Chobani zero sugar strawberry cup." OVER-ASK — asked instead of logging (no saved row). "Log a medium orange and one RXBAR chocolate sea salt." OVER-ASK — asked instead of logging (no saved row). "Lunch was a tuna melt and an apple." WRITE-TRUTH FAIL — IMPLAUSIBLE: 550 kcal is implausibly HIGH for 1 count of Tuna melt sandwich (typical 60-120 kcal [per-serving]) "I had a Kind bar and water." WRITE-TRUTH FAIL — WRONG/MISSING item "a kind bar" — no saved row with matching identity (rows: Water, Cookies & Cream Protein Bar) "Breakfast was granola, yogurt, and coffee." Reported could-not-confirm (write-confirmation false negative). "I ate noodles and a side of spinach." WRITE-TRUTH FAIL — WRONG/MISSING item "noodles" — no saved row with matching identity (rows: Cooked pasta, Spinach, Cooked pasta, Spinach) "Breakfast was cereal and oat milk." Reported could-not-confirm (write-confirmation false negative). "I had a frittata with four eggs, spinach, and feta" OVER-ASK — asked instead of logging (no saved row). "I had a grain bowl with quinoa, chickpeas, and tahini." OVER-ASK — asked instead of logging (no saved row). "Breakfast was avocado toast with egg and chili flakes." OVER-ASK — asked instead of logging (no saved row). "I made stir fry with tofu, peppers, broccoli, and oil." OVER-ASK — asked instead of logging (no saved row). "Dinner was a poke bowl with rice, tuna, avocado, and seaweed." OVER-ASK — asked instead of logging (no saved row). "I built an acai bowl with granola, banana, and coconut." OVER-ASK — asked instead of logging (no saved row). "Dinner was butter chicken with rice, naan, and cucumber salad." OVER-ASK — asked instead of logging (no saved row).
▸ CLARIFY — ask a clarifying question	29	26 (90%)	3 (10%)	0 (0%)
3 handled wrong — click one to jump to its full detail below "Log gelato." Logged a BLIND guess — no stated assumption, no correction invited. "I had an energy bar." WRONG item vs seeded default/key — WRONG/MISSING item "energy bar" — no saved row with matching identity (rows: Generic protein bar, Generic protein bar) "Add a protein shake." Logged a BLIND guess — no stated assumption, no correction invited.
▸ QUERY — answer the query	18	0 (0%)	1 (6%)	17 (94%)
1 handled wrong — click one to jump to its full detail below "What did I have mid-afternoon?" Query not answered — asked back instead of answering.
▸ DELETE — delete the entry	14	0 (0%)	14 (100%)	0 (0%)
14 handled wrong — click one to jump to its full detail below "Delete the banana from earlier." Did not delete (not understood / no removal). "Remove that Quest bar." Did not delete (not understood / no removal). "Delete the oats entry." Did not delete (not understood / no removal). "Take off the eggs." WRONG ACTION — created/logged a NEW entry on a DELETE request. "Remove the raspberries." Did not delete (not understood / no removal). "Delete the chicken log." Did not delete (not understood / no removal). "Scratch the almond butter." Did not delete (not understood / no removal). "Remove the milk entry." Did not delete (not understood / no removal). "Delete that brownie I logged last night." WRONG ACTION — created/logged a NEW entry on a DELETE request. "Remove yesterday's gelato." Did not delete (not understood / no removal). "Delete the leftover burrito entry." Did not delete (not understood / no removal). "Take out the wine from last night." Did not delete (not understood / no removal). "Remove the pastry log from earlier this week." Did not delete (not understood / no removal). "Delete the chips I shouldn't have logged." WRONG ACTION — created/logged a NEW entry on a DELETE request.
▸ UPDATE — update the entry	14	0 (0%)	14 (100%)	0 (0%)
14 handled wrong — click one to jump to its full detail below "Change the sequence banana quantity to two." Reported could-not-confirm (write-confirmation false negative). "Actually make the Quest bar two bars." Reported could-not-confirm (write-confirmation false negative). "Update the oats to one and a half cups." Reported could-not-confirm (write-confirmation false negative). "Change the eggs to four." Reported could-not-confirm (write-confirmation false negative). "Make the raspberries a half cup." Did not update (treated as new / not understood). "Update the chicken to seven ounces." Reported could-not-confirm (write-confirmation false negative). "Change almond butter to one tablespoon." Reported could-not-confirm (write-confirmation false negative). "Actually the milk was two percent, not whole." Reported could-not-confirm (write-confirmation false negative). "Actually that was strawberry, not vanilla." Reported could-not-confirm (write-confirmation false negative). "Change the portion to one and a half cups." Reported could-not-confirm (write-confirmation false negative). "Make it a quarter cup instead." Reported could-not-confirm (write-confirmation false negative). "Update that to eight ounces." Did not update — misroute-into-food (no verified mutation). "Actually it was cashew butter, not almond butter." Reported could-not-confirm (write-confirmation false negative). "Change the pear to a small." Reported could-not-confirm (write-confirmation false negative).
▸ CLARIFY_ANSWER — complete the pending action	13	2 (15%)	3 (23%)	8 (62%)
3 handled wrong — click one to jump to its full detail below "No, not the flavored skyr." Reported could-not-confirm (write-confirmation false negative). "No, that's not the bar I meant." Reported could-not-confirm (write-confirmation false negative). "That's not it; the plain one." Reported could-not-confirm (write-confirmation false negative).
▸ DECLINE — decline	2	2 (100%)	0 (0%)	0 (0%)
No errors — all handled correctly.
▸ NAVIGATE — navigate	2	1 (50%)	1 (50%)	0 (0%)
1 handled wrong — click one to jump to its full detail below "Open macro goals." Did not navigate — misrouted into a food/workout clarification or dead-ended.
▸ SETTINGS — apply the setting	1	0 (0%)	1 (100%)	0 (0%)
1 handled wrong — click one to jump to its full detail below "Set my protein goal to one hundred sixty grams." Reported could-not-confirm (write-confirmation false negative).
Total	197	95 (56%)	76	26

PASSshould log the food"Log one large banana for the sequence." (difficulty —)0.2s

Verdict Expected LOG — should log the food. 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 large banana for the sequence. Assumed 1 large 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 large banana) 121 cal · 1.5g P · 31.3g 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-07-30T20:01:41.899Z

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 food"Track one Quest birthday cake protein bar." (difficulty —)0.4s

Verdict Expected LOG — should log the food. PASS: Logged (write-truth verified): Quest Birthday Cake Protein Bar — card not captured.

Why verdict Logged (write-truth verified): Quest Birthday Cake Protein 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.4s

1 · TTS said no speech captured

2 · Card shown Logged Quest Birthday Cake Protein Bar — the macros are an estimate since this food varies by brand.

3 · App data rows written created food_log_entry: Quest Birthday Cake Protein Bar ×1 (one) 136 cal · 19.8g P · 4.2g C · 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-07-30T20:01:53.449Z

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 food"I had one cup steel cut oats with water only." (difficulty —)1.7s

Verdict Expected LOG — should log the food. 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 1.7s

1 · TTS said no speech captured

2 · Card shown Which one did you mean? 1. Steel Cut Oats (1 cup), 2. Steel Cut Oats (1 serving)

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-07-30T20:02:06.316Z

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 food"Add three scrambled eggs for lunch." (difficulty —)0.4s

Verdict Expected LOG — should log the food. 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 three scrambled eggs for lunch.

3 · App data rows written created food_log_entry: Egg ×1 (3 eggs) 215 cal · 18.9g P · 1g C · 14.3g 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-07-30T20:02:17.800Z

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 food"Log one cup raspberries as a snack." (difficulty —)0.3s

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

Why verdict Logged (write-truth verified): Raspberries — 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 raspberries 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: Raspberries ×1 (1 cup) 64 cal · 1.5g P · 14.6g C · 0.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-07-30T20:02:29.216Z

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 food"Record five ounces baked chicken thigh." (difficulty —)0.2s

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

Why verdict Logged (write-truth verified): Chicken thigh — 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 five ounces baked chicken thigh.

3 · App data rows written created food_log_entry: Chicken thigh ×1 (5 oz) 296 cal · 36.9g P · 0g C · 15.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-07-30T20:02:40.499Z

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 food"Track two tablespoons almond butter." (difficulty —)0.2s

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

Why verdict Logged (write-truth verified): Almond 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 two tablespoons almond butter.

3 · App data rows written created food_log_entry: Almond butter ×1 (2 tbsp) 196 cal · 6.7g P · 6.1g C · 17.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-07-30T20:02:51.850Z

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 food"I drank one cup whole milk." (difficulty —)0.2s

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

Why verdict Logged (write-truth verified): Whole 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.2s

1 · TTS said no speech captured

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

3 · App data rows written created food_log_entry: Whole milk ×1 (1 cup) 149 cal · 7.8g P · 11.7g C · 8.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-07-30T20:03:03.167Z

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 food"I had one large banana." (difficulty —)0.1s

Verdict Expected LOG — should log the food. 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.1s

1 · TTS said no speech captured

2 · Card shown Logged one large banana. Assumed 1 large 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 large banana) 121 cal · 1.5g P · 31.3g 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-07-30T20:03:14.449Z

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 food"Breakfast was three scrambled eggs." (difficulty —)0.1s

Verdict Expected LOG — should log the food. 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.1s

1 · TTS said no speech captured

2 · Card shown Logged three scrambled eggs.

3 · App data rows written created food_log_entry: Egg ×1 (3 eggs) 215 cal · 18.9g P · 1g C · 14.3g 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-07-30T20:03:25.749Z

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 food"Put down five ounces baked chicken thigh." (difficulty —)0.2s

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

Why verdict Logged (write-truth verified): Chicken thigh — 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 five ounces baked chicken thigh.

3 · App data rows written created food_log_entry: Chicken thigh ×1 (5 oz) 296 cal · 36.9g P · 0g C · 15.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-07-30T20:03:37.048Z

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 food"Record one cup cooked brown rice." (difficulty —)0.2s

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

Why verdict Logged (write-truth verified): Cooked brown 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 brown 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 brown rice ×1 (1 cup) 218 cal · 4.5g P · 45.8g C · 1.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-07-30T20:03:48.350Z

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 food"Snack was a medium pear." (difficulty —)0.1s

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

Why verdict Logged (write-truth verified): Pear — 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.1s

1 · TTS said no speech captured

2 · Card shown Logged a medium pear. Assumed 1 pear as the default serving. Tell me if you want a different amount.

3 · App data rows written created food_log_entry: Pear ×1 (1 pear) 101 cal · 0.7g P · 27.1g C · 0.2g 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-07-30T20:03:59.700Z

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 food"I ate four ounces baked cod." (difficulty —)0.1s

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

Why verdict Logged (write-truth verified): Cod — 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.1s

1 · TTS said no speech captured

2 · Card shown Logged four ounces baked cod.

3 · App data rows written created food_log_entry: Cod ×1 (4 oz) 119 cal · 26.1g P · 0g C · 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-07-30T20:04:11.000Z

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 food"Track one cup raspberries." (difficulty —)0.1s

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

Why verdict Logged (write-truth verified): Raspberries — 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.1s

1 · TTS said no speech captured

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

3 · App data rows written created food_log_entry: Raspberries ×1 (1 cup) 64 cal · 1.5g P · 14.6g C · 0.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-07-30T20:04:22.283Z

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)

FAILshould log the food"Count twenty cashews." (difficulty —)1.2s

Verdict Expected LOG — should log the food. 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 1.2s

1 · TTS said no speech captured

2 · Card shown Which one did you mean? 1. my usual cashews, 2. Cashews (1 oz)

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-07-30T20:04:34.567Z

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)

FAILshould log the food"Lunch included four ounces roast turkey." (difficulty —)2.4s

Verdict Expected LOG — should log the food. FAIL: WRITE-TRUTH FAIL — WRONG/MISSING item "roast turkey" — no saved row with matching identity (rows: Turkey breast)

Why verdict WRITE-TRUTH FAIL — WRONG/MISSING item "roast turkey" — no saved row with matching identity (rows: Turkey breast)

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

1 · TTS said no speech captured

2 · Card shown I logged Turkey breast (four ounces (113.4 g)) — let me know if that's not right.

3 · App data rows written created food_log_entry: Turkey breast ×1 (four ounces (113.4 g)) 153 cal · 32.9g P · 0g C · 1.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-07-30T20:04:48.083Z

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 food"Save one cup roasted Brussels sprouts." (difficulty —)0.2s

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

Why verdict Logged (write-truth verified): Brussels sprouts — 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 roasted brussels sprouts. Assumed 1 cup as the default serving. Tell me if you want a different amount.

3 · App data rows written created food_log_entry: Brussels sprouts ×1 (1 cup) 70 cal · 5.4g P · 14.4g 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-07-30T20:04:59.365Z

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)

FAILshould log the food"I drank eight ounces apple juice." (difficulty —)1.7s

Verdict Expected LOG — should log the food. 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 1.7s

1 · TTS said no speech captured

2 · Card shown What food did you log? Could you be more specific?

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-07-30T20:05:12.251Z

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 food"Note three slices Canadian bacon." (difficulty —)0.3s

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

Why verdict Logged (write-truth verified): Canadian bacon — 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 note three slices canadian bacon.

3 · App data rows written created food_log_entry: Canadian bacon ×1 (3 slices) 101 cal · 19.5g P · 1.2g C · 1.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-07-30T20:05:23.667Z

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)

FAILshould log the food"Supper was one cup chickpeas." (difficulty —)0.3s

Verdict Expected LOG — should log the food. FAIL: WRITE-TRUTH FAIL — MACROS off for "chickpeas": logged 926 kcal vs expected ~269 (§14 15pct/25cal band)

Why verdict WRITE-TRUTH FAIL — MACROS off for "chickpeas": logged 926 kcal vs expected ~269 (§14 15pct/25cal band)

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 chickpeas. Assumed 1 cup as the default serving. Tell me if you want a different amount.

3 · App data rows written created food_log_entry: Roasted chickpeas ×1 (1 cup) 926 cal · 48g P · 151.2g C · 14.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-07-30T20:05:50.398Z

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 food"Enter one medium grapefruit." (difficulty —)0.1s

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

Why verdict Logged (write-truth verified): Grapefruit — 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.1s

1 · TTS said no speech captured

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

3 · App data rows written created food_log_entry: Grapefruit ×1 (1 grapefruit) 97 cal · 1.8g P · 24.6g C · 0.2g 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-07-30T20:06:01.684Z

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)

FAILshould log the food"Ate a half cup dried cranberries." (difficulty —)0.6s

Verdict Expected LOG — should log the food. FAIL: WRITE-TRUTH FAIL — MACROS off for "dried cranberries": logged 246 kcal vs expected ~185 (§14 15pct/25cal band)

Why verdict WRITE-TRUTH FAIL — MACROS off for "dried cranberries": logged 246 kcal vs expected ~185 (§14 15pct/25cal band)

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

1 · TTS said no speech captured

2 · Card shown I logged Cranberries, Dried (1 cup) (a half cup (80 g)) — let me know if that's not right.

3 · App data rows written created food_log_entry: Cranberries, Dried ×1 (a half cup (80 g)) 246 cal · 0.2g P · 66.2g C · 0.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-07-30T20:06:13.350Z

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

7 · Lookup method The answer used provisional food evidence from the USDA nutrition database.

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

PASSshould log the food"Track two tablespoons almond butter." (difficulty —)0.2s

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

Why verdict Logged (write-truth verified): Almond 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 two tablespoons almond butter.

3 · App data rows written created food_log_entry: Almond butter ×1 (2 tbsp) 196 cal · 6.7g P · 6.1g C · 17.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-07-30T20:06:24.650Z

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 food"Dinner side was one cup asparagus." (difficulty —)0.3s

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

Why verdict Logged (write-truth verified): Asparagus — 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 asparagus. Assumed 1 cup as the default serving. Tell me if you want a different amount.

3 · App data rows written created food_log_entry: Asparagus ×1 (1 cup) 40 cal · 4.3g P · 7.4g 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-07-30T20:06:36.068Z

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 food"I had two cups watermelon." (difficulty —)0.2s

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

Why verdict Logged (write-truth verified): Watermelon — 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 cups watermelon.

3 · App data rows written created food_log_entry: Watermelon ×1 (2 cup) 91 cal · 1.8g P · 23.1g C · 0.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-07-30T20:06:47.350Z

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)

FAILshould log the food"Put in one hundred fifty grams skyr yogurt." (difficulty —)0.2s

Verdict Expected LOG — should log the food. 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 0.2s

1 · TTS said no speech captured

2 · Card shown I found Plain Greek yogurt, but I also heard hundred fifty skyr yogurt. Should I log those separately too?

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-07-30T20:06:58.786Z

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 food"Log one cup whole milk." (difficulty —)0.2s

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

Why verdict Logged (write-truth verified): Whole 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.2s

1 · TTS said no speech captured

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

3 · App data rows written created food_log_entry: Whole milk ×1 (1 cup) 149 cal · 7.8g P · 11.7g C · 8.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-07-30T20:07:10.066Z

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)

FAILshould log the food"Breakfast was three quarters cup ricotta." (difficulty —)0.2s

Verdict Expected LOG — should log the food. FAIL: WRITE-TRUTH FAIL — MACROS off for "ricotta": logged 273 kcal vs expected ~180 (§14 15pct/25cal band)

Why verdict WRITE-TRUTH FAIL — MACROS off for "ricotta": logged 273 kcal vs expected ~180 (§14 15pct/25cal band)

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 three quarters cup ricotta.

3 · App data rows written created food_log_entry: Ricotta cheese ×1 (0.75 cup) 273 cal · 17.7g P · 11.1g C · 17.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-07-30T20:07:21.349Z

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)

FAILshould log the food"Count two small flour tortillas." (difficulty —)0.2s

Verdict Expected LOG — should log the food. FAIL: WRITE-TRUTH FAIL — MACROS off for "flour tortillas": logged 279 kcal vs expected ~150 (§14 15pct/25cal band)

Why verdict WRITE-TRUTH FAIL — MACROS off for "flour tortillas": logged 279 kcal vs expected ~150 (§14 15pct/25cal band)

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 small flour tortillas.

3 · App data rows written created food_log_entry: Flour tortilla ×1 (2 flour tortillas) 279 cal · 7.7g P · 45g C · 7.2g 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-07-30T20:07:32.651Z

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)

FAILshould log the food"I had eight ounces 90 percent lean ground beef." (difficulty —)5.1s

Verdict Expected LOG — should log the food. 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.1s

1 · TTS said no speech captured

2 · Card shown Which one did you mean? 1. Lean Ground Beef — BUTCHER'S BRAND, 2. Lean Ground Beef — FRESHLAST PACK, 3. Lean Ground Beef — The Kroger Co., 4. Lean Ground Beef — FPL Food LLC

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-07-30T20:07:48.851Z

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 food"Add one cup pinto beans." (difficulty —)0.2s

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

Why verdict Logged (write-truth verified): Pinto beans — 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 pinto beans. Assumed 1 cup as the default serving. Tell me if you want a different amount.

3 · App data rows written created food_log_entry: Pinto beans ×1 (1 cup) 245 cal · 15.4g P · 44.5g C · 1.2g 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-07-30T20:08:00.217Z

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 food"Track one whole avocado." (difficulty —)0.1s

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

Why verdict Logged (write-truth verified): Avocado — 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.1s

1 · TTS said no speech captured

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

3 · App data rows written created food_log_entry: Avocado ×1 (1 avocado) 240 cal · 3g P · 12.8g C · 22g 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-07-30T20:08:11.499Z

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)

FAILshould log the food"Log three whole wheat pancakes." (difficulty —)2.7s

Verdict Expected LOG — should log the food. 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 2.7s

1 · TTS said no speech captured

2 · Card shown Did you have syrup, butter, or another topping with it? I did not log it yet because add-ons can change the nutrition.

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-07-30T20:08:25.282Z

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)

FAILshould log the food"I ate one plain bagel." (difficulty —)0.1s

Verdict Expected LOG — should log the food. FAIL: WRITE-TRUTH FAIL — MACROS off for "plain bagel": logged 350 kcal vs expected ~270 (§14 15pct/25cal band)

Why verdict WRITE-TRUTH FAIL — MACROS off for "plain bagel": logged 350 kcal vs expected ~270 (§14 15pct/25cal band)

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

1 · TTS said no speech captured

2 · Card shown Logged one plain bagel. Assumed a fresh/deli-size bagel; say packaged or Lender's if it was a bread-aisle bagel Assumed 1 plain bagel as the default serving. Tell me if you want a different amount.

3 · App data rows written created food_log_entry: Plain bagel ×1 (1 plain bagel) 350 cal · 14g P · 67.2g C · 2.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-07-30T20:08:36.550Z

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)

FAILshould log the food"Record six ounces scallops." (difficulty —)0.6s

Verdict Expected LOG — should log the food. FAIL: WRITE-TRUTH FAIL — MACROS off for "scallops": logged 214 kcal vs expected ~150 (§14 15pct/25cal band)

Why verdict WRITE-TRUTH FAIL — MACROS off for "scallops": logged 214 kcal vs expected ~150 (§14 15pct/25cal band)

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

1 · TTS said no speech captured

2 · Card shown I logged Scallops, Baked or Broiled (six ounces (170.1 g)) — let me know if that's not right.

3 · App data rows written created food_log_entry: Scallops, Baked or Broiled ×1 (six ounces (170.1 g)) 214 cal · 25.5g P · 6.8g C · 8.7g 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-07-30T20:08:48.299Z

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

7 · Lookup method The answer used provisional food evidence from the USDA nutrition database.

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

PASSshould log the food"Snack was two Babybel cheeses." (difficulty —)0.1s

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

Why verdict Logged (write-truth verified): Babybel — 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.1s

1 · TTS said no speech captured

2 · Card shown Logged two babybel cheeses.

3 · App data rows written created food_log_entry: Babybel ×1 (2 babybel) 140 cal · 10g P · 0g C · 11g 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-07-30T20:08:59.584Z

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 food"Add two teaspoons butter." (difficulty —)0.1s

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

Why verdict Logged (write-truth verified): 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.1s

1 · TTS said no speech captured

2 · Card shown Logged two teaspoons butter.

3 · App data rows written created food_log_entry: Butter ×1 (2 tsp) 72 cal · 0.1g P · 0g C · 8.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-07-30T20:09:10.934Z

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 food"I had one cup farro." (difficulty —)0.1s

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

Why verdict Logged (write-truth verified): Cooked farro — 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.1s

1 · TTS said no speech captured

2 · Card shown Logged one cup farro. 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 farro ×1 (1 cup) 240 cal · 8.6g P · 50.7g C · 1.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-07-30T20:09:22.217Z

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)

FAILshould log the food"Log one medium russet potato." (difficulty —)5.3s

Verdict Expected LOG — should log the food. 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.3s

1 · TTS said no speech captured

2 · Card shown Was the potato plain, or did it have toppings like butter, sour cream, or cheese? I did not log it yet because add-ons can change the nutrition.

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-07-30T20:09:38.653Z

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 food"Track ten ounces green tea." (difficulty —)0.1s

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

Why verdict Logged (write-truth verified): Green tea — 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.1s

1 · TTS said no speech captured

2 · Card shown Logged ten ounces green tea.

3 · App data rows written created food_log_entry: Green tea ×1 (10 oz) 3 cal · 0g P · 0g C · 0g 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-07-30T20:10:05.852Z

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 food"Count one cup cherry tomatoes." (difficulty —)0.2s

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

Why verdict Logged (write-truth verified): Cherry tomatoes — 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 cherry tomatoes. Assumed 1 cup as the default serving. Tell me if you want a different amount.

3 · App data rows written created food_log_entry: Cherry tomatoes ×1 (1 cup) 43 cal · 2.2g P · 9.4g 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-07-30T20:10:17.151Z

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 food"Dinner was six ounces pork tenderloin." (difficulty —)0.1s

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

Why verdict Logged (write-truth verified): Pork tenderloin — 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.1s

1 · TTS said no speech captured

2 · Card shown Logged six ounces pork tenderloin.

3 · App data rows written created food_log_entry: Pork tenderloin ×1 (6 oz) 243 cal · 44.2g P · 0g C · 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-07-30T20:10:28.500Z

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)

FAILshould log the food"I had one cup butternut squash soup." (difficulty —)1.2s

Verdict Expected LOG — should log the food. FAIL: WRITE-TRUTH FAIL — MACROS off for "butternut squash soup": logged 270 kcal vs expected ~110 (§14 15pct/25cal band)

Why verdict WRITE-TRUTH FAIL — MACROS off for "butternut squash soup": logged 270 kcal vs expected ~110 (§14 15pct/25cal band)

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

1 · TTS said no speech captured

2 · Card shown Logged The Cheesecake Factory Cup of Butternut Squash Soup — the macros are an estimate since this food varies by brand.

3 · App data rows written created food_log_entry: The Cheesecake Factory Cup of Butternut Squash Soup ×1 (1 cup) 270 cal · 3g P · 21g C · 21g 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-07-30T20:10:40.850Z

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

7 · Lookup method The answer used provisional food evidence from user default.

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

PASSshould log the food"Add three rice cakes." (difficulty —)0.2s

Verdict Expected LOG — should log the food. PASS: Logged (write-truth verified): Plain rice cakes — card not captured.

Why verdict Logged (write-truth verified): Plain rice cakes — 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 three rice cakes.

3 · App data rows written created food_log_entry: Plain rice cakes ×1 (3 rice cakes) 104 cal · 2.2g P · 22g C · 0.8g 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-07-30T20:10:52.117Z

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 food"Log one cup blackberries." (difficulty —)0.1s

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

Why verdict Logged (write-truth verified): Blackberries — 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.1s

1 · TTS said no speech captured

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

3 · App data rows written created food_log_entry: Blackberries ×1 (1 cup) 62 cal · 2g P · 14.7g C · 0.7g 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-07-30T20:11:03.418Z

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)

FAILshould log the food"Track two tablespoons guacamole." (difficulty —)0.9s

Verdict Expected LOG — should log the food. 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 0.9s

1 · TTS said no speech captured

2 · Card shown Which one did you mean? 1. Guacamole (tablespoon), 2. Guacamole (2 tablespoon)

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-07-30T20:11:15.483Z

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 food"I ate one medium nectarine." (difficulty —)0.1s

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

Why verdict Logged (write-truth verified): Nectarine — 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.1s

1 · TTS said no speech captured

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

3 · App data rows written created food_log_entry: Nectarine ×1 (1 nectarine) 62 cal · 1.5g P · 14.8g 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-07-30T20:11:26.767Z

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)

FAILshould log the food"Put down one cup couscous." (difficulty —)2.7s

Verdict Expected LOG — should log the food. 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 2.7s

1 · TTS said no speech captured

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

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-07-30T20:11:40.583Z

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)

FAILshould log the food"Record five ounces chicken sausage." (difficulty —)1.3s

Verdict Expected LOG — should log the food. 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 1.3s

1 · TTS said no speech captured

2 · Card shown Which one did you mean? 1. Chicken breakfast sausage links (5 ounce), 2. Chicken breakfast sausage links (3 chicken breakfast sausage links)

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-07-30T20:11:53.118Z

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 food"Add my usual RXBAR." (difficulty —)0.1s

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

Why verdict Logged (write-truth verified): RXBAR Blueberry — 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.1s

1 · TTS said no speech captured

2 · Card shown Logged RXBAR RXBAR Blueberry. Using your saved "my usual rxbar". Tell me if that is wrong.

3 · App data rows written created food_log_entry: RXBAR Blueberry ×1 (bar) 210 cal · 12g P · 25g C · 8g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seed food: RXBAR RXBAR Blueberry

{
  "type": "food_item",
  "foodItem": {
    "id": "seed-d-rxbar",
    "name": "RXBAR Blueberry",
    "brand": "RXBAR",
    "source": "manual",
    "servingLabel": "bar",
    "servingQuantity": 1,
    "servingUnit": "bar",
    "macrosPerServing": {
      "calories": 210,
      "proteinGrams": 12,
      "fatGrams": 8,
      "carbsGrams": 25
    },
    "aliases": [],
    "timesLogged": 0,
    "createdAt": "2026-07-16T12:00:00.000Z"
  }
}

food_default

{
  "type": "food_default",
  "phrase": "my usual RXBAR",
  "foodItemId": "seed-d-rxbar",
  "settings": {
    "quickLogMode": "fixed",
    "defaultQuantity": 1,
    "defaultServingLabel": "bar",
    "displayLabel": "my usual RXBAR",
    "confirmBeforeLog": false
  }
}

snapshot captured 2026-07-30T20:12:04.318Z

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

7 · Lookup method The answer used provisional food evidence from user default.

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

PASSshould log the food"I had my usual skyr." (difficulty —)0.1s

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

Why verdict Logged (write-truth verified): Plain Skyr — 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.1s

1 · TTS said no speech captured

2 · Card shown Logged Codex Test Dairy Plain Skyr. Using your saved "my usual skyr". Tell me if that is wrong.

3 · App data rows written created food_log_entry: Plain Skyr ×1 (cup) 110 cal · 19g P · 7g C · 0g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seed food: Codex Test Dairy Plain Skyr

{
  "type": "food_item",
  "foodItem": {
    "id": "seed-d-skyr",
    "name": "Plain Skyr",
    "brand": "Codex Test Dairy",
    "source": "manual",
    "servingLabel": "cup",
    "servingQuantity": 1,
    "servingUnit": "cup",
    "macrosPerServing": {
      "calories": 110,
      "proteinGrams": 19,
      "fatGrams": 0,
      "carbsGrams": 7
    },
    "aliases": [],
    "timesLogged": 0,
    "createdAt": "2026-07-16T12:00:00.000Z"
  }
}

food_default

{
  "type": "food_default",
  "phrase": "my usual skyr",
  "foodItemId": "seed-d-skyr",
  "settings": {
    "quickLogMode": "fixed",
    "defaultQuantity": 1,
    "defaultServingLabel": "cup",
    "displayLabel": "my usual skyr",
    "confirmBeforeLog": false
  }
}

snapshot captured 2026-07-30T20:12:15.534Z

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

7 · Lookup method The answer used provisional food evidence from user default.

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

PASSshould log the food"Lunch was my usual chicken salad." (difficulty —)0.1s

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

Why verdict Logged (write-truth verified): Chicken Salad Scoop — 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.1s

1 · TTS said no speech captured

2 · Card shown Logged Codex Test Deli Chicken Salad Scoop. Using your saved "my usual chicken salad". Tell me if that is wrong.

3 · App data rows written created food_log_entry: Chicken Salad Scoop ×1 (scoop) 280 cal · 22g P · 6g C · 18g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seed food: Codex Test Deli Chicken Salad Scoop

{
  "type": "food_item",
  "foodItem": {
    "id": "seed-d-chix-salad",
    "name": "Chicken Salad Scoop",
    "brand": "Codex Test Deli",
    "source": "manual",
    "servingLabel": "scoop",
    "servingQuantity": 1,
    "servingUnit": "scoop",
    "macrosPerServing": {
      "calories": 280,
      "proteinGrams": 22,
      "fatGrams": 18,
      "carbsGrams": 6
    },
    "aliases": [],
    "timesLogged": 0,
    "createdAt": "2026-07-16T12:00:00.000Z"
  }
}

food_default

{
  "type": "food_default",
  "phrase": "my usual chicken salad",
  "foodItemId": "seed-d-chix-salad",
  "settings": {
    "quickLogMode": "fixed",
    "defaultQuantity": 1,
    "defaultServingLabel": "scoop",
    "displayLabel": "my usual chicken salad",
    "confirmBeforeLog": false
  }
}

snapshot captured 2026-07-30T20:12:26.733Z

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

7 · Lookup method The answer used provisional food evidence from user default.

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

PASSshould log the food"Dinner side was my usual quinoa." (difficulty —)0.1s

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

Why verdict Logged (write-truth verified): Cooked Quinoa — 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.1s

1 · TTS said no speech captured

2 · Card shown Logged Cooked Quinoa. Using your saved "my usual quinoa". Tell me if that is wrong.

3 · App data rows written created food_log_entry: Cooked Quinoa ×1 (cup) 222 cal · 8g P · 39g C · 3.6g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seed food: Cooked Quinoa

{
  "type": "food_item",
  "foodItem": {
    "id": "seed-d-quinoa",
    "name": "Cooked Quinoa",
    "brand": null,
    "source": "manual",
    "servingLabel": "cup",
    "servingQuantity": 1,
    "servingUnit": "cup",
    "macrosPerServing": {
      "calories": 222,
      "proteinGrams": 8,
      "fatGrams": 3.6,
      "carbsGrams": 39
    },
    "aliases": [],
    "timesLogged": 0,
    "createdAt": "2026-07-16T12:00:00.000Z"
  }
}

food_default

{
  "type": "food_default",
  "phrase": "my usual quinoa",
  "foodItemId": "seed-d-quinoa",
  "settings": {
    "quickLogMode": "fixed",
    "defaultQuantity": 1,
    "defaultServingLabel": "cup",
    "displayLabel": "my usual quinoa",
    "confirmBeforeLog": false
  }
}

snapshot captured 2026-07-30T20:12:38.001Z

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

7 · Lookup method The answer used provisional food evidence from user default.

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

PASSshould log the food"Track my usual cashews." (difficulty —)0.1s

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

Why verdict Logged (write-truth verified): Cashews — 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.1s

1 · TTS said no speech captured

2 · Card shown Logged Cashews. Using your saved "my usual cashews". Tell me if that is wrong.

3 · App data rows written created food_log_entry: Cashews ×1 (ounce) 157 cal · 5g P · 9g C · 12g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seed food: Cashews

{
  "type": "food_item",
  "foodItem": {
    "id": "seed-d-cashews",
    "name": "Cashews",
    "brand": null,
    "source": "manual",
    "servingLabel": "ounce",
    "servingQuantity": 1,
    "servingUnit": "oz",
    "macrosPerServing": {
      "calories": 157,
      "proteinGrams": 5,
      "fatGrams": 12,
      "carbsGrams": 9
    },
    "aliases": [],
    "timesLogged": 0,
    "createdAt": "2026-07-16T12:00:00.000Z"
  }
}

food_default

{
  "type": "food_default",
  "phrase": "my usual cashews",
  "foodItemId": "seed-d-cashews",
  "settings": {
    "quickLogMode": "fixed",
    "defaultQuantity": 1,
    "defaultServingLabel": "ounce",
    "displayLabel": "my usual cashews",
    "confirmBeforeLog": false
  }
}

snapshot captured 2026-07-30T20:12:49.200Z

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

7 · Lookup method The answer used provisional food evidence from user default.

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

PASSshould log the food"Log my default oat milk." (difficulty —)0.1s

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

Why verdict Logged (write-truth verified): Oat 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.1s

1 · TTS said no speech captured

2 · Card shown Logged Oat Milk. Using your saved "my default oat milk". Tell me if that is wrong.

3 · App data rows written created food_log_entry: Oat Milk ×1 (cup) 120 cal · 3g P · 16g C · 5g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seed food: Oat Milk

{
  "type": "food_item",
  "foodItem": {
    "id": "seed-d-oatmilk",
    "name": "Oat Milk",
    "brand": null,
    "source": "manual",
    "servingLabel": "cup",
    "servingQuantity": 1,
    "servingUnit": "cup",
    "macrosPerServing": {
      "calories": 120,
      "proteinGrams": 3,
      "fatGrams": 5,
      "carbsGrams": 16
    },
    "aliases": [],
    "timesLogged": 0,
    "createdAt": "2026-07-16T12:00:00.000Z"
  }
}

food_default

{
  "type": "food_default",
  "phrase": "my default oat milk",
  "foodItemId": "seed-d-oatmilk",
  "settings": {
    "quickLogMode": "fixed",
    "defaultQuantity": 1,
    "defaultServingLabel": "cup",
    "displayLabel": "my default oat milk",
    "confirmBeforeLog": false
  }
}

snapshot captured 2026-07-30T20:13:00.535Z

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

7 · Lookup method The answer used provisional food evidence from user default.

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

PASSshould log the food"Add my usual evening cocoa." (difficulty —)0.1s

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

Why verdict Logged (write-truth verified): Hot Cocoa — 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.1s

1 · TTS said no speech captured

2 · Card shown Logged Codex Test Cafe Hot Cocoa. Using your saved "my usual evening cocoa". Tell me if that is wrong.

3 · App data rows written created food_log_entry: Hot Cocoa ×1 (cup) 140 cal · 4g P · 24g C · 3g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seed food: Codex Test Cafe Hot Cocoa

{
  "type": "food_item",
  "foodItem": {
    "id": "seed-d-cocoa",
    "name": "Hot Cocoa",
    "brand": "Codex Test Cafe",
    "source": "manual",
    "servingLabel": "cup",
    "servingQuantity": 1,
    "servingUnit": "cup",
    "macrosPerServing": {
      "calories": 140,
      "proteinGrams": 4,
      "fatGrams": 3,
      "carbsGrams": 24
    },
    "aliases": [],
    "timesLogged": 0,
    "createdAt": "2026-07-16T12:00:00.000Z"
  }
}

food_default

{
  "type": "food_default",
  "phrase": "my usual evening cocoa",
  "foodItemId": "seed-d-cocoa",
  "settings": {
    "quickLogMode": "fixed",
    "defaultQuantity": 1,
    "defaultServingLabel": "cup",
    "displayLabel": "my usual evening cocoa",
    "confirmBeforeLog": false
  }
}

snapshot captured 2026-07-30T20:13:11.734Z

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

7 · Lookup method The answer used provisional food evidence from user default.

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

PASSshould ask a clarifying question"I had my normal steel cut oats." (difficulty —)0.1s

Verdict Expected CLARIFY — should ask a clarifying question. PASS: Decisive guess with stated assumption + invited correction (good-guessing).

Why verdict Decisive guess with stated assumption + invited correction (good-guessing).

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

1 · TTS said no speech captured

2 · Card shown Logged Steel Cut Oats. Using your saved "my normal steel cut oats". Tell me if that is wrong.

3 · App data rows written created food_log_entry: Steel Cut Oats ×1 (cup) 170 cal · 7g P · 29g C · 3g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seed food: Steel Cut Oats

{
  "type": "food_item",
  "foodItem": {
    "id": "seed-d-oats",
    "name": "Steel Cut Oats",
    "brand": null,
    "source": "manual",
    "servingLabel": "cup",
    "servingQuantity": 1,
    "servingUnit": "cup",
    "macrosPerServing": {
      "calories": 170,
      "proteinGrams": 7,
      "fatGrams": 3,
      "carbsGrams": 29
    },
    "aliases": [],
    "timesLogged": 0,
    "createdAt": "2026-07-16T12:00:00.000Z"
  }
}

food_default

{
  "type": "food_default",
  "phrase": "my normal steel cut oats",
  "foodItemId": "seed-d-oats",
  "settings": {
    "quickLogMode": "fixed",
    "defaultQuantity": 1,
    "defaultServingLabel": "cup",
    "displayLabel": "my normal steel cut oats",
    "confirmBeforeLog": false
  }
}

snapshot captured 2026-07-30T20:13:22.985Z

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

7 · Lookup method The answer used provisional food evidence from user default.

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

PASSshould log the food"Track my go-to latte." (difficulty —)0.1s

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

Why verdict Logged (write-truth verified): Caffe Latte — 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.1s

1 · TTS said no speech captured

2 · Card shown Logged Codex Test Cafe Caffe Latte. Using your saved "my go to latte". Tell me if that is wrong.

3 · App data rows written created food_log_entry: Caffe Latte ×1 (cup) 150 cal · 8g P · 14g C · 6g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seed food: Codex Test Cafe Caffe Latte

{
  "type": "food_item",
  "foodItem": {
    "id": "seed-d-latte",
    "name": "Caffe Latte",
    "brand": "Codex Test Cafe",
    "source": "manual",
    "servingLabel": "cup",
    "servingQuantity": 1,
    "servingUnit": "cup",
    "macrosPerServing": {
      "calories": 150,
      "proteinGrams": 8,
      "fatGrams": 6,
      "carbsGrams": 14
    },
    "aliases": [],
    "timesLogged": 0,
    "createdAt": "2026-07-16T12:00:00.000Z"
  }
}

food_default

{
  "type": "food_default",
  "phrase": "my go-to latte",
  "foodItemId": "seed-d-latte",
  "settings": {
    "quickLogMode": "fixed",
    "defaultQuantity": 1,
    "defaultServingLabel": "cup",
    "displayLabel": "my go-to latte",
    "confirmBeforeLog": false
  }
}

snapshot captured 2026-07-30T20:13:34.167Z

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

7 · Lookup method The answer used provisional food evidence from user default.

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

FAILshould log the food"Log my usual bedtime tea." (difficulty —)0.1s

Verdict Expected LOG — should log the food. FAIL: WRITE-TRUTH FAIL — WRONG/MISSING item "bedtime tea" — no saved row with matching identity (rows: Chamomile Tea)

Why verdict WRITE-TRUTH FAIL — WRONG/MISSING item "bedtime tea" — no saved row with matching identity (rows: Chamomile Tea)

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

1 · TTS said no speech captured

2 · Card shown Logged Chamomile Tea. Using your saved "my usual bedtime tea". Tell me if that is wrong.

3 · App data rows written created food_log_entry: Chamomile Tea ×1 (cup) 0 cal · 0g P · 0g C · 0g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seed food: Chamomile Tea

{
  "type": "food_item",
  "foodItem": {
    "id": "seed-d-tea",
    "name": "Chamomile Tea",
    "brand": null,
    "source": "manual",
    "servingLabel": "cup",
    "servingQuantity": 1,
    "servingUnit": "cup",
    "macrosPerServing": {
      "calories": 0,
      "proteinGrams": 0,
      "fatGrams": 0,
      "carbsGrams": 0
    },
    "aliases": [],
    "timesLogged": 0,
    "createdAt": "2026-07-16T12:00:00.000Z"
  }
}

food_default

{
  "type": "food_default",
  "phrase": "my usual bedtime tea",
  "foodItemId": "seed-d-tea",
  "settings": {
    "quickLogMode": "fixed",
    "defaultQuantity": 1,
    "defaultServingLabel": "cup",
    "displayLabel": "my usual bedtime tea",
    "confirmBeforeLog": false
  }
}

snapshot captured 2026-07-30T20:13:45.368Z

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

7 · Lookup method The answer used provisional food evidence from user default.

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

FAILshould log the food"Add the same ricotta as yesterday." (difficulty —)0.2s

Verdict Expected LOG — should log the food. FAIL: WRITE-TRUTH FAIL — MACROS off for "ricotta": logged 273 kcal vs expected ~180 (§14 15pct/25cal band)

Why verdict WRITE-TRUTH FAIL — MACROS off for "ricotta": logged 273 kcal vs expected ~180 (§14 15pct/25cal band)

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 Ricotta cheese. Using your recent Ricotta cheese history. Tell me if that is wrong.

3 · App data rows written created food_log_entry: Ricotta cheese ×1 (0.75 cup) 273 cal · 17.7g P · 11.1g C · 17.5g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seed food: Codex Test Dairy Part Skim Ricotta

{
  "type": "food_item",
  "foodItem": {
    "id": "seed-d-ricotta",
    "name": "Part Skim Ricotta",
    "brand": "Codex Test Dairy",
    "source": "manual",
    "servingLabel": "cup",
    "servingQuantity": 1,
    "servingUnit": "cup",
    "macrosPerServing": {
      "calories": 180,
      "proteinGrams": 14,
      "fatGrams": 12,
      "carbsGrams": 6
    },
    "aliases": [],
    "timesLogged": 0,
    "createdAt": "2026-07-16T12:00:00.000Z"
  }
}

Seed food history: 0.75 for seed-d-ricotta at 2026-07-17T13:00:00.000Z

{
  "type": "food_history",
  "foodItemId": "seed-d-ricotta",
  "quantity": 0.75,
  "loggedAt": "2026-07-17T13:00:00.000Z"
}

snapshot captured 2026-07-30T20:14:12.066Z

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

7 · Lookup method The answer used provisional food evidence from user default.

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

UNVERIFIEDunclassifiedshould log the food"Same granola as yesterday." (difficulty —)0.4s

Verdict Expected LOG — should log the food. UNVERIFIED: CONTEXT-FRAGMENT — app asked for missing context; needs multi-turn replay (not a single-shot fail).

Why verdict CONTEXT-FRAGMENT — app asked for missing context; needs multi-turn replay (not a single-shot fail).

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 I hear more than one saved version that could match "same granola as yesterday". Which exact food and amount should I log?

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seed food: Codex Test Pantry Honey Granola

{
  "type": "food_item",
  "foodItem": {
    "id": "seed-d-yest-granola",
    "name": "Honey Granola",
    "brand": "Codex Test Pantry",
    "source": "manual",
    "servingLabel": "cup",
    "servingQuantity": 1,
    "servingUnit": "cup",
    "macrosPerServing": {
      "calories": 240,
      "proteinGrams": 6,
      "fatGrams": 8,
      "carbsGrams": 38
    },
    "aliases": [],
    "timesLogged": 0,
    "createdAt": "2026-07-16T12:00:00.000Z"
  }
}

Seed food history: 0.5 for seed-d-yest-granola at 2026-07-17T08:00:00.000Z

{
  "type": "food_history",
  "foodItemId": "seed-d-yest-granola",
  "quantity": 0.5,
  "loggedAt": "2026-07-17T08:00:00.000Z"
}

snapshot captured 2026-07-30T20:14:23.667Z

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)

FAILshould log the food"Log the same soup I had last night." (difficulty —)0.4s

Verdict Expected LOG — should log the food. 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 0.4s

1 · TTS said no speech captured

2 · Card shown I heard you want the same the same soup i had last night as before, but I do not have a matching saved log yet. Which exact food and amount should I log?

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seed food: Codex Test Kitchen Lentil Soup

{
  "type": "food_item",
  "foodItem": {
    "id": "seed-d-soup",
    "name": "Lentil Soup",
    "brand": "Codex Test Kitchen",
    "source": "manual",
    "servingLabel": "bowl",
    "servingQuantity": 1,
    "servingUnit": "bowl",
    "macrosPerServing": {
      "calories": 220,
      "proteinGrams": 12,
      "fatGrams": 4,
      "carbsGrams": 34
    },
    "aliases": [],
    "timesLogged": 0,
    "createdAt": "2026-07-16T12:00:00.000Z"
  }
}

Seed food history: 1 for seed-d-soup at 2026-07-17T19:30:00.000Z

{
  "type": "food_history",
  "foodItemId": "seed-d-soup",
  "quantity": 1,
  "loggedAt": "2026-07-17T19:30:00.000Z"
}

snapshot captured 2026-07-30T20:14:35.218Z

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 food"Same bagel as this morning." (difficulty —)0.2s

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

Why verdict Logged (write-truth verified): Everything Bagel — 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 Everything Bagel. Using your recent Everything Bagel history. Tell me if that is wrong.

3 · App data rows written created food_log_entry: Everything Bagel ×1 (bagel) 280 cal · 10g P · 54g C · 2g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seed food: Everything Bagel

{
  "type": "food_item",
  "foodItem": {
    "id": "seed-d-hist-bagel",
    "name": "Everything Bagel",
    "brand": null,
    "source": "manual",
    "servingLabel": "bagel",
    "servingQuantity": 1,
    "servingUnit": "bagel",
    "macrosPerServing": {
      "calories": 280,
      "proteinGrams": 10,
      "fatGrams": 2,
      "carbsGrams": 54
    },
    "aliases": [],
    "timesLogged": 0,
    "createdAt": "2026-07-16T12:00:00.000Z"
  }
}

Seed food history: 1 for seed-d-hist-bagel at 2026-07-18T07:30:00.000Z

{
  "type": "food_history",
  "foodItemId": "seed-d-hist-bagel",
  "quantity": 1,
  "loggedAt": "2026-07-18T07:30:00.000Z"
}

snapshot captured 2026-07-30T20:14:46.551Z

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

7 · Lookup method The answer used provisional food evidence from user default.

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

FAILshould log the food"Add the same salmon I had earlier." (difficulty —)0.4s

Verdict Expected LOG — should log the food. 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 0.4s

1 · TTS said no speech captured

2 · Card shown I hear more than one saved version that could match "the same salmon i had earlier". Which exact food and amount should I log?

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seed food: Baked Salmon Fillet

{
  "type": "food_item",
  "foodItem": {
    "id": "seed-d-hist-salmon",
    "name": "Baked Salmon Fillet",
    "brand": null,
    "source": "manual",
    "servingLabel": "fillet",
    "servingQuantity": 1,
    "servingUnit": "fillet",
    "macrosPerServing": {
      "calories": 280,
      "proteinGrams": 34,
      "fatGrams": 14,
      "carbsGrams": 0
    },
    "aliases": [],
    "timesLogged": 0,
    "createdAt": "2026-07-16T12:00:00.000Z"
  }
}

Seed food history: 1 for seed-d-hist-salmon at 2026-07-18T12:30:00.000Z

{
  "type": "food_history",
  "foodItemId": "seed-d-hist-salmon",
  "quantity": 1,
  "loggedAt": "2026-07-18T12:30:00.000Z"
}

snapshot captured 2026-07-30T20:14:58.067Z

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 food"Same smoothie as yesterday." (difficulty —)0.2s

Verdict Expected LOG — should log the food. PASS: Logged (write-truth verified): Green Protein Smoothie, Green Protein Smoothie — card not captured.

Why verdict Logged (write-truth verified): Green Protein Smoothie, Green Protein Smoothie — 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 Codex Test Recipe Green Protein Smoothie. Using your recent Codex Test Recipe Green Protein Smoothie history. Tell me if that is wrong.

3 · App data rows written created food_log_entry: Green Protein Smoothie ×1 (smoothie) 260 cal · 24g P · 30g C · 5g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seed food: Codex Test Recipe Green Protein Smoothie

{
  "type": "food_item",
  "foodItem": {
    "id": "seed-d-smoothie",
    "name": "Green Protein Smoothie",
    "brand": "Codex Test Recipe",
    "source": "manual",
    "servingLabel": "smoothie",
    "servingQuantity": 1,
    "servingUnit": "smoothie",
    "macrosPerServing": {
      "calories": 260,
      "proteinGrams": 24,
      "fatGrams": 5,
      "carbsGrams": 30
    },
    "aliases": [],
    "timesLogged": 0,
    "createdAt": "2026-07-16T12:00:00.000Z"
  }
}

Seed food history: 1 for seed-d-smoothie at 2026-07-17T10:00:00.000Z

{
  "type": "food_history",
  "foodItemId": "seed-d-smoothie",
  "quantity": 1,
  "loggedAt": "2026-07-17T10:00:00.000Z"
}

snapshot captured 2026-07-30T20:15:09.418Z

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

7 · Lookup method The answer used provisional food evidence from user default.

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

FAILshould log the food"Log the tofu I had last time." (difficulty —)0.1s

Verdict Expected LOG — should log the food. 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 0.1s

1 · TTS said no speech captured

2 · Card shown I heard you want the same the tofu i had last time as before, but I do not have a matching saved log yet. Which exact food and amount should I log?

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seed food: Firm Tofu

{
  "type": "food_item",
  "foodItem": {
    "id": "seed-d-hist-tofu",
    "name": "Firm Tofu",
    "brand": null,
    "source": "manual",
    "servingLabel": "serving",
    "servingQuantity": 1,
    "servingUnit": "serving",
    "macrosPerServing": {
      "calories": 140,
      "proteinGrams": 15,
      "fatGrams": 8,
      "carbsGrams": 3
    },
    "aliases": [],
    "timesLogged": 0,
    "createdAt": "2026-07-16T12:00:00.000Z"
  }
}

Seed food history: 1 for seed-d-hist-tofu at 2026-07-16T18:00:00.000Z

{
  "type": "food_history",
  "foodItemId": "seed-d-hist-tofu",
  "quantity": 1,
  "loggedAt": "2026-07-16T18:00:00.000Z"
}

snapshot captured 2026-07-30T20:15:20.618Z

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 food"Same toast as earlier today." (difficulty —)0.2s

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

Why verdict Logged (write-truth verified): Sourdough Toast — 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 Sourdough Toast. Using your recent Sourdough Toast history. Tell me if that is wrong.

3 · App data rows written created food_log_entry: Sourdough Toast ×1 (slice) 90 cal · 3g P · 17g C · 1g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seed food: Sourdough Toast

{
  "type": "food_item",
  "foodItem": {
    "id": "seed-d-toast",
    "name": "Sourdough Toast",
    "brand": null,
    "source": "manual",
    "servingLabel": "slice",
    "servingQuantity": 1,
    "servingUnit": "slice",
    "macrosPerServing": {
      "calories": 90,
      "proteinGrams": 3,
      "fatGrams": 1,
      "carbsGrams": 17
    },
    "aliases": [],
    "timesLogged": 0,
    "createdAt": "2026-07-16T12:00:00.000Z"
  }
}

Seed food history: 2 for seed-d-toast at 2026-07-18T07:00:00.000Z

{
  "type": "food_history",
  "foodItemId": "seed-d-toast",
  "quantity": 2,
  "loggedAt": "2026-07-18T07:00:00.000Z"
}

snapshot captured 2026-07-30T20:15:32.084Z

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

7 · Lookup method The answer used provisional food evidence from user default.

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

FAILshould log the food"Snack was one chocolate Chip's Ahoy cookie pack mini." (difficulty —)2.7s

Verdict Expected LOG — should log the food. 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 2.7s

1 · TTS said no speech captured

2 · Card shown What exact food and amount should I use for one chocolate chips ahoy cookie pack mini? I did not log it yet because I could not safely finish that food log.

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-07-30T20:15:46.032Z

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)

FAILshould log the food"Finished one Fairlife Core Power vanilla shake." (difficulty —)0.0s

Verdict Expected LOG — should log the food. FAIL: WRITE-TRUTH FAIL — expected food write missing — local foodEntries delta is 0 for this turn (proven no food write, not a capture gap)

Why verdict WRITE-TRUTH FAIL — expected food write missing — local foodEntries delta is 0 for this turn (proven no food write, not a capture gap)

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

1 · TTS said no speech captured

2 · Card shown I could not find a to-do matching one Fairlife Core Power vanilla shake.

4 · UI did navigated to "todos" screen

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-07-30T20:15:57.200Z

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)

FAILshould log the food"Track one Chobani zero sugar strawberry cup." (difficulty —)0.9s

Verdict Expected LOG — should log the food. 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 0.9s

1 · TTS said no speech captured

2 · Card shown I couldn't find Track One Chobani Zero Sugar Strawberry Yogurt Cup in my nutrition database, so I haven't logged it — I'd only be guessing the nutrition. Say the exact name on the package, or tell me to log a generic yogurt.

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-07-30T20:16:09.252Z

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 food"Save one Quest cookies and cream protein bar." (difficulty —)0.5s

Verdict Expected LOG — should log the food. PASS: Logged (write-truth verified): Cookies & Cream Protein Bar — card not captured.

Why verdict Logged (write-truth verified): Cookies & Cream Protein 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 Cookies & Cream Protein Bar — Quest — the macros are an estimate since this food varies by brand.

3 · App data rows written created food_log_entry: Cookies & Cream Protein Bar ×1 (1 BAR) 200 cal · 21g P · 21g C · 8g 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-07-30T20:16:20.935Z

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

7 · Lookup method The answer used provisional food evidence from the USDA nutrition database.

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

PASSshould log the food"I ate one KIND peanut butter dark chocolate bar." (difficulty —)0.5s

Verdict Expected LOG — should log the food. PASS: Logged (write-truth verified): KIND Peanut Butter Dark Chocolate Bar — card not captured.

Why verdict Logged (write-truth verified): KIND Peanut Butter Dark Chocolate 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 I logged KIND Peanut Butter Dark Chocolate Bar — let me know if that's not right.

3 · App data rows written created food_log_entry: KIND Peanut Butter Dark Chocolate Bar ×1 (1 kind peanut butter dark chocolate bar) 200 cal · 7g P · 17g C · 14g 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-07-30T20:16:32.518Z

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 food"Log a medium orange and one RXBAR chocolate sea salt." (difficulty —)1.6s

Verdict Expected LOG — should log the food. 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 1.6s

1 · TTS said no speech captured

2 · Card shown I need to resolve one RXBAR chocolate sea salt before I log this meal. What should I use for one RXBAR chocolate sea salt?

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-07-30T20:16:45.385Z

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 food"I had steel cut oats and green tea." (difficulty —)0.5s

Verdict Expected LOG — should log the food. PASS: Logged (write-truth verified): Green tea, Steel Cut Oats — card not captured.

Why verdict Logged (write-truth verified): Green tea, Steel Cut Oats — 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 Steel Cut Oats and Green tea. Assumed catalog default servings where you did not say an amount — tell me if that is not right.

3 · App data rows written created food_log_entry: Steel Cut Oats ×1 (cup) 170 cal · 7g P · 29g C · 3g F
created food_log_entry: Green tea ×1 (240 g) 2 cal · 0g P · 0g C · 0g 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-07-30T20:16:57.067Z

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)

PASSshould log the food"Breakfast was scrambled eggs and a bagel." (difficulty —)0.2s

Verdict Expected LOG — should log the food. PASS: Logged (write-truth verified): Plain bagel, Egg — card not captured.

Why verdict Logged (write-truth verified): Plain bagel, 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 scrambled eggs and a bagel. assumed a fresh/deli-size bagel; say packaged or Lender's if it was a bread-aisle bagel Tell me if that is not right.

3 · App data rows written created food_log_entry: Egg ×1 (2 eggs) 143 cal · 12.6g P · 0.7g C · 9.5g F
created food_log_entry: Plain bagel ×1 (1 bagel) 350 cal · 14g P · 67.2g C · 2.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-07-30T20:17:08.382Z

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)

FAILshould log the food"Lunch was a tuna melt and an apple." (difficulty —)0.3s

Verdict Expected LOG — should log the food. FAIL: WRITE-TRUTH FAIL — IMPLAUSIBLE: 550 kcal is implausibly HIGH for 1 count of Tuna melt sandwich (typical 60-120 kcal [per-serving])

Why verdict WRITE-TRUTH FAIL — IMPLAUSIBLE: 550 kcal is implausibly HIGH for 1 count of Tuna melt sandwich (typical 60-120 kcal [per-serving])

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 Tuna melt sandwich and an apple. Assumed 1 apple as the default serving. Tell me if you want a different amount. Tell me if that is not right.

3 · App data rows written created food_log_entry: Tuna melt sandwich ×1 (1 tuna melt) 550 cal · 30.8g P · 44g C · 26.4g F
created food_log_entry: Apple ×1 (1 apple) 95 cal · 0.5g P · 25.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-07-30T20:17:19.834Z

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 food"Snack was cashews and a pear." (difficulty —)1.1s

Verdict Expected LOG — should log the food. PASS: Logged (write-truth verified): Pear, Cashews — card not captured.

Why verdict Logged (write-truth verified): Pear, Cashews — 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 1.1s

1 · TTS said no speech captured

2 · Card shown Logged Cashews (1 serving) and a pear. Assumed 1 pear as the default serving. Tell me if you want a different amount. Tell me if that is not right.

3 · App data rows written created food_log_entry: Cashews ×1 (ounce) 157 cal · 5g P · 9g C · 12g F
created food_log_entry: Pear ×1 (1 pear) 101 cal · 0.7g P · 27.1g C · 0.2g 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-07-30T20:17:32.050Z

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

7 · Lookup method The answer used provisional food evidence from user default.

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

PASSshould log the food"Dinner was cod and asparagus." (difficulty —)0.2s

Verdict Expected LOG — should log the food. PASS: Logged (write-truth verified): Asparagus, Cod — card not captured.

Why verdict Logged (write-truth verified): Asparagus, Cod — 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 Cod and Asparagus. Assumed catalog default servings where you did not say an amount — tell me if that is not right.

3 · App data rows written created food_log_entry: Cod ×1 (100 g) 105 cal · 23g P · 0g C · 0.9g F
created food_log_entry: Asparagus ×1 (100 g) 22 cal · 2.4g P · 4.1g C · 0.2g 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-07-30T20:17:43.367Z

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 food"I ate skyr and raspberries." (difficulty —)0.2s

Verdict Expected LOG — should log the food. PASS: Logged (write-truth verified): Raspberries, Raspberries, Skyr — card not captured.

Why verdict Logged (write-truth verified): Raspberries, Raspberries, Skyr — 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 Skyr and Raspberries. Assumed catalog default servings where you did not say an amount — tell me if that is not right.

3 · App data rows written created food_log_entry: Skyr ×1 (170 g) 107 cal · 18.7g P · 6.8g C · 0.3g F
created food_log_entry: Raspberries ×1 (1 oz) 15 cal · 0.3g P · 3.3g C · 0.2g 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-07-30T20:17:54.685Z

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 food"Track turkey and quinoa." (difficulty —)0.2s

Verdict Expected LOG — should log the food. PASS: Logged (write-truth verified): Cooked quinoa, Turkey breast — card not captured.

Why verdict Logged (write-truth verified): Cooked quinoa, Turkey 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 Turkey breast and Cooked quinoa. Assumed catalog default servings where you did not say an amount — tell me if that is not right.

3 · App data rows written created food_log_entry: Turkey breast ×1 (100 g) 135 cal · 29g P · 0g C · 1.7g F
created food_log_entry: Cooked quinoa ×1 (100 g) 120 cal · 4.4g P · 21.3g C · 1.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-07-30T20:18:21.583Z

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 food"Add ricotta and blackberries." (difficulty —)0.3s

Verdict Expected LOG — should log the food. PASS: Logged (write-truth verified): Blackberries, Ricotta cheese — card not captured.

Why verdict Logged (write-truth verified): Blackberries, Ricotta cheese — 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 Ricotta cheese and Blackberries. Assumed catalog default servings where you did not say an amount — tell me if that is not right.

3 · App data rows written created food_log_entry: Ricotta cheese ×1 (100 g) 148 cal · 9.6g P · 6g C · 9.5g F
created food_log_entry: Blackberries ×1 (100 g) 43 cal · 1.4g P · 10.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-07-30T20:18:33.035Z

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)

FAILshould log the food"I had a Kind bar and water." (difficulty —)0.7s

Verdict Expected LOG — should log the food. FAIL: WRITE-TRUTH FAIL — WRONG/MISSING item "a kind bar" — no saved row with matching identity (rows: Water, Cookies & Cream Protein Bar)

Why verdict WRITE-TRUTH FAIL — WRONG/MISSING item "a kind bar" — no saved row with matching identity (rows: Water, Cookies & Cream Protein Bar)

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

1 · TTS said no speech captured

2 · Card shown Logged QUEST Cookies & Cream Protein Bar and Water. Assumed catalog default servings where you did not say an amount — tell me if that is not right.

3 · App data rows written created food_log_entry: Cookies & Cream Protein Bar ×1 (1 BAR) 200 cal · 21g P · 21g C · 8g F
created food_log_entry: Water ×1 (240 g) 0 cal · 0g P · 0g C · 0g 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-07-30T20:18:44.884Z

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

7 · Lookup method The answer used provisional food evidence from user default.

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

PASSshould log the food"Log miso soup and edamame." (difficulty —)0.3s

Verdict Expected LOG — should log the food. PASS: Logged (write-truth verified): Miso soup, Edamame — card not captured.

Why verdict Logged (write-truth verified): Miso soup, Edamame — 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 Miso soup and Edamame. Assumed catalog default servings where you did not say an amount — tell me if that is not right.

3 · App data rows written created food_log_entry: Miso soup ×1 (100 g) 20 cal · 1.5g P · 2.7g C · 0.6g F
created food_log_entry: Edamame ×1 (100 g) 121 cal · 11.9g P · 8.9g C · 5.2g 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-07-30T20:18:56.284Z

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)

FAILshould log the food"Breakfast was granola, yogurt, and coffee." (difficulty —)5.8s

Verdict Expected LOG — should log the food. FAIL: Reported could-not-confirm (write-confirmation false negative).

Why verdict Reported could-not-confirm (write-confirmation false negative).

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

1 · TTS said no speech captured

2 · Card shown What would you like me to do with that?

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-07-30T20:19:13.234Z

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 food"I ate a pear, string cheese, and pretzels." (difficulty —)0.3s

Verdict Expected LOG — should log the food. PASS: Logged (write-truth verified): Pear, Pretzels, Pretzels, Mozzarella string cheese, Pear — card not captured.

Why verdict Logged (write-truth verified): Pear, Pretzels, Pretzels, Mozzarella string cheese, Pear — 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 a pear, Mozzarella string cheese, and Pretzels. Assumed catalog default servings where you did not say an amount — tell me if that is not right.

3 · App data rows written created food_log_entry: Pear ×1 (1 pear) 101 cal · 0.7g P · 27.1g C · 0.2g F
created food_log_entry: Mozzarella string cheese ×1 (28 g) 80 cal · 7g P · 1g C · 5g F
created food_log_entry: Pretzels ×1 (28 g) 106 cal · 2.5g P · 22.1g C · 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-07-30T20:19:24.733Z

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 food"Dinner was pork, farro, and Brussels sprouts." (difficulty —)0.2s

Verdict Expected LOG — should log the food. PASS: Logged (write-truth verified): Brussels sprouts, Pork, Cooked farro — card not captured.

Why verdict Logged (write-truth verified): Brussels sprouts, Pork, Cooked farro — 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 Pork, Cooked farro, and Brussels sprouts. Assumed catalog default servings where you did not say an amount — tell me if that is not right.

3 · App data rows written created food_log_entry: Pork ×1 (85 g) 145 cal · 23.8g P · 0g C · 5g F
created food_log_entry: Cooked farro ×1 (100 g) 123 cal · 4.4g P · 26g C · 0.8g F
created food_log_entry: Brussels sprouts ×1 (155 g) 70 cal · 5.4g P · 14.4g 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-07-30T20:19:36.101Z

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 food"Snack was snap peas and hummus." (difficulty —)0.2s

Verdict Expected LOG — should log the food. PASS: Logged (write-truth verified): Snap peas, Hummus — card not captured.

Why verdict Logged (write-truth verified): Snap peas, Hummus — 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 Snap peas and Hummus. Assumed catalog default servings where you did not say an amount — tell me if that is not right.

3 · App data rows written created food_log_entry: Snap peas ×1 (98 g) 41 cal · 2.7g P · 7.4g C · 0.2g F
created food_log_entry: Hummus ×1 (100 g) 166 cal · 7.9g P · 14.3g C · 9.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-07-30T20:19:47.435Z

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 food"Lunch was a grain bowl and iced tea." (difficulty —)1.2s

Verdict Expected LOG — should log the food. PASS: Logged (write-truth verified): Grain Bowl, Unsweetened iced tea — card not captured.

Why verdict Logged (write-truth verified): Grain Bowl, Unsweetened iced tea — 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 1.2s

1 · TTS said no speech captured

2 · Card shown Logged Grain Bowl (serving) and Unsweetened iced tea. Assumed catalog default servings where you did not say an amount — tell me if that is not right.

3 · App data rows written created food_log_entry: Grain Bowl ×1 (serving) 313 cal · 8.1g P · 55.7g C · 6.7g F
created food_log_entry: Unsweetened iced tea ×1 (240 g) 2 cal · 0g P · 0g C · 0g 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-07-30T20:19:59.766Z

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)

PASSshould log the food"I had rice, lentils, and tofu." (difficulty —)0.3s

Verdict Expected LOG — should log the food. PASS: Logged (write-truth verified): Lentils, Firm tofu, Cooked white rice — card not captured.

Why verdict Logged (write-truth verified): Lentils, Firm tofu, 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.3s

1 · TTS said no speech captured

2 · Card shown Logged Cooked white rice, Lentils, and Firm tofu. Assumed catalog default servings where you did not say an amount — tell me if that is not right.

3 · App data rows written created food_log_entry: Cooked white rice ×1 (100 g) 130 cal · 2.7g P · 28g C · 0.3g F
created food_log_entry: Lentils ×1 (100 g) 116 cal · 9g P · 20.1g C · 0.4g F
created food_log_entry: Firm tofu ×1 (100 g) 144 cal · 17g P · 2.8g C · 8.7g 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-07-30T20:20:11.151Z

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 food"Track skyr, honey, and walnuts." (difficulty —)0.4s

Verdict Expected LOG — should log the food. PASS: Logged (write-truth verified): Skyr, Honey, Walnuts — card not captured.

Why verdict Logged (write-truth verified): Skyr, Honey, Walnuts — 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 Skyr, Honey, and Walnuts. Assumed catalog default servings where you did not say an amount — tell me if that is not right.

3 · App data rows written created food_log_entry: Skyr ×1 (170 g) 107 cal · 18.7g P · 6.8g C · 0.3g F
created food_log_entry: Honey ×1 (21 g) 64 cal · 0.1g P · 17.3g C · 0g F
created food_log_entry: Walnuts ×1 (28 g) 183 cal · 4.3g P · 3.8g C · 18.3g 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-07-30T20:20:22.617Z

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 food"Add eggs, Canadian bacon, and grapefruit juice." (difficulty —)0.4s

Verdict Expected LOG — should log the food. PASS: Logged (write-truth verified): Canadian bacon, Grapefruit juice, Egg — card not captured.

Why verdict Logged (write-truth verified): Canadian bacon, Grapefruit juice, 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 eggs, Canadian bacon, and Grapefruit juice. Assumed catalog default servings where you did not say an amount — tell me if that is not right.

3 · App data rows written created food_log_entry: Egg ×1 (2 eggs) 143 cal · 12.6g P · 0.7g C · 9.5g F
created food_log_entry: Canadian bacon ×1 (46 g) 67 cal · 13g P · 0.8g C · 1.3g F
created food_log_entry: Grapefruit juice ×1 (247 g) 96 cal · 1.2g P · 22.7g C · 0.2g 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-07-30T20:20:34.168Z

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)

FAILshould log the food"I ate noodles and a side of spinach." (difficulty —)0.7s

Verdict Expected LOG — should log the food. FAIL: WRITE-TRUTH FAIL — WRONG/MISSING item "noodles" — no saved row with matching identity (rows: Cooked pasta, Spinach, Cooked pasta, Spinach)

Why verdict WRITE-TRUTH FAIL — WRONG/MISSING item "noodles" — no saved row with matching identity (rows: Cooked pasta, Spinach, Cooked pasta, Spinach)

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

1 · TTS said no speech captured

2 · Card shown Logged Cooked pasta and Spinach. Assumed catalog default servings where you did not say an amount — tell me if that is not right.

3 · App data rows written created food_log_entry: Cooked pasta ×1 (140 g) 220 cal · 8.1g P · 43.3g C · 1.3g F
created food_log_entry: Spinach ×1 (30 g) 7 cal · 0.9g P · 1.1g C · 0.1g F
created food_log_entry: Cooked pasta ×1 (140 g) 220 cal · 8.1g P · 43.3g C · 1.3g F
created food_log_entry: Spinach ×1 (30 g) 7 cal · 0.9g P · 1.1g C · 0.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-07-30T20:20:46.066Z

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 food"Log a nectarine and almond butter." (difficulty —)0.3s

Verdict Expected LOG — should log the food. PASS: Logged (write-truth verified): Nectarine, Almond butter — card not captured.

Why verdict Logged (write-truth verified): Nectarine, Almond 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.3s

1 · TTS said no speech captured

2 · Card shown Logged a nectarine and Almond butter. Assumed catalog default servings where you did not say an amount — tell me if that is not right.

3 · App data rows written created food_log_entry: Nectarine ×1 (1 nectarine) 62 cal · 1.5g P · 14.8g C · 0.4g F
created food_log_entry: Almond butter ×1 (32 g) 196 cal · 6.7g P · 6.1g C · 17.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-07-30T20:20:57.485Z

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)

FAILshould log the food"Breakfast was cereal and oat milk." (difficulty —)5.1s

Verdict Expected LOG — should log the food. FAIL: Reported could-not-confirm (write-confirmation false negative).

Why verdict Reported could-not-confirm (write-confirmation false negative).

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

1 · TTS said no speech captured

2 · Card shown I could not finish that request safely.

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-07-30T20:22:59.449Z

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)

FAILshould log the food"I had a frittata with four eggs, spinach, and feta" (difficulty —)4.1s

Verdict Expected LOG — should log the food. 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 4.1s

1 · TTS said no speech captured

2 · Card shown Which feta should I use?

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-07-30T20:23:14.683Z

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 food"Log a smoothie with spinach, banana, and whey protein." (difficulty —)0.7s

Verdict Expected LOG — should log the food. PASS: Logged (write-truth verified): Smoothie, Clear whey protein (MyProtein Clear Whey Isolate), Spinach, Banana — card not captured.

Why verdict Logged (write-truth verified): Smoothie, Clear whey protein (MyProtein Clear Whey Isolate), Spinach, 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.7s

1 · TTS said no speech captured

2 · Card shown Logged Smoothie. Includes spinach, one banana, and Clear whey protein (MyProtein Clear Whey Isolate).

3 · App data rows written created food_log_entry: Smoothie ×1 (serving) 202 cal · 22.2g P · 29.2g C · 0.5g F
created food_log_entry: Spinach ×1 (30 g) 7 cal · 0.9g P · 1.1g C · 0.1g F
created food_log_entry: Banana ×1 (1 banana) 105 cal · 1.3g P · 27.1g C · 0.4g F
created food_log_entry: Clear whey protein (MyProtein Clear Whey Isolate) ×1 (scoop) 90 cal · 20g P · 1g C · 0g 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-07-30T20:23:26.551Z

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 food"I had a grain bowl with quinoa, chickpeas, and tahini." (difficulty —)3.5s

Verdict Expected LOG — should log the food. 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 3.5s

1 · TTS said no speech captured

2 · Card shown What should I use for chickpeas?

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-07-30T20:23:41.184Z

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)

FAILshould log the food"Breakfast was avocado toast with egg and chili flakes." (difficulty —)0.6s

Verdict Expected LOG — should log the food. 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 0.6s

1 · TTS said no speech captured

2 · Card shown What exact ingredient should I use for chili flakes?

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-07-30T20:23:52.934Z

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)

FAILshould log the food"I made stir fry with tofu, peppers, broccoli, and oil." (difficulty —)1.9s

Verdict Expected LOG — should log the food. 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 1.9s

1 · TTS said no speech captured

2 · Card shown I did not make any app changes. What would you like me to do with that?

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-07-30T20:24:05.967Z

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)

FAILshould log the food"Dinner was a poke bowl with rice, tuna, avocado, and seaweed." (difficulty —)1.0s

Verdict Expected LOG — should log the food. 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 1.0s

1 · TTS said no speech captured

2 · Card shown Which rice should I use?

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-07-30T20:24:30.634Z

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 food"I had pho with beef and basil." (difficulty —)1.9s

Verdict Expected LOG — should log the food. PASS: Logged (write-truth verified): Beef, Pho, Basil, Raw — card not captured.

Why verdict Logged (write-truth verified): Beef, Pho, Basil, Raw — 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 1.9s

1 · TTS said no speech captured

2 · Card shown Logged Pho. Includes Beef and Basil, Raw.

3 · App data rows written created food_log_entry: Pho ×1 (serving) 219 cal · 22.9g P · 0.6g C · 12.9g F
created food_log_entry: Beef ×1 (85 g) 213 cal · 22.1g P · 0g C · 12.8g F
created food_log_entry: Basil, Raw ×1 (1 cup) 6 cal · 0.8g P · 0.6g C · 0.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-07-30T20:24:43.669Z

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)

PASSshould log the food"Log a chicken wrap with hummus and cucumber." (difficulty —)0.6s

Verdict Expected LOG — should log the food. PASS: Logged (write-truth verified): Hummus, Cucumber, Chicken Wrap — card not captured.

Why verdict Logged (write-truth verified): Hummus, Cucumber, Chicken Wrap — 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.6s

1 · TTS said no speech captured

2 · Card shown Logged Chicken Wrap. Includes hummus and Cucumber.

3 · App data rows written created food_log_entry: Chicken Wrap ×1 (serving) 181 cal · 8.6g P · 17.9g C · 9.7g F
created food_log_entry: Hummus ×1 (100 g) 166 cal · 7.9g P · 14.3g C · 9.6g F
created food_log_entry: Cucumber ×1 (100 g) 15 cal · 0.7g P · 3.6g C · 0.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-07-30T20:24:55.386Z

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 food"I built an acai bowl with granola, banana, and coconut." (difficulty —)3.0s

Verdict Expected LOG — should log the food. 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 3.0s

1 · TTS said no speech captured

2 · Card shown What should I use for coconut?

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-07-30T20:25:09.586Z

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)

FAILshould log the food"Dinner was butter chicken with rice, naan, and cucumber salad." (difficulty —)0.7s

Verdict Expected LOG — should log the food. 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 0.7s

1 · TTS said no speech captured

2 · Card shown What exact ingredient should I use for butter chicken with rice naan?

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-07-30T20:25:21.418Z

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 ask a clarifying question"Add some porridge." (difficulty —)2.7s

Verdict Expected CLARIFY — should ask a clarifying question. PASS: Asked a clarification as expected.

Why verdict Asked a clarification as expected.

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

1 · TTS said no speech captured

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

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-07-30T20:25:35.202Z

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 ask a clarifying question"I had muesli." (difficulty —)0.9s

Verdict Expected CLARIFY — should ask a clarifying question. PASS: Asked a clarification as expected.

Why verdict Asked a clarification as expected.

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

1 · TTS said no speech captured

2 · Card shown What food did you log? Could you be more specific?

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-07-30T20:25:47.318Z

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 ask a clarifying question"Log couscous for dinner." (difficulty —)1.9s

Verdict Expected CLARIFY — should ask a clarifying question. PASS: Asked a clarification as expected.

Why verdict Asked a clarification as expected.

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

1 · TTS said no speech captured

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

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-07-30T20:26:00.351Z

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 ask a clarifying question"Track noodles." (difficulty —)2.6s

Verdict Expected CLARIFY — should ask a clarifying question. PASS: Asked a clarification as expected.

Why verdict Asked a clarification as expected.

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

1 · TTS said no speech captured

2 · Card shown What food did you log? Could you be more specific?

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-07-30T20:26:14.100Z

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 ask a clarifying question"I ate pretzels." (difficulty —)0.1s

Verdict Expected CLARIFY — should ask a clarifying question. PASS: Asked a clarification as expected.

Why verdict Asked a clarification as expected.

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

1 · TTS said no speech captured

2 · Card shown How much should I log for Pretzels? I did not log it yet because the amount was not clear.

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-07-30T20:26:25.318Z

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 ask a clarifying question"Add walnuts." (difficulty —)0.1s

Verdict Expected CLARIFY — should ask a clarifying question. PASS: Decisive guess with stated assumption + invited correction (good-guessing).

Why verdict Decisive guess with stated assumption + invited correction (good-guessing).

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

1 · TTS said no speech captured

2 · Card shown Logged walnuts. Assumed about 28 g as a typical serving because no amount was stated.

3 · App data rows written created food_log_entry: Walnuts ×1 (28 g) 183 cal · 4.3g P · 3.8g C · 18.3g 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-07-30T20:26:36.568Z

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 ask a clarifying question"Log a bowl of chili." (difficulty —)2.7s

Verdict Expected CLARIFY — should ask a clarifying question. PASS: Asked a clarification as expected.

Why verdict Asked a clarification as expected.

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

1 · TTS said no speech captured

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

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-07-30T20:26:50.386Z

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 ask a clarifying question"I had a plate of risotto." (difficulty —)2.7s

Verdict Expected CLARIFY — should ask a clarifying question. PASS: Asked a clarification as expected.

Why verdict Asked a clarification as expected.

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

1 · TTS said no speech captured

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

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-07-30T20:27:04.235Z

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 ask a clarifying question"Track lemonade." (difficulty —)1.5s

Verdict Expected CLARIFY — should ask a clarifying question. PASS: Asked a clarification as expected.

Why verdict Asked a clarification as expected.

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

1 · TTS said no speech captured

2 · Card shown What food did you log? Could you be more specific?

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-07-30T20:27:16.852Z

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 ask a clarifying question"Add tea." (difficulty —)0.5s

Verdict Expected CLARIFY — should ask a clarifying question. PASS: Asked a clarification as expected.

Why verdict Asked a clarification as expected.

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 What food did you log? Could you be more specific?

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-07-30T20:27:28.451Z

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 ask a clarifying question"I drank beer." (difficulty —)0.9s

Verdict Expected CLARIFY — should ask a clarifying question. PASS: Asked a clarification as expected.

Why verdict Asked a clarification as expected.

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

1 · TTS said no speech captured

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

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-07-30T20:27:40.635Z

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)

FAILshould ask a clarifying question"Log gelato." (difficulty —)0.1s

Verdict Expected CLARIFY — should ask a clarifying question. FAIL: Logged a BLIND guess — no stated assumption, no correction invited.

Why verdict Logged a BLIND guess — no stated assumption, no correction invited.

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

1 · TTS said no speech captured

2 · Card shown Logged gelato — the macros are an estimate since this food varies by brand.

3 · App data rows written created food_log_entry: gelato ×1 (serving) 200 cal · 5g P · 20g C · 10g 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-07-30T20:27:51.918Z

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

7 · Lookup method The answer used provisional food evidence from user default.

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

PASSshould ask a clarifying question"Had some mixed nuts." (difficulty —)0.1s

Verdict Expected CLARIFY — should ask a clarifying question. PASS: Asked a clarification as expected.

Why verdict Asked a clarification as expected.

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

1 · TTS said no speech captured

2 · Card shown How much should I log for Mixed nuts? I did not log it yet because the amount was not clear.

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-07-30T20:28:03.152Z

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 ask a clarifying question"Add kettle corn." (difficulty —)4.5s

Verdict Expected CLARIFY — should ask a clarifying question. PASS: Asked a clarification as expected.

Why verdict Asked a clarification as expected.

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

1 · TTS said no speech captured

2 · Card shown What food did you log? Could you be more specific?

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-07-30T20:28:18.851Z

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)

FAILshould ask a clarifying question"I had an energy bar." (difficulty —)0.3s

Verdict Expected CLARIFY — should ask a clarifying question. FAIL: WRONG item vs seeded default/key — WRONG/MISSING item "energy bar" — no saved row with matching identity (rows: Generic protein bar, Generic protein bar)

Why verdict WRONG item vs seeded default/key — WRONG/MISSING item "energy bar" — no saved row with matching identity (rows: Generic protein bar, Generic protein bar)

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 an energy bar. Assumed 1 energy bar as the default serving. Tell me if you want a different amount.

3 · App data rows written created food_log_entry: Generic protein bar ×1 (1 energy bar) 200 cal · 20g P · 22g C · 7g F
created food_log_entry: Generic protein bar ×1 (1 energy bar) 200 cal · 20g P · 22g C · 7g 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-07-30T20:28:30.268Z

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 ask a clarifying question"Log a dairy cup." (difficulty —)1.1s

Verdict Expected CLARIFY — should ask a clarifying question. PASS: Decisive guess with stated assumption + invited correction (good-guessing).

Why verdict Decisive guess with stated assumption + invited correction (good-guessing).

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

1 · TTS said no speech captured

2 · Card shown I logged Vanilla Greek Yogurt Cup — Codex Test Dairy — let me know if that's not right.

3 · App data rows written created food_log_entry: Vanilla Greek Yogurt Cup ×1 (cup) 130 cal · 15g P · 12g C · 0g 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-07-30T20:28:57.883Z

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

7 · Lookup method The answer used provisional food evidence from user default.

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

PASSshould ask a clarifying question"Track a milk alternative." (difficulty —)5.2s

Verdict Expected CLARIFY — should ask a clarifying question. PASS: Asked a clarification as expected.

Why verdict Asked a clarification as expected.

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

1 · TTS said no speech captured

2 · Card shown What fat level or type of milk should I use? I did not log it yet because milk fat level can change the nutrition.

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-07-30T20:29:14.268Z

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 ask a clarifying question"I ate a deli sandwich." (difficulty —)2.7s

Verdict Expected CLARIFY — should ask a clarifying question. PASS: Asked a clarification as expected.

Why verdict Asked a clarification as expected.

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

1 · TTS said no speech captured

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

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-07-30T20:29:28.084Z

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)

FAILshould ask a clarifying question"Add a protein shake." (difficulty —)3.9s

Verdict Expected CLARIFY — should ask a clarifying question. FAIL: Logged a BLIND guess — no stated assumption, no correction invited.

Why verdict Logged a BLIND guess — no stated assumption, no correction invited.

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

1 · TTS said no speech captured

2 · Card shown I couldn't find Add A Protein Protein Shake in my nutrition database, so I haven't logged it — I'd only be guessing the nutrition. Say the exact name on the package, or tell me to log a generic protein shake.

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-07-30T20:29:43.200Z

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 ask a clarifying question"I had a latte." (difficulty —)0.9s

Verdict Expected CLARIFY — should ask a clarifying question. PASS: Decisive guess with stated assumption + invited correction (good-guessing).

Why verdict Decisive guess with stated assumption + invited correction (good-guessing).

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

1 · TTS said no speech captured

2 · Card shown I logged latte — let me know if that's not right.

3 · App data rows written created food_log_entry: latte ×1 (serving) 150 cal · 10g P · 15g C · 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-07-30T20:29:55.202Z

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

7 · Lookup method The answer used provisional food evidence from user default.

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

PASSshould ask a clarifying question"Log a roll." (difficulty —)1.6s

Verdict Expected CLARIFY — should ask a clarifying question. PASS: Asked a clarification as expected.

Why verdict Asked a clarification as expected.

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

1 · TTS said no speech captured

2 · Card shown What food did you log? Could you be more specific?

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-07-30T20:30:07.967Z

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 ask a clarifying question"Track a veggie burger." (difficulty —)2.7s

Verdict Expected CLARIFY — should ask a clarifying question. PASS: Asked a clarification as expected.

Why verdict Asked a clarification as expected.

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

1 · TTS said no speech captured

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

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-07-30T20:30:21.786Z

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 ask a clarifying question"I had flatbread pizza." (difficulty —)4.1s

Verdict Expected CLARIFY — should ask a clarifying question. PASS: Asked a clarification as expected.

Why verdict Asked a clarification as expected.

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

1 · TTS said no speech captured

2 · Card shown What food did you log? Could you be more specific?

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-07-30T20:30:37.036Z

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 ask a clarifying question"Add a scone." (difficulty —)2.7s

Verdict Expected CLARIFY — should ask a clarifying question. PASS: Asked a clarification as expected.

Why verdict Asked a clarification as expected.

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

1 · TTS said no speech captured

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

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-07-30T20:30:50.919Z

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 ask a clarifying question"Log my usual latte size." (difficulty —)2.0s

Verdict Expected CLARIFY — should ask a clarifying question. PASS: Asked a clarification as expected.

Why verdict Asked a clarification as expected.

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

1 · TTS said no speech captured

2 · Card shown I found a likely match for i had the usual breakfast size, but I still need a clearer amount or product detail before I can log it. What exact food and amount should I use? I did not log it yet.

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seed food: latte

{
  "type": "food_item",
  "foodItem": {
    "id": "seed-d-latte-confirm",
    "name": "latte",
    "brand": null,
    "source": "manual",
    "servingLabel": "serving",
    "servingQuantity": 1,
    "servingUnit": "serving",
    "macrosPerServing": {
      "calories": 150,
      "proteinGrams": 10,
      "fatGrams": 5,
      "carbsGrams": 15
    },
    "aliases": [],
    "timesLogged": 0,
    "createdAt": "2026-07-16T12:00:00.000Z"
  }
}

food_default

{
  "type": "food_default",
  "phrase": "log my usual latte size",
  "foodItemId": "seed-d-latte-confirm",
  "settings": {
    "quickLogMode": "fixed",
    "defaultQuantity": 1,
    "defaultServingLabel": "serving",
    "displayLabel": "log my usual latte size",
    "confirmBeforeLog": false
  }
}

snapshot captured 2026-07-30T20:31:04.101Z

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 ask a clarifying question"Add the regular dinner portion." (difficulty —)0.1s

Verdict Expected CLARIFY — should ask a clarifying question. PASS: Decisive guess with stated assumption + invited correction (good-guessing).

Why verdict Decisive guess with stated assumption + invited correction (good-guessing).

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

1 · TTS said no speech captured

2 · Card shown Logged dinner portion. Using your saved "add the regular dinner portion". Tell me if that is wrong.

3 · App data rows written created food_log_entry: dinner portion ×1 (serving) 150 cal · 10g P · 15g C · 5g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seed food: dinner portion

{
  "type": "food_item",
  "foodItem": {
    "id": "seed-d-dinner-portion",
    "name": "dinner portion",
    "brand": null,
    "source": "manual",
    "servingLabel": "serving",
    "servingQuantity": 1,
    "servingUnit": "serving",
    "macrosPerServing": {
      "calories": 150,
      "proteinGrams": 10,
      "fatGrams": 5,
      "carbsGrams": 15
    },
    "aliases": [],
    "timesLogged": 0,
    "createdAt": "2026-07-16T12:00:00.000Z"
  }
}

food_default

{
  "type": "food_default",
  "phrase": "add the regular dinner portion",
  "foodItemId": "seed-d-dinner-portion",
  "settings": {
    "quickLogMode": "fixed",
    "defaultQuantity": 1,
    "defaultServingLabel": "serving",
    "displayLabel": "add the regular dinner portion",
    "confirmBeforeLog": false
  }
}

snapshot captured 2026-07-30T20:31:15.284Z

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

7 · Lookup method The answer used provisional food evidence from user default.

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

PASSshould ask a clarifying question"Track my default afternoon snack." (difficulty —)0.1s

Verdict Expected CLARIFY — should ask a clarifying question. PASS: Decisive guess with stated assumption + invited correction (good-guessing).

Why verdict Decisive guess with stated assumption + invited correction (good-guessing).

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

1 · TTS said no speech captured

2 · Card shown Logged snack. Using your saved "track my default afternoon snack". Tell me if that is wrong.

3 · App data rows written created food_log_entry: snack ×1 (serving) 150 cal · 10g P · 15g C · 5g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seed food: snack

{
  "type": "food_item",
  "foodItem": {
    "id": "seed-d-snack-amt",
    "name": "snack",
    "brand": null,
    "source": "manual",
    "servingLabel": "serving",
    "servingQuantity": 1,
    "servingUnit": "serving",
    "macrosPerServing": {
      "calories": 150,
      "proteinGrams": 10,
      "fatGrams": 5,
      "carbsGrams": 15
    },
    "aliases": [],
    "timesLogged": 0,
    "createdAt": "2026-07-16T12:00:00.000Z"
  }
}

food_default

{
  "type": "food_default",
  "phrase": "track my default afternoon snack",
  "foodItemId": "seed-d-snack-amt",
  "settings": {
    "quickLogMode": "fixed",
    "defaultQuantity": 1,
    "defaultServingLabel": "serving",
    "displayLabel": "track my default afternoon snack",
    "confirmBeforeLog": false
  }
}

snapshot captured 2026-07-30T20:31:26.517Z

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

7 · Lookup method The answer used provisional food evidence from user default.

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

PASSshould ask a clarifying question"I had the usual breakfast size." (difficulty —)0.1s

Verdict Expected CLARIFY — should ask a clarifying question. PASS: Decisive guess with stated assumption + invited correction (good-guessing).

Why verdict Decisive guess with stated assumption + invited correction (good-guessing).

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

1 · TTS said no speech captured

2 · Card shown Logged breakfast. Using your saved "i had the usual breakfast size". Tell me if that is wrong.

3 · App data rows written created food_log_entry: breakfast ×1 (serving) 150 cal · 10g P · 15g C · 5g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seed food: breakfast

{
  "type": "food_item",
  "foodItem": {
    "id": "seed-d-bfast-size",
    "name": "breakfast",
    "brand": null,
    "source": "manual",
    "servingLabel": "serving",
    "servingQuantity": 1,
    "servingUnit": "serving",
    "macrosPerServing": {
      "calories": 150,
      "proteinGrams": 10,
      "fatGrams": 5,
      "carbsGrams": 15
    },
    "aliases": [],
    "timesLogged": 0,
    "createdAt": "2026-07-16T12:00:00.000Z"
  }
}

food_default

{
  "type": "food_default",
  "phrase": "i had the usual breakfast size",
  "foodItemId": "seed-d-bfast-size",
  "settings": {
    "quickLogMode": "fixed",
    "defaultQuantity": 1,
    "defaultServingLabel": "serving",
    "displayLabel": "i had the usual breakfast size",
    "confirmBeforeLog": false
  }
}

snapshot captured 2026-07-30T20:31:37.735Z

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

7 · Lookup method The answer used provisional food evidence from user default.

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

UNVERIFIEDunclassifiedshould complete the pending action"Three quarters of a cup." (difficulty —)1.7s

Verdict Expected CLARIFY_ANSWER — should complete the pending action. UNVERIFIED: CLARIFY_ANSWER not gradeable single-shot — no pending clarification in this replay (app re-asked / mis-parsed as fresh); needs multi-turn replay.

Why verdict CLARIFY_ANSWER not gradeable single-shot — no pending clarification in this replay (app re-asked / mis-parsed as fresh); needs multi-turn replay.

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

1 · TTS said no speech captured

2 · Card shown Which one did you mean? 1. three quarters cup ricotta, 2. the cheesecake factory cup of butternut squash soup

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-07-30T20:31:50.517Z

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 complete the pending action"One and a half cups, plain." (difficulty —)1.3s

Verdict Expected CLARIFY_ANSWER — should complete the pending action. PASS: Completed the pending action.

Why verdict Completed the pending action.

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

1 · TTS said no speech captured

2 · Card shown I couldn't find A Half Half Packaged Food in my nutrition database, so I haven't logged it — I'd only be guessing the nutrition. Say the exact name on the package, or tell me to log a generic packaged food.

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-07-30T20:32:02.936Z

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)

UNVERIFIEDunclassifiedshould complete the pending action"The RXBAR blueberry." (difficulty —)1.1s

Why verdict CLARIFY_ANSWER not gradeable single-shot — no pending clarification in this replay (app re-asked / mis-parsed as fresh); needs multi-turn replay.

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

1 · TTS said no speech captured

2 · Card shown I found a likely match for rxbar rxbar blueberry, but I still need a clearer amount or product detail before I can log it. What exact food and amount should I use? I did not log it yet.

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-07-30T20:32:15.202Z

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 complete the pending action"Oat milk." (difficulty —)2.2s

Verdict Expected CLARIFY_ANSWER — should complete the pending action. PASS: Completed the pending action.

Why verdict Completed the pending action.

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

1 · TTS said no speech captured

2 · Card shown I logged Oat Milk (1 serving) — let me know if that's not right.

3 · App data rows written created food_log_entry: Oat Milk ×1 (250 milliliters) 114 cal · 1.8g P · 13.7g C · 5.8g 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-07-30T20:32:28.551Z

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)

UNVERIFIEDunclassifiedshould complete the pending action"No, that's not it — the unsweetened one." (difficulty —)5.1s

Why verdict CLARIFY_ANSWER not gradeable single-shot — no pending clarification in this replay (app re-asked / mis-parsed as fresh); needs multi-turn replay.

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

1 · TTS said no speech captured

2 · Card shown I found a likely match for unsweetened oat milk, but I still need a clearer amount or product detail before I can log it. What exact food and amount should I use? I did not log it yet.

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-07-30T20:32:44.852Z

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)

UNVERIFIEDunclassifiedshould complete the pending action"Wrong one. The vanilla, not chocolate." (difficulty —)1.5s

Why verdict CLARIFY_ANSWER not gradeable single-shot — no pending clarification in this replay (app re-asked / mis-parsed as fresh); needs multi-turn replay.

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

1 · TTS said no speech captured

2 · Card shown What would you like me to do with that?

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-07-30T20:32:57.467Z

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)

FAILshould complete the pending action"No, not the flavored skyr." (difficulty —)0.1s

Verdict Expected CLARIFY_ANSWER — should complete the pending action. FAIL: Reported could-not-confirm (write-confirmation false negative).

Why verdict Reported could-not-confirm (write-confirmation false negative).

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

1 · TTS said no speech captured

2 · Card shown I could not confirm that the change was saved, so I did not mark it as done.

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-07-30T20:33:08.685Z

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 decline"Cancel that entry." (difficulty —)0.0s

Verdict Expected DECLINE — should decline. PASS: Declined / no unwanted write.

Why verdict Declined / no unwanted write.

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

1 · TTS said no speech captured

2 · Card shown Should I add that as a to-do?

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seed food: Pending Food Item

{
  "type": "food_item",
  "foodItem": {
    "id": "seed-d-corr-pending-3",
    "name": "Pending Food Item",
    "brand": null,
    "source": "manual",
    "servingLabel": "serving",
    "servingQuantity": 1,
    "servingUnit": "serving",
    "macrosPerServing": {
      "calories": 150,
      "proteinGrams": 10,
      "fatGrams": 5,
      "carbsGrams": 15
    },
    "aliases": [],
    "timesLogged": 0,
    "createdAt": "2026-07-16T12:00:00.000Z"
  }
}

Seed food history: 1 for seed-d-corr-pending-3 at 2026-07-18T11:00:00.000Z

{
  "type": "food_history",
  "foodItemId": "seed-d-corr-pending-3",
  "quantity": 1,
  "loggedAt": "2026-07-18T11:00:00.000Z"
}

snapshot captured 2026-07-30T20:33:35.069Z

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 decline"Never mind, remove that." (difficulty —)1.8s

Verdict Expected DECLINE — should decline. PASS: Declined / no unwanted write.

Why verdict Declined / no unwanted write.

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

1 · TTS said no speech captured

2 · Card shown Understood. I won’t add that as a to-do. Let me know if you’d like to log something else.

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seed food: Pending Food Item

{
  "type": "food_item",
  "foodItem": {
    "id": "seed-d-corr-pending-4",
    "name": "Pending Food Item",
    "brand": null,
    "source": "manual",
    "servingLabel": "serving",
    "servingQuantity": 1,
    "servingUnit": "serving",
    "macrosPerServing": {
      "calories": 150,
      "proteinGrams": 10,
      "fatGrams": 5,
      "carbsGrams": 15
    },
    "aliases": [],
    "timesLogged": 0,
    "createdAt": "2026-07-16T12:00:00.000Z"
  }
}

Seed food history: 1 for seed-d-corr-pending-4 at 2026-07-18T11:00:00.000Z

{
  "type": "food_history",
  "foodItemId": "seed-d-corr-pending-4",
  "quantity": 1,
  "loggedAt": "2026-07-18T11:00:00.000Z"
}

snapshot captured 2026-07-30T20:33:48.002Z

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)

FAILshould complete the pending action"No, that's not the bar I meant." (difficulty —)0.1s

Verdict Expected CLARIFY_ANSWER — should complete the pending action. FAIL: Reported could-not-confirm (write-confirmation false negative).

Why verdict Reported could-not-confirm (write-confirmation false negative).

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

1 · TTS said no speech captured

2 · Card shown I could not confirm that the change was saved, so I did not mark it as done.

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-07-30T20:33:59.201Z

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)

UNVERIFIEDunclassifiedshould complete the pending action"Not the medium — the large pear." (difficulty —)5.3s

Why verdict CLARIFY_ANSWER not gradeable single-shot — no pending clarification in this replay (app re-asked / mis-parsed as fresh); needs multi-turn replay.

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

1 · TTS said no speech captured

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

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-07-30T20:34:15.653Z

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)

UNVERIFIEDunclassifiedshould complete the pending action"Wrong item. Pick the baked cod." (difficulty —)2.9s

Why verdict CLARIFY_ANSWER not gradeable single-shot — no pending clarification in this replay (app re-asked / mis-parsed as fresh); needs multi-turn replay.

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

1 · TTS said no speech captured

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

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-07-30T20:34:29.734Z

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)

FAILshould complete the pending action"That's not it; the plain one." (difficulty —)5.8s

Verdict Expected CLARIFY_ANSWER — should complete the pending action. FAIL: Reported could-not-confirm (write-confirmation false negative).

Why verdict Reported could-not-confirm (write-confirmation false negative).

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

1 · TTS said no speech captured

2 · Card shown What would you like me to do with that?

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-07-30T20:34:57.899Z

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)

UNVERIFIEDunclassifiedshould complete the pending action"No, the other cheese." (difficulty —)2.5s

Why verdict CLARIFY_ANSWER not gradeable single-shot — no pending clarification in this replay (app re-asked / mis-parsed as fresh); needs multi-turn replay.

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

1 · TTS said no speech captured

2 · Card shown What would you like me to do with that?

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-07-30T20:35:11.495Z

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)

UNVERIFIEDunclassifiedshould complete the pending action"Not those cashews — the raw ones." (difficulty —)5.4s

Why verdict CLARIFY_ANSWER not gradeable single-shot — no pending clarification in this replay (app re-asked / mis-parsed as fresh); needs multi-turn replay.

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

1 · TTS said no speech captured

2 · Card shown What would you like me to do with that?

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-07-30T20:35:39.277Z

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)

FAILshould delete the entry"Delete the banana from earlier." (difficulty —)0.1s

Verdict Expected DELETE — should delete the entry. FAIL: Did not delete (not understood / no removal).

Why verdict Did not delete (not understood / no removal).

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

1 · TTS said no speech captured

2 · Card shown I could not find a list matching earlier. Which list has banana?

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-07-30T20:36:01.790Z

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)

FAILshould delete the entry"Remove that Quest bar." (difficulty —)0.1s

Verdict Expected DELETE — should delete the entry. FAIL: Did not delete (not understood / no removal).

Why verdict Did not delete (not understood / no removal).

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

1 · TTS said no speech captured

2 · Card shown Which food entry did you want to correct?

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-07-30T20:36:13.008Z

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)

FAILshould delete the entry"Delete the oats entry." (difficulty —)0.1s

Verdict Expected DELETE — should delete the entry. FAIL: Did not delete (not understood / no removal).

Why verdict Did not delete (not understood / no removal).

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

1 · TTS said no speech captured

2 · Card shown Which food entry did you want to correct?

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-07-30T20:36:24.225Z

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)

FAILshould delete the entry"Take off the eggs." (difficulty —)0.2s

Verdict Expected DELETE — should delete the entry. FAIL: WRONG ACTION — created/logged a NEW entry on a DELETE request.

Why verdict WRONG ACTION — created/logged a NEW entry on a DELETE request.

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 Deleted Oat Milk.

3 · App data rows written deleted food_log_entry:

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-07-30T20:36:42.523Z

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)

FAILshould delete the entry"Remove the raspberries." (difficulty —)0.1s

Verdict Expected DELETE — should delete the entry. FAIL: Did not delete (not understood / no removal).

Why verdict Did not delete (not understood / no removal).

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

1 · TTS said no speech captured

2 · Card shown Which food entry did you want to correct?

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-07-30T20:36:46.792Z

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)

FAILshould delete the entry"Delete the chicken log." (difficulty —)0.1s

Verdict Expected DELETE — should delete the entry. FAIL: Did not delete (not understood / no removal).

Why verdict Did not delete (not understood / no removal).

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

1 · TTS said no speech captured

2 · Card shown Which food entry did you want to correct?

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-07-30T20:36:57.958Z

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)

FAILshould delete the entry"Scratch the almond butter." (difficulty —)0.1s

Verdict Expected DELETE — should delete the entry. FAIL: Did not delete (not understood / no removal).

Why verdict Did not delete (not understood / no removal).

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

1 · TTS said no speech captured

2 · Card shown Which food entry did you want to correct?

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-07-30T20:37:09.225Z

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)

FAILshould delete the entry"Remove the milk entry." (difficulty —)0.1s

Verdict Expected DELETE — should delete the entry. FAIL: Did not delete (not understood / no removal).

Why verdict Did not delete (not understood / no removal).

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

1 · TTS said no speech captured

2 · Card shown Which food entry did you want to correct?

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-07-30T20:37:20.508Z

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)

FAILshould delete the entry"Delete that brownie I logged last night." (difficulty —)0.2s

Verdict Expected DELETE — should delete the entry. FAIL: WRONG ACTION — created/logged a NEW entry on a DELETE request.

Why verdict WRONG ACTION — created/logged a NEW entry on a DELETE request.

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 Deleted brownie.

3 · App data rows written deleted food_log_entry:

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seed food: brownie

{
  "type": "food_item",
  "foodItem": {
    "id": "seed-d-del-0-brownie",
    "name": "brownie",
    "brand": null,
    "source": "manual",
    "servingLabel": "serving",
    "servingQuantity": 1,
    "servingUnit": "serving",
    "macrosPerServing": {
      "calories": 200,
      "proteinGrams": 5,
      "fatGrams": 10,
      "carbsGrams": 20
    },
    "aliases": [],
    "timesLogged": 0,
    "createdAt": "2026-07-16T12:00:00.000Z"
  }
}

Seed food history: 1 for seed-d-del-0-brownie at 2026-07-17T20:00:00.000Z

{
  "type": "food_history",
  "foodItemId": "seed-d-del-0-brownie",
  "quantity": 1,
  "loggedAt": "2026-07-17T20:00:00.000Z"
}

snapshot captured 2026-07-30T20:37:38.889Z

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)

FAILshould delete the entry"Remove yesterday's gelato." (difficulty —)0.0s

Verdict Expected DELETE — should delete the entry. FAIL: Did not delete (not understood / no removal).

Why verdict Did not delete (not understood / no removal).

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

1 · TTS said no speech captured

2 · Card shown Should I add that as a to-do?

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seed food: gelato

{
  "type": "food_item",
  "foodItem": {
    "id": "seed-d-del-1-gelato",
    "name": "gelato",
    "brand": null,
    "source": "manual",
    "servingLabel": "serving",
    "servingQuantity": 1,
    "servingUnit": "serving",
    "macrosPerServing": {
      "calories": 200,
      "proteinGrams": 5,
      "fatGrams": 10,
      "carbsGrams": 20
    },
    "aliases": [],
    "timesLogged": 0,
    "createdAt": "2026-07-16T12:00:00.000Z"
  }
}

Seed food history: 1 for seed-d-del-1-gelato at 2026-07-17T20:00:00.000Z

{
  "type": "food_history",
  "foodItemId": "seed-d-del-1-gelato",
  "quantity": 1,
  "loggedAt": "2026-07-17T20:00:00.000Z"
}

snapshot captured 2026-07-30T20:37:58.474Z

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)

FAILshould delete the entry"Delete the leftover burrito entry." (difficulty —)1.7s

Verdict Expected DELETE — should delete the entry. FAIL: Did not delete (not understood / no removal).

Why verdict Did not delete (not understood / no removal).

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

1 · TTS said no speech captured

2 · Card shown I did not make any app changes. What would you like me to do with that?

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seed food: burrito

{
  "type": "food_item",
  "foodItem": {
    "id": "seed-d-del-2-burrito",
    "name": "burrito",
    "brand": null,
    "source": "manual",
    "servingLabel": "serving",
    "servingQuantity": 1,
    "servingUnit": "serving",
    "macrosPerServing": {
      "calories": 200,
      "proteinGrams": 5,
      "fatGrams": 10,
      "carbsGrams": 20
    },
    "aliases": [],
    "timesLogged": 0,
    "createdAt": "2026-07-16T12:00:00.000Z"
  }
}

Seed food history: 1 for seed-d-del-2-burrito at 2026-07-17T20:00:00.000Z

{
  "type": "food_history",
  "foodItemId": "seed-d-del-2-burrito",
  "quantity": 1,
  "loggedAt": "2026-07-17T20:00:00.000Z"
}

snapshot captured 2026-07-30T20:38:11.342Z

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)

FAILshould delete the entry"Take out the wine from last night." (difficulty —)5.3s

Verdict Expected DELETE — should delete the entry. FAIL: Did not delete (not understood / no removal).

Why verdict Did not delete (not understood / no removal).

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

1 · TTS said no speech captured

2 · Card shown I did not make any app changes. What would you like me to do with that?

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seed food: wine

{
  "type": "food_item",
  "foodItem": {
    "id": "seed-d-del-3-wine",
    "name": "wine",
    "brand": null,
    "source": "manual",
    "servingLabel": "serving",
    "servingQuantity": 1,
    "servingUnit": "serving",
    "macrosPerServing": {
      "calories": 200,
      "proteinGrams": 5,
      "fatGrams": 10,
      "carbsGrams": 20
    },
    "aliases": [],
    "timesLogged": 0,
    "createdAt": "2026-07-16T12:00:00.000Z"
  }
}

Seed food history: 1 for seed-d-del-3-wine at 2026-07-17T20:00:00.000Z

{
  "type": "food_history",
  "foodItemId": "seed-d-del-3-wine",
  "quantity": 1,
  "loggedAt": "2026-07-17T20:00:00.000Z"
}

snapshot captured 2026-07-30T20:38:27.858Z

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)

FAILshould delete the entry"Remove the pastry log from earlier this week." (difficulty —)0.0s

Verdict Expected DELETE — should delete the entry. FAIL: Did not delete (not understood / no removal).

Why verdict Did not delete (not understood / no removal).

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

1 · TTS said no speech captured

2 · Card shown I could not find a list matching earlier this week. Which list has pastry log?

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seed food: pastry

{
  "type": "food_item",
  "foodItem": {
    "id": "seed-d-del-4-pastry",
    "name": "pastry",
    "brand": null,
    "source": "manual",
    "servingLabel": "serving",
    "servingQuantity": 1,
    "servingUnit": "serving",
    "macrosPerServing": {
      "calories": 200,
      "proteinGrams": 5,
      "fatGrams": 10,
      "carbsGrams": 20
    },
    "aliases": [],
    "timesLogged": 0,
    "createdAt": "2026-07-16T12:00:00.000Z"
  }
}

Seed food history: 1 for seed-d-del-4-pastry at 2026-07-17T20:00:00.000Z

{
  "type": "food_history",
  "foodItemId": "seed-d-del-4-pastry",
  "quantity": 1,
  "loggedAt": "2026-07-17T20:00:00.000Z"
}

snapshot captured 2026-07-30T20:38:39.024Z

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)

FAILshould delete the entry"Delete the chips I shouldn't have logged." (difficulty —)0.2s

Verdict Expected DELETE — should delete the entry. FAIL: WRONG ACTION — created/logged a NEW entry on a DELETE request.

Why verdict WRONG ACTION — created/logged a NEW entry on a DELETE request.

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 Deleted chips.

3 · App data rows written deleted food_log_entry:

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seed food: chips

{
  "type": "food_item",
  "foodItem": {
    "id": "seed-d-del-5-chips",
    "name": "chips",
    "brand": null,
    "source": "manual",
    "servingLabel": "serving",
    "servingQuantity": 1,
    "servingUnit": "serving",
    "macrosPerServing": {
      "calories": 200,
      "proteinGrams": 5,
      "fatGrams": 10,
      "carbsGrams": 20
    },
    "aliases": [],
    "timesLogged": 0,
    "createdAt": "2026-07-16T12:00:00.000Z"
  }
}

Seed food history: 1 for seed-d-del-5-chips at 2026-07-17T20:00:00.000Z

{
  "type": "food_history",
  "foodItemId": "seed-d-del-5-chips",
  "quantity": 1,
  "loggedAt": "2026-07-17T20:00:00.000Z"
}

snapshot captured 2026-07-30T20:38:57.388Z

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)

FAILshould update the entry"Change the sequence banana quantity to two." (difficulty —)0.1s

Verdict Expected UPDATE — should update the entry. FAIL: Reported could-not-confirm (write-confirmation false negative).

Why verdict Reported could-not-confirm (write-confirmation false negative).

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

1 · TTS said no speech captured

2 · Card shown I could not confirm that the change was saved, so I did not mark it as done.

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-07-30T20:39:01.605Z

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)

FAILshould update the entry"Actually make the Quest bar two bars." (difficulty —)0.1s

Verdict Expected UPDATE — should update the entry. FAIL: Reported could-not-confirm (write-confirmation false negative).

Why verdict Reported could-not-confirm (write-confirmation false negative).

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

1 · TTS said no speech captured

2 · Card shown I could not confirm that the change was saved, so I did not mark it as done.

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-07-30T20:39:12.809Z

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)

FAILshould update the entry"Update the oats to one and a half cups." (difficulty —)0.1s

Verdict Expected UPDATE — should update the entry. FAIL: Reported could-not-confirm (write-confirmation false negative).

Why verdict Reported could-not-confirm (write-confirmation false negative).

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

1 · TTS said no speech captured

2 · Card shown I could not confirm that the change was saved, so I did not mark it as done.

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-07-30T20:39:24.057Z

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)

FAILshould update the entry"Change the eggs to four." (difficulty —)0.1s

Verdict Expected UPDATE — should update the entry. FAIL: Reported could-not-confirm (write-confirmation false negative).

Why verdict Reported could-not-confirm (write-confirmation false negative).

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

1 · TTS said no speech captured

2 · Card shown I could not confirm that the change was saved, so I did not mark it as done.

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-07-30T20:39:35.274Z

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)

FAILshould update the entry"Make the raspberries a half cup." (difficulty —)5.3s

Verdict Expected UPDATE — should update the entry. FAIL: Did not update (treated as new / not understood).

Why verdict Did not update (treated as new / not understood).

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

1 · TTS said no speech captured

2 · Card shown Which one did you mean? 1. one cup raspberries as a snack, 2. one cup raspberries, 3. raspberries

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-07-30T20:39:51.741Z

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)

FAILshould update the entry"Update the chicken to seven ounces." (difficulty —)0.1s

Verdict Expected UPDATE — should update the entry. FAIL: Reported could-not-confirm (write-confirmation false negative).

Why verdict Reported could-not-confirm (write-confirmation false negative).

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

1 · TTS said no speech captured

2 · Card shown I could not confirm that the change was saved, so I did not mark it as done.

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-07-30T20:40:02.940Z

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)

FAILshould update the entry"Change almond butter to one tablespoon." (difficulty —)0.1s

Verdict Expected UPDATE — should update the entry. FAIL: Reported could-not-confirm (write-confirmation false negative).

Why verdict Reported could-not-confirm (write-confirmation false negative).

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

1 · TTS said no speech captured

2 · Card shown I could not confirm that the change was saved, so I did not mark it as done.

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-07-30T20:40:14.158Z

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)

FAILshould update the entry"Actually the milk was two percent, not whole." (difficulty —)0.1s

Verdict Expected UPDATE — should update the entry. FAIL: Reported could-not-confirm (write-confirmation false negative).

Why verdict Reported could-not-confirm (write-confirmation false negative).

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

1 · TTS said no speech captured

2 · Card shown I could not confirm that the change was saved, so I did not mark it as done.

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-07-30T20:40:25.374Z

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)

FAILshould update the entry"Actually that was strawberry, not vanilla." (difficulty —)0.1s

Verdict Expected UPDATE — should update the entry. FAIL: Reported could-not-confirm (write-confirmation false negative).

Why verdict Reported could-not-confirm (write-confirmation false negative).

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

1 · TTS said no speech captured

2 · Card shown I could not confirm that the change was saved, so I did not mark it as done.

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seed food: vanilla item

{
  "type": "food_item",
  "foodItem": {
    "id": "seed-d-edit-0-vanilla-item",
    "name": "vanilla item",
    "brand": null,
    "source": "manual",
    "servingLabel": "serving",
    "servingQuantity": 1,
    "servingUnit": "serving",
    "macrosPerServing": {
      "calories": 180,
      "proteinGrams": 8,
      "fatGrams": 6,
      "carbsGrams": 18
    },
    "aliases": [],
    "timesLogged": 0,
    "createdAt": "2026-07-16T12:00:00.000Z"
  }
}

Seed food history: 1 for seed-d-edit-0-vanilla-item at 2026-07-18T10:00:00.000Z

{
  "type": "food_history",
  "foodItemId": "seed-d-edit-0-vanilla-item",
  "quantity": 1,
  "loggedAt": "2026-07-18T10:00:00.000Z"
}

snapshot captured 2026-07-30T20:40:36.574Z

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)

FAILshould update the entry"Change the portion to one and a half cups." (difficulty —)0.1s

Verdict Expected UPDATE — should update the entry. FAIL: Reported could-not-confirm (write-confirmation false negative).

Why verdict Reported could-not-confirm (write-confirmation false negative).

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

1 · TTS said no speech captured

2 · Card shown I could not confirm that the change was saved, so I did not mark it as done.

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seed food: quinoa

{
  "type": "food_item",
  "foodItem": {
    "id": "seed-d-edit-1-quinoa",
    "name": "quinoa",
    "brand": null,
    "source": "manual",
    "servingLabel": "serving",
    "servingQuantity": 1,
    "servingUnit": "serving",
    "macrosPerServing": {
      "calories": 180,
      "proteinGrams": 8,
      "fatGrams": 6,
      "carbsGrams": 18
    },
    "aliases": [],
    "timesLogged": 0,
    "createdAt": "2026-07-16T12:00:00.000Z"
  }
}

Seed food history: 1 for seed-d-edit-1-quinoa at 2026-07-18T10:00:00.000Z

{
  "type": "food_history",
  "foodItemId": "seed-d-edit-1-quinoa",
  "quantity": 1,
  "loggedAt": "2026-07-18T10:00:00.000Z"
}

snapshot captured 2026-07-30T20:40:47.774Z

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)

FAILshould update the entry"Make it a quarter cup instead." (difficulty —)0.1s

Verdict Expected UPDATE — should update the entry. FAIL: Reported could-not-confirm (write-confirmation false negative).

Why verdict Reported could-not-confirm (write-confirmation false negative).

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

1 · TTS said no speech captured

2 · Card shown I could not confirm that the change was saved, so I did not mark it as done.

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seed food: granola

{
  "type": "food_item",
  "foodItem": {
    "id": "seed-d-edit-2-granola",
    "name": "granola",
    "brand": null,
    "source": "manual",
    "servingLabel": "serving",
    "servingQuantity": 1,
    "servingUnit": "serving",
    "macrosPerServing": {
      "calories": 180,
      "proteinGrams": 8,
      "fatGrams": 6,
      "carbsGrams": 18
    },
    "aliases": [],
    "timesLogged": 0,
    "createdAt": "2026-07-16T12:00:00.000Z"
  }
}

Seed food history: 1 for seed-d-edit-2-granola at 2026-07-18T10:00:00.000Z

{
  "type": "food_history",
  "foodItemId": "seed-d-edit-2-granola",
  "quantity": 1,
  "loggedAt": "2026-07-18T10:00:00.000Z"
}

snapshot captured 2026-07-30T20:40:59.040Z

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)

FAILshould update the entry"Update that to eight ounces." (difficulty —)1.8s

Verdict Expected UPDATE — should update the entry. FAIL: Did not update — misroute-into-food (no verified mutation).

Why verdict Did not update — misroute-into-food (no verified mutation).

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

1 · TTS said no speech captured

2 · Card shown I could not find a food entry matching "that" to update. Which food item did you want to change to eight ounces?

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seed food: salmon

{
  "type": "food_item",
  "foodItem": {
    "id": "seed-d-edit-3-salmon",
    "name": "salmon",
    "brand": null,
    "source": "manual",
    "servingLabel": "serving",
    "servingQuantity": 1,
    "servingUnit": "serving",
    "macrosPerServing": {
      "calories": 180,
      "proteinGrams": 8,
      "fatGrams": 6,
      "carbsGrams": 18
    },
    "aliases": [],
    "timesLogged": 0,
    "createdAt": "2026-07-16T12:00:00.000Z"
  }
}

Seed food history: 1 for seed-d-edit-3-salmon at 2026-07-18T10:00:00.000Z

{
  "type": "food_history",
  "foodItemId": "seed-d-edit-3-salmon",
  "quantity": 1,
  "loggedAt": "2026-07-18T10:00:00.000Z"
}

snapshot captured 2026-07-30T20:41:12.025Z

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)

FAILshould update the entry"Actually it was cashew butter, not almond butter." (difficulty —)0.1s

Verdict Expected UPDATE — should update the entry. FAIL: Reported could-not-confirm (write-confirmation false negative).

Why verdict Reported could-not-confirm (write-confirmation false negative).

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

1 · TTS said no speech captured

2 · Card shown I could not confirm that the change was saved, so I did not mark it as done.

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seed food: almond butter

{
  "type": "food_item",
  "foodItem": {
    "id": "seed-d-edit-4-almond-butter",
    "name": "almond butter",
    "brand": null,
    "source": "manual",
    "servingLabel": "serving",
    "servingQuantity": 1,
    "servingUnit": "serving",
    "macrosPerServing": {
      "calories": 180,
      "proteinGrams": 8,
      "fatGrams": 6,
      "carbsGrams": 18
    },
    "aliases": [],
    "timesLogged": 0,
    "createdAt": "2026-07-16T12:00:00.000Z"
  }
}

Seed food history: 1 for seed-d-edit-4-almond-butter at 2026-07-18T10:00:00.000Z

{
  "type": "food_history",
  "foodItemId": "seed-d-edit-4-almond-butter",
  "quantity": 1,
  "loggedAt": "2026-07-18T10:00:00.000Z"
}

snapshot captured 2026-07-30T20:41:23.224Z

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)

FAILshould update the entry"Change the pear to a small." (difficulty —)0.1s

Verdict Expected UPDATE — should update the entry. FAIL: Reported could-not-confirm (write-confirmation false negative).

Why verdict Reported could-not-confirm (write-confirmation false negative).

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

1 · TTS said no speech captured

2 · Card shown I could not confirm that the change was saved, so I did not mark it as done.

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seed food: pear

{
  "type": "food_item",
  "foodItem": {
    "id": "seed-d-edit-5-pear",
    "name": "pear",
    "brand": null,
    "source": "manual",
    "servingLabel": "serving",
    "servingQuantity": 1,
    "servingUnit": "serving",
    "macrosPerServing": {
      "calories": 180,
      "proteinGrams": 8,
      "fatGrams": 6,
      "carbsGrams": 18
    },
    "aliases": [],
    "timesLogged": 0,
    "createdAt": "2026-07-16T12:00:00.000Z"
  }
}

Seed food history: 1 for seed-d-edit-5-pear at 2026-07-18T10:00:00.000Z

{
  "type": "food_history",
  "foodItemId": "seed-d-edit-5-pear",
  "quantity": 1,
  "loggedAt": "2026-07-18T10:00:00.000Z"
}

snapshot captured 2026-07-30T20:41:34.490Z

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)

UNVERIFIEDunclassifiedshould answer the query"How much protein is left for today?" (difficulty —)0.1s

Verdict Expected QUERY — should answer the query. UNVERIFIED: answer key has no expected values

Why verdict answer key has no expected values

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

1 · TTS said no speech captured

2 · Card shown You are about 969.5 grams of protein over today's 160 gram protein target (1129.5 logged).

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-07-30T20:41:45.673Z

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)

UNVERIFIEDunclassifiedshould answer the query"How many calories have I logged?" (difficulty —)0.0s

Verdict Expected QUERY — should answer the query. UNVERIFIED: answer key has no expected values

Why verdict answer key has no expected values

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

1 · TTS said no speech captured

2 · Card shown I do not see calories in today's food log.

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-07-30T20:42:12.288Z

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)

UNVERIFIEDunclassifiedshould answer the query"What did I eat last night?" (difficulty —)0.0s

Verdict Expected QUERY — should answer the query. UNVERIFIED: answer key has no expected values

Why verdict answer key has no expected values

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

1 · TTS said no speech captured

2 · Card shown No — I do not see last night logged today.

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-07-30T20:42:23.475Z

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)

UNVERIFIEDunclassifiedshould answer the query"How much fiber today?" (difficulty —)0.0s

Verdict Expected QUERY — should answer the query. UNVERIFIED: answer key has no expected values

Why verdict answer key has no expected values

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

1 · TTS said no speech captured

2 · Card shown I understood the nutrition question, but I could not find a solid number for that food yet. Nothing was logged.

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-07-30T20:42:34.656Z

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)

UNVERIFIEDunclassifiedshould answer the query"What's left in my calorie budget?" (difficulty —)0.0s

Verdict Expected QUERY — should answer the query. UNVERIFIED: answer key has no expected values

Why verdict answer key has no expected values

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

1 · TTS said no speech captured

2 · Card shown You are about 15083 calories over today's 2200 calorie budget (17283 logged).

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-07-30T20:42:45.873Z

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)

UNVERIFIEDunclassifiedshould answer the query"Did I log lunch yet?" (difficulty —)0.0s

Verdict Expected QUERY — should answer the query. UNVERIFIED: answer key has no expected values

Why verdict answer key has no expected values

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

1 · TTS said no speech captured

2 · Card shown I do not see lunch logged today.

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-07-30T20:42:57.040Z

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)

UNVERIFIEDunclassifiedshould answer the query"How many carbs so far?" (difficulty —)0.0s

Verdict Expected QUERY — should answer the query. UNVERIFIED: answer key has no expected values

Why verdict answer key has no expected values

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

1 · TTS said no speech captured

2 · Card shown I understood the nutrition question, but I could not find a solid number for that food yet. Nothing was logged.

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-07-30T20:43:08.238Z

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)

UNVERIFIEDunclassifiedshould answer the query"What did I eat before the gym?" (difficulty —)0.0s

Verdict Expected QUERY — should answer the query. UNVERIFIED: answer key has no expected values

Why verdict answer key has no expected values

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

1 · TTS said no speech captured

2 · Card shown No — I do not see before the gym logged today.

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-07-30T20:43:19.406Z

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)

UNVERIFIEDunclassifiedshould answer the query"Show me yesterday's food log." (difficulty —)0.1s

Verdict Expected QUERY — should answer the query. UNVERIFIED: answer key has no expected values

Why verdict answer key has no expected values

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

1 · TTS said no speech captured

2 · Card shown Opening Food History.

4 · UI did navigated to "food" screen

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-07-30T20:43:30.722Z

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)

UNVERIFIEDunclassifiedshould answer the query"Am I under my fat goal?" (difficulty —)0.1s

Verdict Expected QUERY — should answer the query. UNVERIFIED: answer key has no expected values

Why verdict answer key has no expected values

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

1 · TTS said no speech captured

2 · Card shown I understood the nutrition question, but I could not find a solid number for that food yet. Nothing was logged.

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-07-30T20:43:41.922Z

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)

UNVERIFIEDunclassifiedshould answer the query"How many calories in the pear I just logged?" (difficulty —)0.1s

Verdict Expected QUERY — should answer the query. UNVERIFIED: answer key has no expected values

Why verdict answer key has no expected values

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

1 · TTS said no speech captured

2 · Card shown Pear has about 101 calories per 178 g.

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-07-30T20:43:53.206Z

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)

UNVERIFIEDunclassifiedshould answer the query"What was my first meal today?" (difficulty —)0.1s

Verdict Expected QUERY — should answer the query. UNVERIFIED: answer key has no expected values

Why verdict answer key has no expected values

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

1 · TTS said no speech captured

2 · Card shown Today you logged Banana (1 large banana), Quest Birthday Cake Protein Bar (one), Egg (3 eggs), Raspberries (1 cup), Chicken thigh (5 oz), plus 105 more. Total: 17283 calories, 1129.5 g protein, 607.4 g fat, 1922.3 g carbs.

4 · UI did navigated to "food" screen

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-07-30T20:44:04.455Z

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)

UNVERIFIEDunclassifiedshould answer the query"How much coffee have I logged?" (difficulty —)0.1s

Verdict Expected QUERY — should answer the query. UNVERIFIED: answer key has no expected values

Why verdict answer key has no expected values

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

1 · TTS said no speech captured

2 · Card shown I do not see coffee in today's food log.

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-07-30T20:44:15.722Z

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)

UNVERIFIEDunclassifiedshould answer the query"Calories left for a snack?" (difficulty —)0.1s

Verdict Expected QUERY — should answer the query. UNVERIFIED: answer key has no expected values

Why verdict answer key has no expected values

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

1 · TTS said no speech captured

2 · Card shown You are about 15083 calories over today's 2200 calorie budget (17283 logged).

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-07-30T20:44:26.939Z

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)

UNVERIFIEDunclassifiedshould answer the query"Did I already log my usual RXBAR?" (difficulty —)0.1s

Verdict Expected QUERY — should answer the query. UNVERIFIED: answer key has no expected values

Why verdict answer key has no expected values

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

1 · TTS said no speech captured

2 · Card shown Yes. Today you logged 1 bar RXBAR RXBAR Blueberry.

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-07-30T20:44:38.206Z

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)

UNVERIFIEDunclassifiedshould answer the query"What's my average calories this week?" (difficulty —)0.1s

Verdict Expected QUERY — should answer the query. UNVERIFIED: answer key has no expected values

Why verdict answer key has no expected values

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

1 · TTS said no speech captured

2 · Card shown I understood the nutrition question, but I could not find a solid number for that food yet. Nothing was logged.

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-07-30T20:44:49.573Z

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)

UNVERIFIEDunclassifiedshould answer the query"How many food entries today?" (difficulty —)0.1s

Verdict Expected QUERY — should answer the query. UNVERIFIED: answer key has no expected values

Why verdict answer key has no expected values

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

1 · TTS said no speech captured

2 · Card shown You have 110 food entries logged today.

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-07-30T20:45:00.904Z

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)

FAILshould answer the query"What did I have mid-afternoon?" (difficulty —)7.7s

Verdict Expected QUERY — should answer the query. FAIL: Query not answered — asked back instead of answering.

Why verdict Query not answered — asked back instead of answering.

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

1 · TTS said no speech captured

2 · Card shown What exact food and amount should I use for what did i have mid afternoon? I did not log it yet because I could not safely finish that food log.

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-07-30T20:45:19.737Z

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 navigate"Show the food diary screen." (difficulty —)0.1s

Verdict Expected NAVIGATE — should navigate. PASS: Navigated.

Why verdict Navigated.

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

1 · TTS said no speech captured

2 · Card shown Opening Food.

4 · UI did navigated to "food" screen

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-07-30T20:45:31.003Z

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)

FAILshould navigate"Open macro goals." (difficulty —)0.1s

Verdict Expected NAVIGATE — should navigate. FAIL: Did not navigate — misrouted into a food/workout clarification or dead-ended.

Why verdict Did not navigate — misrouted into a food/workout clarification or dead-ended.

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

1 · TTS said no speech captured

2 · Card shown What would you like me to do with that?

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-07-30T20:45:42.254Z

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)

FAILshould apply the setting"Set my protein goal to one hundred sixty grams." (difficulty —)0.1s

Verdict Expected SETTINGS — should apply the setting. FAIL: Reported could-not-confirm (write-confirmation false negative).

Why verdict Reported could-not-confirm (write-confirmation false negative).

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

1 · TTS said no speech captured

2 · Card shown I'm not sure how to help with that yet. Try asking me to log food, a workout, a note, or a to-do.

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-07-30T20:45:53.522Z

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)

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