food-corpus-b-FROZEN-20260712-324f4ab3-c62-20260802

Supposed to	N	Correct	Wrong	Unverified
▸ LOG — log the entry	180	85 (47%)	62 (34%)	33 (18%)
62 handled wrong — click one to jump to its full detail below "I ate 2 slices sourdough toast with 14 grams butter." WRITE-TRUTH FAIL — IMPLAUSIBLE: 530 kcal is implausibly HIGH for 2 count of Toast (typical 160-260 kcal [per-serving]) "Breakfast was 45 grams dry rolled oats cooked with water." OVER-ASK — asked instead of logging (no saved row). "Add one large navel orange." OVER-ASK — asked instead of logging (no saved row). "Dinner was 5 ounces cod plus 160 grams roasted potatoes." OVER-ASK — asked instead of logging (no saved row). "Track 7 ounces rotisserie chicken, meat only." WRITE-TRUTH FAIL — WRONG/MISSING item "7 ounces rotisserie chicken meat only" — no saved row with matching identity (rows: Chicken breast, Pork, Cured, Ham with Natural Juices, Spiral Slice, Meat Only, Boneless, Separable Lean Only, Heated, Roasted) "Log 250 milliliters whole milk." OVER-ASK — asked instead of logging (no saved row). "Record 100 grams cooked pasta with 125 grams marinara." OVER-ASK — asked instead of logging (no saved row). "Add 140 grams sweet potato mash." OVER-ASK — asked instead of logging (no saved row). "Add 1 cup canned corn drained." OVER-ASK — asked instead of logging (no saved row). "Add 1 cup beef chili." OVER-ASK — asked instead of logging (no saved row). "I had 1 cup cooked couscous." OVER-ASK — asked instead of logging (no saved row). "Track 6 ounces tilapia with lemon, no oil." Reported could-not-confirm (write-confirmation false negative). "Record 45 grams pita chips." WRITE-TRUTH FAIL — WRONG/MISSING item "45 grams pita chips" — no saved row with matching identity (rows: Potato Chips) "Record 2 cups cauliflower rice." OVER-ASK — asked instead of logging (no saved row). "Add 5 ounces lamb chop, cooked weight." OVER-ASK — asked instead of logging (no saved row). "Record one Fairlife Core Power 26 gram vanilla shake." WRITE-TRUTH FAIL — IMPLAUSIBLE: 15 kcal is implausibly LOW for 1 count of Fairlife Core Power Elite Vanilla Protein Shake (typical 160-250 kcal [per-serving]) "Add a Starbucks grande flat white with whole milk." OVER-ASK — asked instead of logging (no saved row). "Track a Chipotle chicken bowl: white rice, black beans, mild salsa, cheese, lettuce." OVER-ASK — asked instead of logging (no saved row). "Log a McDonalds Egg McMuffin." OVER-ASK — asked instead of logging (no saved row). "I ate a Taco Bell bean burrito." OVER-ASK — asked instead of logging (no saved row). "Track one Dave’s Killer Bread thin-sliced Good Seed slice." OVER-ASK — asked instead of logging (no saved row). "Log a Siggi’s strawberry skyr cup." OVER-ASK — asked instead of logging (no saved row). "I had a Panera Fuji apple salad with chicken, full size." OVER-ASK — asked instead of logging (no saved row). "Record one Celsius peach vibe can." OVER-ASK — asked instead of logging (no saved row). "Add a Kodiak Cakes protein waffle, one waffle." WRITE-TRUTH FAIL — WRONG item/product identity "Kodiak Cakes protein waffle" — saved row does not hit product alias (rows: Waffle, Plain, Birthday Cake Power Waffles With Sprinkles) "Track a Subway six inch turkey on wheat with provolone." OVER-ASK — asked instead of logging (no saved row). "Log one KIND dark chocolate nuts and sea salt bar." WRITE-TRUTH FAIL — WRONG item/product identity "KIND dark chocolate nuts" — saved row does not hit product alias (rows: No Cow Chocolate Sea Salt Bar, Dark chocolate) "I ate a Trader Joe’s chicken tikka masala frozen meal." OVER-ASK — asked instead of logging (no saved row). "Add a Wendy’s small chili." OVER-ASK — asked instead of logging (no saved row). "Log a Sweetgreen harvest bowl." OVER-ASK — asked instead of logging (no saved row). "I had one Larabar apple pie bar." WRITE-TRUTH FAIL — IMPLAUSIBLE: 198 kcal is implausibly HIGH for 1 count of Apple Pie Fruit & Nut Bar (typical 60-130 kcal [per-serving]) "Record a Dunkin medium iced coffee: cream plus sugar." OVER-ASK — asked instead of logging (no saved row). "Add a Kirkland protein bar chocolate brownie." OVER-ASK — asked instead of logging (no saved row). "Track a Five Guys little cheeseburger." OVER-ASK — asked instead of logging (no saved row). "Log one Blue Diamond 100 calorie almond pack." OVER-ASK — asked instead of logging (no saved row). "I ate a Lean Cuisine herb roasted chicken meal." OVER-ASK — asked instead of logging (no saved row). "Record one Gatorade Zero 20 ounce bottle." OVER-ASK — asked instead of logging (no saved row). "Add a Shake Shack single ShackBurger." OVER-ASK — asked instead of logging (no saved row). "Track a Noosa lemon yogurt 8 ounce tub." OVER-ASK — asked instead of logging (no saved row). "Log a Costco rotisserie chicken breast serving, 6 ounces." OVER-ASK — asked instead of logging (no saved row). "Add a Nature Valley oats and honey two-bar pack." OVER-ASK — asked instead of logging (no saved row). "Track a Whole Foods salmon avocado roll." OVER-ASK — asked instead of logging (no saved row). "Log one PopCorners sea salt snack bag." OVER-ASK — asked instead of logging (no saved row). "Add a Banza chickpea pasta serving, 2 ounces dry." OVER-ASK — asked instead of logging (no saved row). "Track one Halo Top vanilla bean pint, half the pint." OVER-ASK — asked instead of logging (no saved row). "Log my turkey sandwich: two slices rye, 4 ounces turkey, one slice Swiss, mustard." WRITE-TRUTH FAIL — WRONG/MISSING item "rye bread" — no saved row with matching identity (rows: Turkey Sandwich); WRONG/MISSING item "swiss" — no saved row with matching identity (rows: Turkey Sandwich); WRONG/MISSING item "mustard" — no saved row with matching identity (rows: Turkey Sandwich) "Dinner bowl: 150 grams rice, 120 grams chicken, 80 grams avocado, salsa, 30 grams cheese." OVER-ASK — asked instead of logging (no saved row). "Add homemade smoothie: banana, 1 cup whole milk, 30 grams peanut butter, and a scoop whey." WRITE-TRUTH FAIL — WRONG/MISSING item "whole milk" — no saved row with matching identity (rows: Banana, Homemade Smoothie); WRONG/MISSING item "peanut butter" — no saved row with matching identity (rows: Banana, Homemade Smoothie); WRONG/MISSING item "whey" — no saved row with matching identity (rows: Banana, Homemade Smoothie) "Track tacos: three corn tortillas, 5 ounces carne asada, onions, cilantro, and salsa verde." OVER-ASK — asked instead of logging (no saved row). "Log salad: 4 cups arugula, 120 grams grilled shrimp, 20 grams walnuts, balsamic." WRITE-TRUTH FAIL — WRONG/MISSING item "grilled shrimp" — no saved row with matching identity (rows: Arugula, Salad); WRONG/MISSING item "walnuts" — no saved row with matching identity (rows: Arugula, Salad); WRONG/MISSING item "balsamic" — no saved row with matching identity (rows: Arugula, Salad) "Record burger night: bun, 6 ounce beef patty, cheddar, ketchup, and fries." OVER-ASK — asked instead of logging (no saved row). "I had sushi: 6 salmon avocado pieces and miso soup." OVER-ASK — asked instead of logging (no saved row). "I ate enchiladas: two chicken enchiladas, rice, beans, and sour cream." OVER-ASK — asked instead of logging (no saved row). "Record my normal pre-workout snack." OVER-ASK — asked instead of logging (no saved row). "Log the same lunch I had Monday." WRITE-TRUTH FAIL — WRONG/MISSING item "Chicken Rice Bowl" — no saved row with matching identity (rows: Sweetgreen Harvest Bowl) "Log another Fairlife shake like this morning." WRITE-TRUTH FAIL — WRONG/MISSING item "Fairlife Core Power Chocolate" — no saved row with matching identity (rows: Fairlife Core Power Elite Vanilla Protein Shake) "Track the other half of dinner from last night." OVER-ASK — asked instead of logging (no saved row). "Log 3 ounces canned tuna in water with 1 tablespoon light mayo." OVER-ASK — asked instead of logging (no saved row). "Record a 16 ounce homemade green juice: kale, apple, cucumber, ginger." OVER-ASK — asked instead of logging (no saved row). "Log one bakery blueberry muffin, large." OVER-ASK — asked instead of logging (no saved row). "Record 1 cup chicken salad made with mayo." OVER-ASK — asked instead of logging (no saved row). "Record 3 dates stuffed with almond butter." OVER-ASK — asked instead of logging (no saved row).
▸ CLARIFY — ask a clarifying question	25	22 (88%)	3 (12%)	0 (0%)
3 handled wrong — click one to jump to its full detail below "I ate the usual snack." WRONG item vs seeded default/key — WRONG/MISSING item "usual snack" — no saved row with matching identity (rows: Coffee) "Add one serving of chips." Logged a BLIND guess — no stated assumption, no correction invited. "I ate my meal prep." WRONG item vs seeded default/key — WRONG/MISSING item "meal prep" — no saved row with matching identity (rows: Chicken Salad Meal)
▸ QUERY — answer the query	20	2 (10%)	3 (15%)	15 (75%)
3 handled wrong — click one to jump to its full detail below "Give me the sodium count for a Subway turkey sandwich." answer did not state expected numeric value(s): sodiumMg "Was dinner higher calorie than lunch today?" answer did not state expected numeric value(s): calories "Show today’s protein total so far." Query not answered — asked back instead of answering.
▸ UPDATE — update the entry	15	6 (40%)	9 (60%)	0 (0%)
9 handled wrong — click one to jump to its full detail below "Change my last chicken entry to 6 ounces, not 4." Reported could-not-confirm (write-confirmation false negative). "Actually make that latte skim milk instead of whole." WRONG ACTION — created a NEW entry on an UPDATE request. "Correction: the rice was brown rice, not white." WRONG ACTION — created a NEW entry on an UPDATE request. "Add olive oil to that salad, one tablespoon." WRONG ACTION — created a NEW entry on an UPDATE request. "Remove the cheese from that sandwich entry." Did not update — misroute-into-food (no verified mutation). "Set the smoothie to two servings." Did not update (treated as new / not understood). "Change lunch from half avocado to a whole avocado." Reported could-not-confirm (write-confirmation false negative). "Update the pasta sauce to pesto instead of marinara." Did not update (treated as new / not understood). "Make the burrito bowl no sour cream." Did not update (treated as new / not understood).
▸ CLARIFY_ANSWER — complete the pending action	12	6 (50%)	0 (0%)	6 (50%)
No errors — all handled correctly.
▸ DELETE — delete the entry	10	0 (0%)	10 (100%)	0 (0%)
10 handled wrong — click one to jump to its full detail below "Delete the banana I just logged." Did not delete (not understood / no removal). "Remove breakfast oatmeal from today." Did not delete (not understood / no removal). "Undo that protein bar entry." Did not delete (not understood / no removal). "Take out the fries from dinner." Did not delete (not understood / no removal). "Delete my lunch salad." Did not delete (not understood / no removal). "Remove the second coffee entry." Did not delete (not understood / no removal). "Cancel the snack I added a minute ago." Did not delete (not understood / no removal). "Erase the pizza from yesterday night." Did not delete (not understood / no removal). "Delete the guacamole line from my burrito bowl." WRONG TARGET — deleted Guacamole instead of guacamole component. "Remove my post-workout shake from today." Did not delete (not understood / no removal).
▸ SETTINGS — apply the setting	10	5 (50%)	0 (0%)	5 (50%)
No errors — all handled correctly.
▸ OTHER — handle appropriately	10	6 (60%)	0 (0%)	4 (40%)
No errors — all handled correctly.
▸ NAVIGATE — navigate	10	6 (60%)	0 (0%)	4 (40%)
No errors — all handled correctly.
▸ DECLINE — decline	8	8 (100%)	0 (0%)	0 (0%)
No errors — all handled correctly.
Total	300	146 (63%)	87	67

PASSshould log the entry"Log 170 grams plain nonfat Greek yogurt." (difficulty —)0.3s

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

Why verdict Logged (write-truth verified): Nonfat Greek yogurt, Nonfat Greek yogurt — 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 Logged 170 grams plain nonfat greek yogurt.

2 · Card shown Logged 170 grams plain nonfat greek yogurt.

3 · App data rows written created food_log_entry: Nonfat Greek yogurt ×1 (170 g) 100 cal · 17.5g P · 6.1g C · 0.7g F
created food_log_entry: Nonfat Greek yogurt ×1 (170 g) 100 cal · 17.5g P · 6.1g 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-08-02T19:35:25.025Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched the common-food list to "Nonfat Greek yogurt" at 90% confidence.
Matched your past food logs to "Plain Greek Yogurt" at 82% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 0.4 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

FAILshould log the entry"I ate 2 slices sourdough toast with 14 grams butter." (difficulty —)0.4s

Verdict Expected LOG — should log the entry. FAIL: WRITE-TRUTH FAIL — IMPLAUSIBLE: 530 kcal is implausibly HIGH for 2 count of Toast (typical 160-260 kcal [per-serving])

Why verdict WRITE-TRUTH FAIL — IMPLAUSIBLE: 530 kcal is implausibly HIGH for 2 count of Toast (typical 160-260 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.4s

1 · TTS said Logged Toast and 14 grams butter. Assumed catalog default servings where you did not say an amount — tell me if that is not right.

2 · Card shown Logged Toast and 14 grams 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: Toast ×2 (100 g) 530 cal · 18g P · 98g C · 6.4g F
created food_log_entry: Butter ×1 (14 g) 100 cal · 0.1g P · 0g C · 11.4g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T19:35:36.608Z

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

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

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

PASSshould log the entry"Record 3.5 ounces roasted turkey breast." (difficulty —)0.2s

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

Why verdict Logged (write-truth verified): 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 Logged 3.5 ounces roasted turkey breast.

2 · Card shown Logged 3.5 ounces roasted turkey breast.

3 · App data rows written created food_log_entry: Turkey breast ×1 (3.5 oz) 134 cal · 28.8g P · 0g C · 1.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-08-02T19:35:47.907Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched the common-food list to "Turkey breast" at 90% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 0.5 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

FAILshould log the entry"Breakfast was 45 grams dry rolled oats cooked with water." (difficulty —)2.2s

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

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

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

Pick every reason you think applies. Multiple boxes are allowed because one utterance can be wrong in more than one way. Use the note below for "Other" or extra detail.

Timing 2.2s

1 · TTS said What exact food and amount should I use for Dry oats? I did not log it yet because I could not safely finish that food log.

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

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

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T19:36:01.278Z

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 entry"Add one large navel orange." (difficulty —)5.4s

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

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

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

Pick every reason you think applies. Multiple boxes are allowed because one utterance can be wrong in more than one way. Use the note below for "Other" or extra detail.

Timing 5.4s

1 · TTS said What exact food and amount should I use for Orange? I did not log it yet because I could not safely finish that food log.

2 · Card shown What exact food and amount should I use for Orange? 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-08-02T19:36:17.747Z

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

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

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

PASSshould log the entry"Track 220 grams cooked jasmine rice." (difficulty —)0.2s

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

Why verdict Logged (write-truth verified): Cooked jasmine 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 Logged 220 grams cooked jasmine rice.

2 · Card shown Logged 220 grams cooked jasmine rice.

3 · App data rows written created food_log_entry: Cooked jasmine rice ×1 (220 g) 286 cal · 5.3g P · 62g 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-08-02T19:36:29.018Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched the common-food list to "Cooked jasmine rice" at 90% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 0.5 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

PASSshould log the entry"For lunch I had 6 ounces grilled flank steak." (difficulty —)0.4s

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

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

2 · Card shown Logged Grilled Steak. Using your recent Grilled Steak history. Tell me if that is wrong.

3 · App data rows written created food_log_entry: Grilled Steak ×1 (ounce) 340 cal · 42g P · 0g C · 18g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T19:36:40.547Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched your past food logs to "Grilled Steak" at 82% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 0.5 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

PASSshould log the entry"Put down 85 grams avocado." (difficulty —)0.2s

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

1 · TTS said Logged 85 grams avocado.

2 · Card shown Logged 85 grams avocado.

3 · App data rows written created food_log_entry: Avocado ×1 (85 g) 136 cal · 1.7g P · 7.2g C · 12.5g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T19:36:51.831Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched the common-food list to "Avocado" at 90% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 0.4 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

PASSshould log the entry"I had a cup and a half of cooked lentils." (difficulty —)0.4s

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

Why verdict Logged (write-truth verified): Lentils — 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 Logged a cup and a half of cooked lentils. Assumed 1.5 cup as the default serving. Tell me if you want a different amount.

2 · Card shown Logged a cup and a half of cooked lentils. Assumed 1.5 cup as the default serving. Tell me if you want a different amount.

3 · App data rows written created food_log_entry: Lentils ×1 (1.5 cup) 345 cal · 26.7g P · 59.7g 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-08-02T19:37:03.395Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched the common-food list to "Lentils" at 90% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 0.6 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

PASSshould log the entry"Record 28 grams cheddar cheese." (difficulty —)0.2s

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

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

1 · TTS said Logged 28 grams cheddar cheese.

2 · Card shown Logged 28 grams cheddar cheese.

3 · App data rows written created food_log_entry: Cheddar cheese ×1 (28 g) 113 cal · 6.4g P · 1g C · 9.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-08-02T19:37:14.696Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched the common-food list to "Cheddar cheese" at 90% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 0.5 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

PASSshould log the entry"Add 12 baby carrots and 2 tablespoons hummus." (difficulty —)2.1s

Verdict Expected LOG — should log the entry. PASS: Logged (write-truth verified): Hummus, Plain, Baby carrots — card not captured.

Why verdict Logged (write-truth verified): Hummus, Plain, Baby carrots — 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 2.1s

1 · TTS said Logged 12 baby carrots and Hummus, Plain.

2 · Card shown Logged 12 baby carrots and Hummus, Plain.

3 · App data rows written created food_log_entry: Baby carrots ×1 (12 baby carrots) 42 cal · 0.7g P · 9.8g C · 0.1g F
created food_log_entry: Hummus, Plain ×1 (2 tablespoons (30 g)) 73 cal · 2.2g P · 4.5g C · 5.1g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T19:37:27.924Z

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

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

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

PASSshould log the entry"Track a 9 ounce baked potato, plain." (difficulty —)0.8s

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

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

1 · TTS said Logged a 9 ounce baked potato plain.

2 · Card shown Logged a 9 ounce baked potato plain.

3 · App data rows written created food_log_entry: Potato ×1 (9 oz) 222 cal · 4.8g P · 51.3g C · 0.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-08-02T19:37:39.886Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched the common-food list to "Potato" at 90% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 0.7 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

FAILshould log the entry"Dinner was 5 ounces cod plus 160 grams roasted potatoes." (difficulty —)6.0s

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

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

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

Pick every reason you think applies. Multiple boxes are allowed because one utterance can be wrong in more than one way. Use the note below for "Other" or extra detail.

Timing 6.0s

1 · TTS said 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.

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-08-02T19:37:56.994Z

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

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

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

PASSshould log the entry"Log one cup cooked quinoa." (difficulty —)0.2s

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

1 · TTS said Logged one cup cooked quinoa. Assumed 1 cup as the default serving. Tell me if you want a different amount.

2 · Card shown Logged one cup cooked quinoa. 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 quinoa ×1 (1 cup) 222 cal · 8.1g P · 39.4g C · 3.5g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T19:38:08.307Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched the common-food list to "Cooked quinoa" at 90% confidence.
Matched your past food logs to "Cooked Oatmeal" at 82% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 0.5 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

PASSshould log the entry"Add 2 cups romaine and 30 grams parmesan." (difficulty —)0.3s

Verdict Expected LOG — should log the entry. PASS: Logged (write-truth verified): Parmesan cheese, Romaine lettuce — card not captured.

Why verdict Logged (write-truth verified): Parmesan cheese, Romaine lettuce — 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 Logged 2 cups romaine and 30 grams parmesan.

2 · Card shown Logged 2 cups romaine and 30 grams parmesan.

3 · App data rows written created food_log_entry: Romaine lettuce ×1 (2 cup) 16 cal · 1.1g P · 3.1g C · 0.3g F
created food_log_entry: Parmesan cheese ×1 (30 g) 124 cal · 9g P · 2.5g C · 8.6g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T19:38:19.700Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched the common-food list to "Parmesan cheese" at 90% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 0.7 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

PASSshould log the entry"I ate 150 grams blueberries." (difficulty —)0.1s

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

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

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

Pick every reason you think applies. Multiple boxes are allowed because one utterance can be wrong in more than one way. Use the note below for "Other" or extra detail.

Timing 0.1s

1 · TTS said Logged 150 grams blueberries.

2 · Card shown Logged 150 grams blueberries.

3 · App data rows written created food_log_entry: Blueberries ×1 (150 g) 86 cal · 1g P · 21.8g C · 0.5g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T19:38:30.975Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched the common-food list to "Blueberries" at 90% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 0.5 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

PASSshould log the entry"Record three scrambled eggs cooked with a teaspoon olive oil." (difficulty —)0.5s

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

Why verdict Logged (write-truth verified): Olive oil, 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.5s

1 · TTS said Logged three scrambled eggs cooked and a teaspoon olive oil. Assumed 1 tsp as the default serving. Tell me if you want a different amount. Tell me if that is not right.

2 · Card shown Logged three scrambled eggs cooked and a teaspoon olive oil. Assumed 1 tsp 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: Egg ×1 (3 eggs) 215 cal · 18.9g P · 1g C · 14.3g F
created food_log_entry: Olive oil ×1 (1 tsp) 40 cal · 0g P · 0g C · 4.5g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T19:38:42.680Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched the common-food list to "Egg" at 90% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 1.0 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

FAILshould log the entry"Track 7 ounces rotisserie chicken, meat only." (difficulty —)0.7s

Verdict Expected LOG — should log the entry. FAIL: WRITE-TRUTH FAIL — WRONG/MISSING item "7 ounces rotisserie chicken meat only" — no saved row with matching identity (rows: Chicken breast, Pork, Cured, Ham with Natural Juices, Spiral Slice, Meat Only, Boneless, Separable Lean Only, Heated, Roasted)

Why verdict WRITE-TRUTH FAIL — WRONG/MISSING item "7 ounces rotisserie chicken meat only" — no saved row with matching identity (rows: Chicken breast, Pork, Cured, Ham with Natural Juices, Spiral Slice, Meat Only, Boneless, Separable Lean Only, Heated, Roasted)

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 Logged Chicken breast and Pork, Cured, Ham with Natural Juices, Spiral Slice, Meat Only, Boneless, Separable Lean Only, Heated, Roasted. Assumed a typical serving of Pork, Cured, Ham with Natural Juices, Spiral Slice, Meat Only, Boneless, Separable Lean Only, Heated, Roasted while logging the rest of this meal. Tell me if that is not right.

2 · Card shown Logged Chicken breast and Pork, Cured, Ham with Natural Juices, Spiral Slice, Meat Only, Boneless, Separable Lean Only, Heated, Roasted. Assumed a typical serving of Pork, Cured, Ham with Natural Juices, Spiral Slice, Meat Only, Boneless, Separable Lean Only, Heated, Roasted while logging the rest of this meal. Tell me if that is not right.

3 · App data rows written created food_log_entry: Chicken breast ×1 (7 ounces (198.4 g)) 327 cal · 61.5g P · 0g C · 7.1g F
created food_log_entry: Pork, Cured, Ham with Natural Juices, Spiral Slice, Meat Only, Boneless, Separable Lean Only, Heated, Roasted ×1 (3 serving) 107 cal · 19.2g P · 0.9g C · 3.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-08-02T19:38:54.463Z

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

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

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

PASSshould log the entry"Snack was 32 grams almonds." (difficulty —)0.2s

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

Why verdict Logged (write-truth verified): Almonds — 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 Logged 32 grams almonds.

2 · Card shown Logged 32 grams almonds.

3 · App data rows written created food_log_entry: Almonds ×1 (32 g) 185 cal · 6.8g P · 6.9g C · 16g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T19:39:05.754Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched the common-food list to "Almonds" at 90% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 0.6 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

FAILshould log the entry"Log 250 milliliters whole milk." (difficulty —)0.1s

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

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

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

Pick every reason you think applies. Multiple boxes are allowed because one utterance can be wrong in more than one way. Use the note below for "Other" or extra detail.

Timing 0.1s

1 · TTS said I couldn't convert 250 milliliters of Whole milk from the serving information I found. What does the label say for grams or calories? I did not log it yet.

2 · Card shown I couldn't convert 250 milliliters of Whole milk from the serving information I found. What does the label say for grams or calories? 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-08-02T19:39:17.064Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched your past food logs to "Coffee shop default Whole Milk Latte" at 82% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 0.7 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

PASSshould log the entry"I had 1 tablespoon peanut butter on a medium banana." (difficulty —)0.4s

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

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

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

Pick every reason you think applies. Multiple boxes are allowed because one utterance can be wrong in more than one way. Use the note below for "Other" or extra detail.

Timing 0.4s

1 · TTS said Logged 1 tablespoon peanut butter and a medium banana. Assumed 1 medium banana as the default serving. Tell me if you want a different amount. Tell me if that is not right.

2 · Card shown Logged 1 tablespoon peanut butter and a medium banana. Assumed 1 medium banana 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: Peanut butter ×1 (1 tbsp) 88 cal · 3.8g P · 2.9g C · 7.6g F
created food_log_entry: Banana ×1 (1 medium banana) 105 cal · 1.3g P · 27.1g C · 0.4g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T19:39:40.034Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched the common-food list to "Peanut butter" at 90% confidence.
Matched your saved foods and aliases to "Medium Banana" at 60% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 1.0 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

FAILshould log the entry"Record 100 grams cooked pasta with 125 grams marinara." (difficulty —)1.0s

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

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

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

Pick every reason you think applies. Multiple boxes are allowed because one utterance can be wrong in more than one way. Use the note below for "Other" or extra detail.

Timing 1.0s

1 · TTS said I found Cooked pasta, but I also heard 125 marinara. Should I log those separately too?

2 · Card shown I found Cooked pasta, but I also heard 125 marinara. 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-08-02T19:39:52.174Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched the common-food list to "Cooked pasta" at 90% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 1.1 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

PASSshould log the entry"Add 4 ounces tofu and 2 cups broccoli." (difficulty —)0.3s

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

Why verdict Logged (write-truth verified): Firm tofu, Broccoli — 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 Logged 4 ounces tofu and 2 cups broccoli.

2 · Card shown Logged 4 ounces tofu and 2 cups broccoli.

3 · App data rows written created food_log_entry: Firm tofu ×1 (4 oz) 163 cal · 19.3g P · 3.2g C · 9.9g F
created food_log_entry: Broccoli ×1 (2 cup) 64 cal · 4.4g P · 13.1g 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-08-02T19:40:03.680Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched the common-food list to "Broccoli" at 90% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 0.9 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

PASSshould log the entry"Track 1 cup black beans drained." (difficulty —)0.2s

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

Why verdict Logged (write-truth verified): Black 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 Logged 1 cup black beans drained.

2 · Card shown Logged 1 cup black beans drained.

3 · App data rows written created food_log_entry: Black beans ×1 (1 cup) 227 cal · 15.3g P · 40.8g 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-08-02T19:40:14.988Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched the common-food list to "Black beans" at 90% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 1.0 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

PASSshould log the entry"Put down 60 grams granola." (difficulty —)0.2s

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

Why verdict Logged (write-truth verified): Granola — 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 Logged 60 grams granola.

2 · Card shown Logged 60 grams granola.

3 · App data rows written created food_log_entry: Granola ×1 (60 g) 283 cal · 6g P · 38.4g C · 12g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T19:40:26.288Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched the common-food list to "Granola" at 90% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 0.7 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

PASSshould log the entry"I ate 180 grams cottage cheese." (difficulty —)0.1s

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

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

1 · TTS said Logged 180 grams cottage cheese.

2 · Card shown Logged 180 grams cottage cheese.

3 · App data rows written created food_log_entry: Cottage cheese ×1 (180 g) 176 cal · 20g P · 6.1g C · 7.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-08-02T19:40:37.572Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched the common-food list to "Cottage cheese" at 90% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 0.9 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

PASSshould log the entry"Log one medium pear and 18 grams walnuts." (difficulty —)0.3s

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

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

1 · TTS said Logged one medium pear and 18 grams walnuts. Assumed 1 pear as the default serving. Tell me if you want a different amount. Tell me if that is not right.

2 · Card shown Logged one medium pear and 18 grams walnuts. 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: Pear ×1 (1 pear) 101 cal · 0.7g P · 27.1g C · 0.2g F
created food_log_entry: Walnuts ×1 (18 g) 118 cal · 2.7g P · 2.5g C · 11.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-08-02T19:40:48.973Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched the common-food list to "Walnuts" at 90% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 1.0 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

PASSshould log the entry"Record 2 ounces smoked salmon." (difficulty —)0.2s

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

Why verdict Logged (write-truth verified): Smoked salmon — 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 Logged 2 ounces smoked salmon.

2 · Card shown Logged 2 ounces smoked salmon.

3 · App data rows written created food_log_entry: Smoked salmon ×1 (2 oz) 66 cal · 10.4g P · 0g C · 2.4g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T19:41:00.272Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched the common-food list to "Smoked salmon" at 90% confidence.
Matched your past food logs to "Baked Salmon" at 82% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 0.8 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

PASSshould log the entry"Add 1 cup cooked farro." (difficulty —)0.2s

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

1 · TTS said Logged 1 cup cooked farro.

2 · Card shown Logged 1 cup cooked farro.

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-08-02T19:41:11.590Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched the common-food list to "Cooked farro" at 90% confidence.
Matched your past food logs to "Cooked quinoa" at 82% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 0.9 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

PASSshould log the entry"Track 90 grams cucumber and 90 grams tomato." (difficulty —)0.3s

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

Why verdict Logged (write-truth verified): Tomato, Cucumber — 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 Logged 90 grams cucumber and 90 grams tomato.

2 · Card shown Logged 90 grams cucumber and 90 grams tomato.

3 · App data rows written created food_log_entry: Cucumber ×1 (90 g) 14 cal · 0.6g P · 3.2g C · 0.1g F
created food_log_entry: Tomato ×1 (90 g) 16 cal · 0.8g P · 3.5g 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-08-02T19:41:22.999Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched the common-food list to "Cucumber" at 90% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 1.1 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

PASSshould log the entry"Log 6 ounces pork tenderloin." (difficulty —)0.2s

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

1 · TTS said Logged 6 ounces pork tenderloin.

2 · Card shown Logged 6 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-08-02T19:41:34.333Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched the common-food list to "Pork tenderloin" at 90% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 1.0 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

PASSshould log the entry"Record 1 cup edamame shelled." (difficulty —)0.2s

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

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

1 · TTS said Logged 1 cup edamame shelled.

2 · Card shown Logged 1 cup edamame shelled.

3 · App data rows written created food_log_entry: Edamame ×1 (1 cup) 188 cal · 18.4g P · 13.8g 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-08-02T19:41:45.615Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched the common-food list to "Edamame" at 90% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 1.0 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

PASSshould log the entry"Add a small flour tortilla with 50 grams grilled chicken." (difficulty —)0.5s

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

Why verdict Logged (write-truth verified): Chicken breast, Flour tortilla — 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 Logged a small flour tortilla and 50 grams grilled chicken. Assumed 1 small flour tortilla as the default serving. Tell me if you want a different amount. Tell me if that is not right.

2 · Card shown Logged a small flour tortilla and 50 grams grilled chicken. Assumed 1 small flour tortilla 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: Flour tortilla ×1 (1 small flour tortilla) 74 cal · 2g P · 12g C · 1.9g F
created food_log_entry: Chicken breast ×1 (50 g) 83 cal · 15.5g P · 0g C · 1.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-08-02T19:41:57.278Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched the common-food list to "Flour tortilla" at 90% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 1.5 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

PASSshould log the entry"I had 40 grams raisins." (difficulty —)0.2s

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

Why verdict Logged (write-truth verified): Raisins — 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 Logged 40 grams raisins.

2 · Card shown Logged 40 grams raisins.

3 · App data rows written created food_log_entry: Raisins ×1 (40 g) 120 cal · 1.2g P · 31.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-08-02T19:42:08.579Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched the common-food list to "Raisins" at 90% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 0.9 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

PASSshould log the entry"Track 2 tablespoons chia seeds." (difficulty —)0.2s

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

Why verdict Logged (write-truth verified): Chia seeds — 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 Logged 2 tablespoons chia seeds.

2 · Card shown Logged 2 tablespoons chia seeds.

3 · App data rows written created food_log_entry: Chia seeds ×1 (2 tbsp) 102 cal · 3.5g P · 8.8g C · 6.4g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T19:42:19.873Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched the common-food list to "Chia seeds" at 90% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 1.1 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

PASSshould log the entry"Log 5 ounces shrimp cooked." (difficulty —)0.2s

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

Why verdict Logged (write-truth verified): Shrimp — 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 Logged 5 ounces shrimp cooked.

2 · Card shown Logged 5 ounces shrimp cooked.

3 · App data rows written created food_log_entry: Shrimp ×1 (5 oz) 140 cal · 34g P · 0.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-08-02T19:42:31.152Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched the common-food list to "Shrimp" at 90% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 1.1 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

PASSshould log the entry"Record 1 cup unsweetened applesauce." (difficulty —)0.2s

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

Why verdict Logged (write-truth verified): Unsweetened applesauce — 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 Logged 1 cup unsweetened applesauce.

2 · Card shown Logged 1 cup unsweetened applesauce.

3 · App data rows written created food_log_entry: Unsweetened applesauce ×1 (1 cup) 102 cal · 0.5g P · 27.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-08-02T19:42:42.455Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched the common-food list to "Unsweetened applesauce" at 90% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 1.1 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

FAILshould log the entry"Add 140 grams sweet potato mash." (difficulty —)4.0s

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

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

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

Pick every reason you think applies. Multiple boxes are allowed because one utterance can be wrong in more than one way. Use the note below for "Other" or extra detail.

Timing 4.0s

1 · TTS said Which one did you mean? 1. Sweet Potato Mash — T.G.I. FRIDAY'S, 2. Sweet Potato Mash — HUNGRY JACK, 3. Sweet Potato Mash — Basic American Foods, Inc.

2 · Card shown Which one did you mean? 1. Sweet Potato Mash — T.G.I. FRIDAY'S, 2. Sweet Potato Mash — HUNGRY JACK, 3. Sweet Potato Mash — Basic American Foods, Inc.

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T19:42:57.564Z

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

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

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

PASSshould log the entry"I ate 25 grams dark chocolate." (difficulty —)0.2s

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

Why verdict Logged (write-truth verified): Dark chocolate — 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 Logged 25 grams dark chocolate.

2 · Card shown Logged 25 grams dark chocolate.

3 · App data rows written created food_log_entry: Dark chocolate ×1 (25 g) 138 cal · 1.3g P · 15g 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-08-02T19:43:08.873Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched the common-food list to "Dark chocolate" at 90% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 1.1 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

PASSshould log the entry"Track 2 cups air-popped popcorn." (difficulty —)0.2s

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

Why verdict Logged (write-truth verified): Air-popped popcorn — 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 Logged 2 cups air popped popcorn.

2 · Card shown Logged 2 cups air popped popcorn.

3 · App data rows written created food_log_entry: Air-popped popcorn ×1 (2 cup) 62 cal · 2.1g P · 12.5g 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-08-02T19:43:20.185Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched the common-food list to "Air-popped popcorn" at 90% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 1.3 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

PASSshould log the entry"Log 1.25 cups low fat kefir." (difficulty —)0.2s

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

Why verdict Logged (write-truth verified): Kefir — 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 Logged 1.25 cups low fat kefir.

2 · Card shown Logged 1.25 cups low fat kefir.

3 · App data rows written created food_log_entry: Kefir ×1 (1.25 cup) 126 cal · 10.1g P · 13.8g C · 3.1g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T19:43:42.969Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched the common-food list to "Kefir" at 90% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 1.3 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

PASSshould log the entry"Record 4 ounces tempeh." (difficulty —)0.2s

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

Why verdict Logged (write-truth verified): Tempeh — 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 Logged 4 ounces tempeh.

2 · Card shown Logged 4 ounces tempeh.

3 · App data rows written created food_log_entry: Tempeh ×1 (4 oz) 218 cal · 23g P · 8.6g C · 12.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-08-02T19:43:54.225Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched the common-food list to "Tempeh" at 90% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 1.0 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

FAILshould log the entry"Add 1 cup canned corn drained." (difficulty —)5.4s

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

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

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

Pick every reason you think applies. Multiple boxes are allowed because one utterance can be wrong in more than one way. Use the note below for "Other" or extra detail.

Timing 5.4s

1 · TTS said What exact food and amount should I use for 1 cup canned corn drained? I did not log it yet because I could not safely finish that food log.

2 · Card shown What exact food and amount should I use for 1 cup canned corn drained? 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-08-02T19:44:10.766Z

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

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

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

PASSshould log the entry"I had 70 grams turkey pepperoni." (difficulty —)2.0s

Verdict Expected LOG — should log the entry. PASS: Logged (write-truth verified): APPLEGATE NATURALS* Uncured Turkey Pepperoni — card not captured.

Why verdict Logged (write-truth verified): APPLEGATE NATURALS* Uncured Turkey Pepperoni — 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 2.0s

1 · TTS said Got it, I logged APPLEGATE NATURALS Uncured Turkey Pepperoni (70 grams (70 g)).

2 · Card shown I logged APPLEGATE NATURALS Uncured Turkey Pepperoni (70 grams (70 g)) — let me know if that's not right.

3 · App data rows written created food_log_entry: APPLEGATE NATURALS* Uncured Turkey Pepperoni ×1 (70 grams (70 g)) 187 cal · 23.3g P · 0g C · 9.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-08-02T19:44:23.824Z

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

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

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

PASSshould log the entry"Track 3 cups spinach cooked down." (difficulty —)0.2s

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

Why verdict Logged (write-truth verified): Spinach — 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 Logged 3 cups spinach cooked down.

2 · Card shown Logged 3 cups spinach cooked down.

3 · App data rows written created food_log_entry: Spinach ×1 (3 cup) 21 cal · 2.6g P · 3.2g C · 0.4g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T19:44:35.136Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched the common-food list to "Spinach" at 90% confidence.
Matched your past food logs to "Cooked farro" at 82% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 1.3 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

PASSshould log the entry"Log 2 rice cakes with 1 tablespoon almond butter." (difficulty —)0.6s

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

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

1 · TTS said Logged 2 rice cakes and 1 tablespoon almond butter.

2 · Card shown Logged 2 rice cakes and 1 tablespoon almond butter.

3 · App data rows written created food_log_entry: Plain rice cakes ×1 (2 rice cakes) 70 cal · 1.4g P · 14.7g C · 0.5g F
created food_log_entry: Almond butter ×1 (1 tbsp) 98 cal · 3.4g P · 3g C · 9g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T19:44:46.835Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched the common-food list to "Plain rice cakes" at 90% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 1.6 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

PASSshould log the entry"Record 120 grams grilled zucchini." (difficulty —)0.2s

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

Why verdict Logged (write-truth verified): Zucchini — 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 Logged 120 grams grilled zucchini.

2 · Card shown Logged 120 grams grilled zucchini.

3 · App data rows written created food_log_entry: Zucchini ×1 (120 g) 20 cal · 1.4g P · 3.7g C · 0.4g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T19:44:58.135Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched the common-food list to "Zucchini" at 90% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 1.3 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

FAILshould log the entry"Add 1 cup beef chili." (difficulty —)0.2s

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

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

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

Pick every reason you think applies. Multiple boxes are allowed because one utterance can be wrong in more than one way. Use the note below for "Other" or extra detail.

Timing 0.2s

1 · TTS said What food did you have?

2 · Card shown What food did you have?

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T19:45:09.447Z

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

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

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

PASSshould log the entry"I ate 4 ounces turkey meatballs." (difficulty —)0.2s

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

Why verdict Logged (write-truth verified): Turkey meatballs — 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 Logged 4 ounces turkey meatballs.

2 · Card shown Logged 4 ounces turkey meatballs.

3 · App data rows written created food_log_entry: Turkey meatballs ×1 (4 oz) 210 cal · 20.4g P · 6.8g C · 11.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-08-02T19:45:20.758Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched the common-food list to "Turkey meatballs" at 90% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 1.3 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

PASSshould log the entry"Track 125 grams mango." (difficulty —)0.2s

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

Why verdict Logged (write-truth verified): Mango — 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 Logged 125 grams mango.

2 · Card shown Logged 125 grams mango.

3 · App data rows written created food_log_entry: Mango ×1 (125 g) 75 cal · 1g P · 18.8g C · 0.5g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T19:45:32.063Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched the common-food list to "Mango" at 90% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 1.1 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

PASSshould log the entry"Log one cup split pea soup." (difficulty —)2.1s

Verdict Expected LOG — should log the entry. PASS: Logged (write-truth verified): Split Pea Soup, Canned, Reduced Sodium, Prepared with Water or Ready-To Serve — card not captured.

Why verdict Logged (write-truth verified): Split Pea Soup, Canned, Reduced Sodium, Prepared with Water or Ready-To Serve — 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 2.1s

1 · TTS said Logged Split Pea Soup, Canned, Reduced Sodium, Prepared with Water or Ready-To Serve (one cup (245 g)) with an estimated macro range.

2 · Card shown Logged Split Pea Soup, Canned, Reduced Sodium, Prepared with Water or Ready-To Serve (one cup (245 g)) — the macros are an estimate since this food varies by brand.

3 · App data rows written created food_log_entry: Split Pea Soup, Canned, Reduced Sodium, Prepared with Water or Ready-To Serve ×1 (one cup (245 g)) 174 cal · 9.6g P · 28.9g C · 2.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-08-02T19:45:45.278Z

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

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

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

PASSshould log the entry"Record 3 ounces goat cheese." (difficulty —)0.2s

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

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

1 · TTS said Logged 3 ounces goat cheese.

2 · Card shown Logged 3 ounces goat cheese.

3 · App data rows written created food_log_entry: Goat cheese ×1 (3 oz) 310 cal · 18.4g P · 0.1g C · 25.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-08-02T19:45:56.575Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched the common-food list to "Goat cheese" at 90% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 1.3 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

PASSshould log the entry"Add 2 cups watermelon cubes." (difficulty —)0.2s

Verdict Expected LOG — should log the entry. 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 Logged 2 cups watermelon cubes.

2 · Card shown Logged 2 cups watermelon cubes.

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-08-02T19:46:07.907Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched the common-food list to "Watermelon" at 90% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 1.4 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

FAILshould log the entry"I had 1 cup cooked couscous." (difficulty —)2.7s

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

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

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

Pick every reason you think applies. Multiple boxes are allowed because one utterance can be wrong in more than one way. Use the note below for "Other" or extra detail.

Timing 2.7s

1 · TTS said What exact food and amount should I use for 1 cup cooked couscous? I did not log it yet because I could not safely finish that food log.

2 · Card shown What exact food and amount should I use for 1 cup cooked 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-08-02T19:46:21.781Z

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 entry"Track 6 ounces tilapia with lemon, no oil." (difficulty —)0.1s

Verdict Expected LOG — should log 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 I wasn't sure which food you meant to correct. Could you try again with a bit more detail?

2 · Card shown I wasn't sure which food you meant to correct. Could you try again with a bit more detail?

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T19:46:32.992Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched the common-food list to "Tilapia" at 90% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 1.6 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

PASSshould log the entry"Log 75 grams sour cream." (difficulty —)0.2s

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

Why verdict Logged (write-truth verified): Sour cream — 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 Logged 75 grams sour cream.

2 · Card shown Logged 75 grams sour cream.

3 · App data rows written created food_log_entry: Sour cream ×1 (75 g) 147 cal · 2.3g P · 4.2g C · 13.5g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T19:46:44.271Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched the common-food list to "Sour cream" at 90% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 1.3 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

PASSshould log the entry"Record 1 cup roasted Brussels sprouts." (difficulty —)0.2s

Verdict Expected LOG — should log the entry. 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 Logged 1 cup roasted brussels sprouts.

2 · Card shown Logged 1 cup roasted brussels sprouts.

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-08-02T19:46:55.610Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched the common-food list to "Brussels sprouts" at 90% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 1.6 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

PASSshould log the entry"Add half cup ricotta." (difficulty —)0.2s

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

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

1 · TTS said Logged half cup ricotta. Assumed 0.5 cup as the default serving. Tell me if you want a different amount.

2 · Card shown Logged half cup ricotta. Assumed 0.5 cup as the default serving. Tell me if you want a different amount.

3 · App data rows written created food_log_entry: Ricotta cheese ×1 (0.5 cup) 182 cal · 11.8g P · 7.4g C · 11.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-08-02T19:47:06.933Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched the common-food list to "Ricotta cheese" at 90% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 1.4 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

PASSshould log the entry"I ate 95 grams grapes." (difficulty —)0.2s

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

Why verdict Logged (write-truth verified): Grapes, Grapes — 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 Logged 95 grams grapes.

2 · Card shown Logged 95 grams grapes.

3 · App data rows written created food_log_entry: Grapes ×1 (95 g) 66 cal · 0.7g P · 17.2g 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-08-02T19:47:18.228Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched the common-food list to "Grapes" at 90% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 1.2 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

PASSshould log the entry"Track 4 ounces seitan." (difficulty —)0.2s

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

Why verdict Logged (write-truth verified): Seitan — 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 Logged 4 ounces seitan.

2 · Card shown Logged 4 ounces seitan.

3 · App data rows written created food_log_entry: Seitan ×1 (4 oz) 160 cal · 28g P · 6.7g C · 2.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-08-02T19:47:29.522Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched the common-food list to "Seitan" at 90% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 1.3 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

PASSshould log the entry"Log 2 cups minestrone soup." (difficulty —)0.2s

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

Why verdict Logged (write-truth verified): Minestrone soup — 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 Logged 2 cups minestrone soup.

2 · Card shown Logged 2 cups minestrone soup.

3 · App data rows written created food_log_entry: Minestrone soup ×1 (2 cup) 191 cal · 8.8g P · 27.4g C · 5.4g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T19:47:52.319Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched the common-food list to "Minestrone soup" at 90% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 1.5 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

FAILshould log the entry"Record 45 grams pita chips." (difficulty —)0.3s

Verdict Expected LOG — should log the entry. FAIL: WRITE-TRUTH FAIL — WRONG/MISSING item "45 grams pita chips" — no saved row with matching identity (rows: Potato Chips)

Why verdict WRITE-TRUTH FAIL — WRONG/MISSING item "45 grams pita chips" — no saved row with matching identity (rows: Potato Chips)

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 Logged Potato Chips (45 grams (45 g)) with an estimated macro range.

2 · Card shown Logged Potato Chips (45 grams (45 g)) — the macros are an estimate since this food varies by brand.

3 · App data rows written created food_log_entry: Potato Chips ×1 (45 grams (45 g)) 241 cal · 3.2g P · 23.9g C · 15.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-08-02T19:48:03.805Z

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

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

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

PASSshould log the entry"Add 1 large kiwi." (difficulty —)0.2s

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

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

2 · Card shown Logged 1 large kiwi.

3 · App data rows written created food_log_entry: Kiwi ×1 (1 kiwi) 42 cal · 0.8g P · 10.1g C · 0.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-08-02T19:48:15.163Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched the common-food list to "Kiwi" at 90% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 1.3 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

PASSshould log the entry"I had 3 ounces ham." (difficulty —)0.2s

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

Why verdict Logged (write-truth verified): Ham — 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 Logged 3 ounces ham.

2 · Card shown Logged 3 ounces ham.

3 · App data rows written created food_log_entry: Ham ×1 (3 oz) 123 cal · 17.9g P · 1.3g C · 4.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-08-02T19:48:26.449Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched the common-food list to "Ham" at 90% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 0.3 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

PASSshould log the entry"Track 1 cup egg whites." (difficulty —)0.2s

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

Why verdict Logged (write-truth verified): Egg whites — 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 Logged 1 cup egg whites.

2 · Card shown Logged 1 cup egg whites.

3 · App data rows written created food_log_entry: Egg whites ×1 (1 cup) 126 cal · 26.5g P · 1.7g C · 0.5g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T19:48:37.742Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched the common-food list to "Egg whites" at 90% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 1.5 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

PASSshould log the entry"Log 35 grams sunflower seeds." (difficulty —)0.2s

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

Why verdict Logged (write-truth verified): Sunflower seeds — 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 Logged 35 grams sunflower seeds.

2 · Card shown Logged 35 grams sunflower seeds.

3 · App data rows written created food_log_entry: Sunflower seeds ×1 (35 g) 204 cal · 7.3g P · 7g C · 18g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T19:48:49.059Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched the common-food list to "Sunflower seeds" at 90% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 1.5 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

FAILshould log the entry"Record 2 cups cauliflower rice." (difficulty —)3.9s

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

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

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

Pick every reason you think applies. Multiple boxes are allowed because one utterance can be wrong in more than one way. Use the note below for "Other" or extra detail.

Timing 3.9s

1 · TTS said Which type of cauliflower rice was it? There are several with different nutrition.

2 · Card shown Which type of cauliflower rice was it? There are several with different 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-08-02T19:49:04.070Z

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 entry"Add 5 ounces lamb chop, cooked weight." (difficulty —)3.2s

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

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

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

Pick every reason you think applies. Multiple boxes are allowed because one utterance can be wrong in more than one way. Use the note below for "Other" or extra detail.

Timing 3.2s

1 · TTS said I need to resolve cooked weight before I log this meal. What should I use for cooked weight?

2 · Card shown I need to resolve cooked weight before I log this meal. What should I use for cooked weight?

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T19:49:18.443Z

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

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

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

PASSshould log the entry"I ate 110 grams pineapple." (difficulty —)0.2s

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

Why verdict Logged (write-truth verified): Pineapple — 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 Logged 110 grams pineapple.

2 · Card shown Logged 110 grams pineapple.

3 · App data rows written created food_log_entry: Pineapple ×1 (110 g) 55 cal · 0.6g P · 14.4g 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-08-02T19:49:29.748Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched the common-food list to "Pineapple" at 90% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 1.4 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

PASSshould log the entry"Track 1 cup baked beans." (difficulty —)0.2s

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

Why verdict Logged (write-truth verified): Baked 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 Logged 1 cup baked beans.

2 · Card shown Logged 1 cup baked beans.

3 · App data rows written created food_log_entry: Baked beans ×1 (1 cup) 273 cal · 11.7g P · 56.2g C · 2.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-08-02T19:49:41.069Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched the common-food list to "Baked beans" at 90% confidence.
Matched your past food logs to "Black beans" at 82% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 1.5 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

PASSshould log the entry"Log a Chobani Zero Sugar vanilla cup." (difficulty —)0.5s

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

Why verdict Logged (write-truth verified): Zero Sugar Vanilla Yogurt — 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 Got it, I logged Zero Sugar Vanilla Yogurt — Chobani.

2 · Card shown I logged Zero Sugar Vanilla Yogurt — Chobani — let me know if that's not right.

3 · App data rows written created food_log_entry: Zero Sugar Vanilla Yogurt ×1 (cup) 120 cal · 15g P · 9g 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-08-02T19:49:52.710Z

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

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

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

PASSshould log the entry"I had a Quest chocolate chip cookie dough protein bar." (difficulty —)0.6s

Verdict Expected LOG — should log the entry. PASS: Logged (write-truth verified): Quest Chocolate Chip Cookie Dough Protein Bar — card not captured.

Why verdict Logged (write-truth verified): Quest Chocolate Chip Cookie Dough 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.6s

1 · TTS said Logged Quest Chocolate Chip Cookie Dough Protein Bar with an estimated macro range.

2 · Card shown Logged Quest Chocolate Chip Cookie Dough Protein Bar — the macros are an estimate since this food varies by brand.

3 · App data rows written created food_log_entry: Quest Chocolate Chip Cookie Dough Protein Bar ×1 (one) 190 cal · 21g P · 22g C · 9g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T19:50:04.492Z

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 entry"Record one Fairlife Core Power 26 gram vanilla shake." (difficulty —)1.4s

Verdict Expected LOG — should log the entry. FAIL: WRITE-TRUTH FAIL — IMPLAUSIBLE: 15 kcal is implausibly LOW for 1 count of Fairlife Core Power Elite Vanilla Protein Shake (typical 160-250 kcal [per-serving])

Why verdict WRITE-TRUTH FAIL — IMPLAUSIBLE: 15 kcal is implausibly LOW for 1 count of Fairlife Core Power Elite Vanilla Protein Shake (typical 160-250 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 1.4s

1 · TTS said Logged Fairlife Core Power Elite Vanilla Protein Shake (26 gram (26 g)) with an estimated macro range.

2 · Card shown Logged Fairlife Core Power Elite Vanilla Protein Shake (26 gram (26 g)) — the macros are an estimate since this food varies by brand.

3 · App data rows written created food_log_entry: Fairlife Core Power Elite Vanilla Protein Shake ×1 (26 gram (26 g)) 15 cal · 2.6g P · 0.5g 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-08-02T19:50:17.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 log the entry"Add a Starbucks grande flat white with whole milk." (difficulty —)5.2s

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

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

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

Pick every reason you think applies. Multiple boxes are allowed because one utterance can be wrong in more than one way. Use the note below for "Other" or extra detail.

Timing 5.2s

1 · TTS said What exact food and amount should I use for Whole milk? I did not log it yet because I could not safely finish that food log.

2 · Card shown What exact food and amount should I use for Whole milk? 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-08-02T19:50:33.308Z

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 entry"Track a Chipotle chicken bowl: white rice, black beans, mild salsa, cheese, lettuce." (difficulty —)2.8s

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

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

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

Pick every reason you think applies. Multiple boxes are allowed because one utterance can be wrong in more than one way. Use the note below for "Other" or extra detail.

Timing 2.8s

1 · TTS said What should I use for lettuce?

2 · Card shown What should I use for lettuce?

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T19:50:42.208Z

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 entry"Log a McDonalds Egg McMuffin." (difficulty —)5.4s

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

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

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

Pick every reason you think applies. Multiple boxes are allowed because one utterance can be wrong in more than one way. Use the note below for "Other" or extra detail.

Timing 5.4s

1 · TTS said What exact food and amount should I use for Egg? I did not log it yet because I could not safely finish that food log.

2 · Card shown What exact food and amount should I use for Egg? 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-08-02T19:51:03.727Z

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 entry"I ate a Taco Bell bean burrito." (difficulty —)2.7s

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

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

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

Pick every reason you think applies. Multiple boxes are allowed because one utterance can be wrong in more than one way. Use the note below for "Other" or extra detail.

Timing 2.7s

1 · TTS said What exact food and amount should I use for a taco bell bean burrito? I did not log it yet because I could not safely finish that food log.

2 · Card shown What exact food and amount should I use for a taco bell bean burrito? 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-08-02T19:51:17.560Z

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

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

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

PASSshould log the entry"Record one RXBAR blueberry protein bar." (difficulty —)0.5s

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

Why verdict Logged (write-truth verified): RXBAR Blueberry 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 Logged RXBAR Blueberry Protein Bar with an estimated macro range.

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

3 · App data rows written created food_log_entry: RXBAR Blueberry Protein Bar ×1 (1 bar) 210 cal · 12g P · 24g 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-08-02T19:51:29.194Z

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

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

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

PASSshould log the entry"Add a Premier Protein caramel shake." (difficulty —)1.1s

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

Why verdict Logged (write-truth verified): Caramel High Protein Shake — 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 Logged Caramel High Protein Shake — premier protein with an estimated macro range.

2 · Card shown Logged Caramel High Protein Shake — premier protein — the macros are an estimate since this food varies by brand.

3 · App data rows written created food_log_entry: Caramel High Protein Shake ×1 (1 portion (311.844 g)) 159 cal · 29.9g P · 1.9g C · 3.1g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T19:51:41.443Z

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 entry"Track one Dave’s Killer Bread thin-sliced Good Seed slice." (difficulty —)5.3s

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

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

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

Pick every reason you think applies. Multiple boxes are allowed because one utterance can be wrong in more than one way. Use the note below for "Other" or extra detail.

Timing 5.3s

1 · TTS said Was it plain, or did you have anything on it like butter or cream cheese? I did not log it yet because add-ons can change the nutrition.

2 · Card shown Was it plain, or did you have anything on it like butter or cream 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-08-02T19:51:49.638Z

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 entry"Log a Siggi’s strawberry skyr cup." (difficulty —)1.0s

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

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

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

Pick every reason you think applies. Multiple boxes are allowed because one utterance can be wrong in more than one way. Use the note below for "Other" or extra detail.

Timing 1.0s

1 · TTS said What food did you have?

2 · Card shown What food did you have?

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T19:52:21.613Z

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 entry"I had a Panera Fuji apple salad with chicken, full size." (difficulty —)1.7s

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

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

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

Pick every reason you think applies. Multiple boxes are allowed because one utterance can be wrong in more than one way. Use the note below for "Other" or extra detail.

Timing 1.7s

1 · TTS said Which full size should I use?

2 · Card shown Which full size 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-08-02T19:52:34.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)

FAILshould log the entry"Record one Celsius peach vibe can." (difficulty —)0.8s

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

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

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

Pick every reason you think applies. Multiple boxes are allowed because one utterance can be wrong in more than one way. Use the note below for "Other" or extra detail.

Timing 0.8s

1 · TTS said I couldn't find Record One Celsius Peach Vibe Packaged Food in my nutrition database. What exact name is on the package? I did not log it because I'd only be guessing the nutrition. If you prefer, tell me to log a generic packaged food.

2 · Card shown I couldn't find Record One Celsius Peach Vibe Packaged Food in my nutrition database. What exact name is on the package? I did not log it because I'd only be guessing the nutrition. If you prefer, 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-08-02T19:52:46.413Z

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 entry"Add a Kodiak Cakes protein waffle, one waffle." (difficulty —)2.2s

Verdict Expected LOG — should log the entry. FAIL: WRITE-TRUTH FAIL — WRONG item/product identity "Kodiak Cakes protein waffle" — saved row does not hit product alias (rows: Waffle, Plain, Birthday Cake Power Waffles With Sprinkles)

Why verdict WRITE-TRUTH FAIL — WRONG item/product identity "Kodiak Cakes protein waffle" — saved row does not hit product alias (rows: Waffle, Plain, Birthday Cake Power Waffles With Sprinkles)

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 Logged Birthday Cake Power Waffles With Sprinkles — KODIAK and Waffle, Plain. Assumed Birthday Cake Power Waffles With Sprinkles — KODIAK for "a Kodiak Cakes protein waffle" (best matching option). Tell me if that is wrong. Tell me if that is not right.

2 · Card shown Logged Birthday Cake Power Waffles With Sprinkles — KODIAK and Waffle, Plain. Assumed Birthday Cake Power Waffles With Sprinkles — KODIAK for "a Kodiak Cakes protein waffle" (best matching option). Tell me if that is wrong. Tell me if that is not right.

3 · App data rows written created food_log_entry: Birthday Cake Power Waffles With Sprinkles ×1 (1 waffle) 230 cal · 10g P · 27g C · 9g F
created food_log_entry: Waffle, Plain ×1 (1 small waffle) 149 cal · 3.5g P · 16.6g C · 7.5g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T19:52:59.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)

FAILshould log the entry"Track a Subway six inch turkey on wheat with provolone." (difficulty —)3.1s

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

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

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

Pick every reason you think applies. Multiple boxes are allowed because one utterance can be wrong in more than one way. Use the note below for "Other" or extra detail.

Timing 3.1s

1 · TTS said What exact food and amount should I use for a subway six inch turkey on wheat with provolone? I did not log it yet because I could not safely finish that food log.

2 · Card shown What exact food and amount should I use for a subway six inch turkey on wheat with provolone? 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-08-02T19:53:13.947Z

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 entry"Log one KIND dark chocolate nuts and sea salt bar." (difficulty —)0.4s

Verdict Expected LOG — should log the entry. FAIL: WRITE-TRUTH FAIL — WRONG item/product identity "KIND dark chocolate nuts" — saved row does not hit product alias (rows: No Cow Chocolate Sea Salt Bar, Dark chocolate)

Why verdict WRITE-TRUTH FAIL — WRONG item/product identity "KIND dark chocolate nuts" — saved row does not hit product alias (rows: No Cow Chocolate Sea Salt Bar, Dark chocolate)

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 Logged Dark chocolate and No Cow Chocolate Sea Salt Bar — No Cow. Assumed catalog default servings where you did not say an amount — tell me if that is not right.

2 · Card shown Logged Dark chocolate and No Cow Chocolate Sea Salt Bar — No Cow. 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: Dark chocolate ×1 (100 g) 550 cal · 5.1g P · 60g C · 32.2g F
created food_log_entry: No Cow Chocolate Sea Salt Bar ×1 (1 bar (60 g)) 210 cal · 20g P · 23g 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-08-02T19:53:25.529Z

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 entry"I ate a Trader Joe’s chicken tikka masala frozen meal." (difficulty —)5.4s

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

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

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

Pick every reason you think applies. Multiple boxes are allowed because one utterance can be wrong in more than one way. Use the note below for "Other" or extra detail.

Timing 5.4s

1 · TTS said What exact food and amount should I use for a trader joes chicken tikka masala frozen meal? I did not log it yet because I could not safely finish that food log.

2 · Card shown What exact food and amount should I use for a trader joes chicken tikka masala frozen meal? 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-08-02T19:53:42.082Z

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

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

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

PASSshould log the entry"Record one Oikos Triple Zero mixed berry yogurt." (difficulty —)0.8s

Verdict Expected LOG — should log the entry. PASS: Logged (write-truth verified): Mixed Berry Flavor Triple Zero Blended Greek Nonfat Yogurt — card not captured.

Why verdict Logged (write-truth verified): Mixed Berry Flavor Triple Zero Blended Greek Nonfat Yogurt — 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.8s

1 · TTS said Got it, I logged Mixed Berry Flavor Triple Zero Blended Greek Nonfat Yogurt — OIKOS.

2 · Card shown I logged Mixed Berry Flavor Triple Zero Blended Greek Nonfat Yogurt — OIKOS — let me know if that's not right.

3 · App data rows written created food_log_entry: Mixed Berry Flavor Triple Zero Blended Greek Nonfat Yogurt ×1 (1 cup) 101 cal · 15g P · 10.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-08-02T19:53:54.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 log the entry"Add a Wendy’s small chili." (difficulty —)2.7s

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

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

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

Pick every reason you think applies. Multiple boxes are allowed because one utterance can be wrong in more than one way. Use the note below for "Other" or extra detail.

Timing 2.7s

1 · TTS said What exact food and amount should I use for a wendys small chili? I did not log it yet because I could not safely finish that food log.

2 · Card shown What exact food and amount should I use for a wendys small 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-08-02T19:54:07.912Z

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

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

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

PASSshould log the entry"Track one Clif Builder chocolate mint bar." (difficulty —)0.5s

Verdict Expected LOG — should log the entry. PASS: Logged (write-truth verified): Builder'S Protein Chocolate Mint Bar — card not captured.

Why verdict Logged (write-truth verified): Builder'S Protein Chocolate Mint 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 Logged Builder'S Protein Chocolate Mint Bar — Clif Bar and Company with an estimated macro range.

2 · Card shown Logged Builder'S Protein Chocolate Mint Bar — Clif Bar and Company — the macros are an estimate since this food varies by brand.

3 · App data rows written created food_log_entry: Builder'S Protein Chocolate Mint Bar ×1 (1 BAR) 270 cal · 20g P · 30g C · 9g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T19:54:19.594Z

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 entry"Log a Sweetgreen harvest bowl." (difficulty —)2.7s

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

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

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

Pick every reason you think applies. Multiple boxes are allowed because one utterance can be wrong in more than one way. Use the note below for "Other" or extra detail.

Timing 2.7s

1 · TTS said What exact food and amount should I use for a sweetgreen harvest bowl? I did not log it yet because I could not safely finish that food log.

2 · Card shown What exact food and amount should I use for a sweetgreen harvest bowl? 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-08-02T19:54:33.438Z

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 entry"I had one Larabar apple pie bar." (difficulty —)0.5s

Verdict Expected LOG — should log the entry. FAIL: WRITE-TRUTH FAIL — IMPLAUSIBLE: 198 kcal is implausibly HIGH for 1 count of Apple Pie Fruit & Nut Bar (typical 60-130 kcal [per-serving])

Why verdict WRITE-TRUTH FAIL — IMPLAUSIBLE: 198 kcal is implausibly HIGH for 1 count of Apple Pie Fruit & Nut Bar (typical 60-130 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.5s

1 · TTS said Logged Apple Pie Fruit & Nut Bar — Larabar with an estimated macro range.

2 · Card shown Logged Apple Pie Fruit & Nut Bar — Larabar — the macros are an estimate since this food varies by brand.

3 · App data rows written created food_log_entry: Apple Pie Fruit & Nut Bar ×1 (1 bar (45 g)) 198 cal · 4.1g P · 24.8g C · 9.5g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T19:54:45.035Z

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 entry"Record a Dunkin medium iced coffee: cream plus sugar." (difficulty —)2.7s

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

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

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

Pick every reason you think applies. Multiple boxes are allowed because one utterance can be wrong in more than one way. Use the note below for "Other" or extra detail.

Timing 2.7s

1 · TTS said What exact food and amount should I use for a dunkin medium iced coffee cream plus sugar? I did not log it yet because I could not safely finish that food log.

2 · Card shown What exact food and amount should I use for a dunkin medium iced coffee cream plus sugar? 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-08-02T19:54:58.897Z

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 entry"Add a Kirkland protein bar chocolate brownie." (difficulty —)0.4s

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

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

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

Pick every reason you think applies. Multiple boxes are allowed because one utterance can be wrong in more than one way. Use the note below for "Other" or extra detail.

Timing 0.4s

1 · TTS said What food did you have?

2 · Card shown What food did you have?

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T19:55:10.428Z

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 entry"Track a Five Guys little cheeseburger." (difficulty —)3.0s

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

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

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

Pick every reason you think applies. Multiple boxes are allowed because one utterance can be wrong in more than one way. Use the note below for "Other" or extra detail.

Timing 3.0s

1 · TTS said What exact food and amount should I use for a five guys little cheeseburger? I did not log it yet because I could not safely finish that food log.

2 · Card shown What exact food and amount should I use for a five guys little cheeseburger? 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-08-02T19:55:24.602Z

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 entry"Log one Blue Diamond 100 calorie almond pack." (difficulty —)6.4s

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

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

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

Pick every reason you think applies. Multiple boxes are allowed because one utterance can be wrong in more than one way. Use the note below for "Other" or extra detail.

Timing 6.4s

1 · TTS said I couldn't find Blue Diamond 100 Calorie Almond Packaged Food in my nutrition database. What exact name is on the package? I did not log it because I'd only be guessing the nutrition. If you prefer, tell me to log a generic packaged food.

2 · Card shown I couldn't find Blue Diamond 100 Calorie Almond Packaged Food in my nutrition database. What exact name is on the package? I did not log it because I'd only be guessing the nutrition. If you prefer, 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-08-02T19:55:42.140Z

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 entry"I ate a Lean Cuisine herb roasted chicken meal." (difficulty —)3.6s

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

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

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

Pick every reason you think applies. Multiple boxes are allowed because one utterance can be wrong in more than one way. Use the note below for "Other" or extra detail.

Timing 3.6s

1 · TTS said What exact food and amount should I use for a lean cuisine herb roasted chicken meal? I did not log it yet because I could not safely finish that food log.

2 · Card shown What exact food and amount should I use for a lean cuisine herb roasted chicken meal? 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-08-02T19:55:56.896Z

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 entry"Record one Gatorade Zero 20 ounce bottle." (difficulty —)2.0s

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

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

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

Pick every reason you think applies. Multiple boxes are allowed because one utterance can be wrong in more than one way. Use the note below for "Other" or extra detail.

Timing 2.0s

1 · TTS said I couldn't find Record One Gatorade Zero 20 Ounce Packaged Food in my nutrition database. What exact name is on the package? I did not log it because I'd only be guessing the nutrition. If you prefer, tell me to log a generic packaged food.

2 · Card shown I couldn't find Record One Gatorade Zero 20 Ounce Packaged Food in my nutrition database. What exact name is on the package? I did not log it because I'd only be guessing the nutrition. If you prefer, 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-08-02T19:56:09.955Z

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 entry"Add a Shake Shack single ShackBurger." (difficulty —)2.7s

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

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

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

Pick every reason you think applies. Multiple boxes are allowed because one utterance can be wrong in more than one way. Use the note below for "Other" or extra detail.

Timing 2.7s

1 · TTS said What exact food and amount should I use for a shake shack single shackburger? I did not log it yet because I could not safely finish that food log.

2 · Card shown What exact food and amount should I use for a shake shack single shackburger? 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-08-02T19:56:23.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 log the entry"Track a Noosa lemon yogurt 8 ounce tub." (difficulty —)3.8s

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

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

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

Pick every reason you think applies. Multiple boxes are allowed because one utterance can be wrong in more than one way. Use the note below for "Other" or extra detail.

Timing 3.8s

1 · TTS said What food did you have?

2 · Card shown What food did you have?

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T19:56:38.748Z

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 entry"Log a Costco rotisserie chicken breast serving, 6 ounces." (difficulty —)5.4s

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

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

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

Pick every reason you think applies. Multiple boxes are allowed because one utterance can be wrong in more than one way. Use the note below for "Other" or extra detail.

Timing 5.4s

1 · TTS said What exact food and amount should I use for Chicken breast? I did not log it yet because I could not safely finish that food log.

2 · Card shown What exact food and amount should I use for Chicken breast? 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-08-02T19:57:06.767Z

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

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

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

PASSshould log the entry"I had a Jimmy Johns turkey tom unwich." (difficulty —)2.3s

Verdict Expected LOG — should log the entry. PASS: Logged (write-truth verified): Jimmy John's #4 Turkey Tom, Unwich — card not captured.

Why verdict Logged (write-truth verified): Jimmy John's #4 Turkey Tom, Unwich — 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 2.3s

1 · TTS said Got it, I logged Jimmy John's #4 Turkey Tom, Unwich.

2 · Card shown I logged Jimmy John's #4 Turkey Tom, Unwich — let me know if that's not right.

3 · App data rows written created food_log_entry: Jimmy John's #4 Turkey Tom, Unwich ×1 (a) 250 cal · 15g P · 5g C · 17g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T19:57:20.271Z

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

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

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

PASSshould log the entry"Record one Orgain creamy chocolate protein shake." (difficulty —)0.6s

Verdict Expected LOG — should log the entry. PASS: Logged (write-truth verified): ORGAIN Organic Protein Shake, Creamy Chocolate — card not captured.

Why verdict Logged (write-truth verified): ORGAIN Organic Protein Shake, Creamy Chocolate — 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 Logged ORGAIN Organic Protein Shake, Creamy Chocolate with an estimated macro range.

2 · Card shown Logged ORGAIN Organic Protein Shake, Creamy Chocolate — the macros are an estimate since this food varies by brand.

3 · App data rows written created food_log_entry: ORGAIN Organic Protein Shake, Creamy Chocolate ×1 (1 orgain creamy chocolate protein shake) 149 cal · 26.1g P · 14.1g C · 4.1g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T19:57:31.955Z

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 entry"Add a Nature Valley oats and honey two-bar pack." (difficulty —)2.9s

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

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

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

Pick every reason you think applies. Multiple boxes are allowed because one utterance can be wrong in more than one way. Use the note below for "Other" or extra detail.

Timing 2.9s

1 · TTS said I need to resolve honey two-bar pack before I log this meal. What should I use for honey two-bar pack?

2 · Card shown I need to resolve honey two-bar pack before I log this meal. What should I use for honey two-bar pack?

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T19:57:46.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 log the entry"Track a Whole Foods salmon avocado roll." (difficulty —)7.4s

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

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

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

Pick every reason you think applies. Multiple boxes are allowed because one utterance can be wrong in more than one way. Use the note below for "Other" or extra detail.

Timing 7.4s

1 · TTS said Which type of Whole Foods salmon avocado roll was it? There are several with different nutrition.

2 · Card shown Which type of Whole Foods salmon avocado roll was it? There are several with different 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-08-02T19:58:04.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 log the entry"Log one PopCorners sea salt snack bag." (difficulty —)1.2s

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

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

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

Pick every reason you think applies. Multiple boxes are allowed because one utterance can be wrong in more than one way. Use the note below for "Other" or extra detail.

Timing 1.2s

1 · TTS said What food did you have?

2 · Card shown What food did you have?

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T19:58:16.864Z

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

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

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

PASSshould log the entry"I ate a Chick-fil-A grilled chicken sandwich." (difficulty —)0.5s

Verdict Expected LOG — should log the entry. PASS: Logged (write-truth verified): Chick Fil A Grilled Chicken Sandwich — card not captured.

Why verdict Logged (write-truth verified): Chick Fil A Grilled Chicken Sandwich — 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 Logged Chick Fil A Grilled Chicken Sandwich with an estimated macro range.

2 · Card shown Logged Chick Fil A Grilled Chicken Sandwich — the macros are an estimate since this food varies by brand.

3 · App data rows written created food_log_entry: Chick Fil A Grilled Chicken Sandwich ×1 (assumed catalog serving (218 g)) 380 cal · 28g P · 43g C · 12g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T19:58:28.543Z

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

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

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

PASSshould log the entry"Record a Muscle Milk chocolate 14 ounce bottle." (difficulty —)1.0s

Verdict Expected LOG — should log the entry. PASS: Logged (write-truth verified): Non-Dairy Protein Shake Chocolate Zero Sugar 414ml Bottle — card not captured.

Why verdict Logged (write-truth verified): Non-Dairy Protein Shake Chocolate Zero Sugar 414ml Bottle — 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.0s

1 · TTS said Logged Non-Dairy Protein Shake Chocolate Zero Sugar 414ml Bottle — Muscle milk (1 bottle (1 bottle (414 g))) with an estimated macro range.

2 · Card shown Logged Non-Dairy Protein Shake Chocolate Zero Sugar 414ml Bottle — Muscle milk (1 bottle (1 bottle (414 g))) — the macros are an estimate since this food varies by brand.

3 · App data rows written created food_log_entry: Non-Dairy Protein Shake Chocolate Zero Sugar 414ml Bottle ×1 (1 bottle (1 bottle (414 g))) 170 cal · 24.8g P · 11.2g 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-08-02T19:58:40.676Z

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 entry"Add a Banza chickpea pasta serving, 2 ounces dry." (difficulty —)1.3s

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

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

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

Pick every reason you think applies. Multiple boxes are allowed because one utterance can be wrong in more than one way. Use the note below for "Other" or extra detail.

Timing 1.3s

1 · TTS said I need to resolve 2 ounces dry before I log this meal. What should I use for 2 ounces dry?

2 · Card shown I need to resolve 2 ounces dry before I log this meal. What should I use for 2 ounces dry?

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T19:58:53.151Z

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 entry"Track one Halo Top vanilla bean pint, half the pint." (difficulty —)3.4s

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

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

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

Pick every reason you think applies. Multiple boxes are allowed because one utterance can be wrong in more than one way. Use the note below for "Other" or extra detail.

Timing 3.4s

1 · TTS said What should I use for one Halo Top vanilla bean pint? I did not log it yet because I could not match it safely.

2 · Card shown What should I use for one Halo Top vanilla bean pint? I did not log it yet because I could not match it 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-08-02T19:59:07.713Z

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 entry"Log my turkey sandwich: two slices rye, 4 ounces turkey, one slice Swiss, mustard." (difficulty —)1.3s

Verdict Expected LOG — should log the entry. FAIL: WRITE-TRUTH FAIL — WRONG/MISSING item "rye bread" — no saved row with matching identity (rows: Turkey Sandwich); WRONG/MISSING item "swiss" — no saved row with matching identity (rows: Turkey Sandwich); WRONG/MISSING item "mustard" — no saved row with matching identity (rows: Turkey Sandwich)

Why verdict WRITE-TRUTH FAIL — WRONG/MISSING item "rye bread" — no saved row with matching identity (rows: Turkey Sandwich); WRONG/MISSING item "swiss" — no saved row with matching identity (rows: Turkey Sandwich); WRONG/MISSING item "mustard" — no saved row with matching identity (rows: Turkey Sandwich)

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 Logged Home default Turkey Sandwich. Using your recent Home default Turkey Sandwich history. Tell me if that is wrong.

2 · Card shown Logged Home default Turkey Sandwich. Using your recent Home default Turkey Sandwich history. Tell me if that is wrong.

3 · App data rows written created food_log_entry: Turkey Sandwich ×1 (sandwich) 380 cal · 26g P · 38g C · 12g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T19:59:20.626Z

6 · Why this food The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 3.4 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

FAILshould log the entry"Dinner bowl: 150 grams rice, 120 grams chicken, 80 grams avocado, salsa, 30 grams cheese." (difficulty —)3.4s

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

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

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

Pick every reason you think applies. Multiple boxes are allowed because one utterance can be wrong in more than one way. Use the note below for "Other" or extra detail.

Timing 3.4s

1 · TTS said I can help you log that dinner bowl. For items like salsa and cheese, the app needs a specific brand or type to find accurate nutrition. Could you tell me what kind of cheese you used (e.g., cheddar, mozzarella, feta) and the brand or style of the salsa?

2 · Card shown I can help you log that dinner bowl. For items like salsa and cheese, the app needs a specific brand or type to find accurate nutrition. Could you tell me what kind of cheese you used (e.g., cheddar, mozzarella, feta) and the brand or style of the salsa?

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T19:59:35.367Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 4.3 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

FAILshould log the entry"Add homemade smoothie: banana, 1 cup whole milk, 30 grams peanut butter, and a scoop whey." (difficulty —)0.5s

Verdict Expected LOG — should log the entry. FAIL: WRITE-TRUTH FAIL — WRONG/MISSING item "whole milk" — no saved row with matching identity (rows: Banana, Homemade Smoothie); WRONG/MISSING item "peanut butter" — no saved row with matching identity (rows: Banana, Homemade Smoothie); WRONG/MISSING item "whey" — no saved row with matching identity (rows: Banana, Homemade Smoothie)

Why verdict WRITE-TRUTH FAIL — WRONG/MISSING item "whole milk" — no saved row with matching identity (rows: Banana, Homemade Smoothie); WRONG/MISSING item "peanut butter" — no saved row with matching identity (rows: Banana, Homemade Smoothie); WRONG/MISSING item "whey" — no saved row with matching identity (rows: Banana, Homemade Smoothie)

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 Logged Homemade Smoothie. Includes one banana, 1 cup whole milk, 30 grams peanut butter, and a scoop whey.

2 · Card shown Logged Homemade Smoothie. Includes one banana, 1 cup whole milk, 30 grams peanut butter, and a scoop whey.

3 · App data rows written created food_log_entry: Homemade Smoothie ×1 (serving) 540 cal · 41.5g P · 45.7g C · 24.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: Whole milk ×1 (1 cup) 149 cal · 7.8g P · 11.7g C · 8.1g F
created food_log_entry: Peanut butter ×1 (30 g) 176 cal · 7.5g P · 5.9g C · 15.1g F
created food_log_entry: Whey protein powder ×1 (1 scoop) 110 cal · 24.9g P · 1g C · 0.5g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T19:59:47.472Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 4.2 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

UNVERIFIEDunclassifiedshould log the entry"Record my omelet: 2 eggs, 50 grams mushrooms, 30 grams feta, spinach." (difficulty —)3.1s

Verdict Expected LOG — should log the entry. UNVERIFIED: UNVERIFIABLE — no evidence captured (chat claims logged but no cloud/local food write captured for this turn).

Why verdict UNVERIFIABLE — no evidence captured (chat claims logged but no cloud/local food write captured for this turn).

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

1 · TTS said Logged Omelet. Includes 2 eggs, 50 grams mushrooms, 30 grams feta, and Spinach.

2 · Card shown Logged Omelet. Includes 2 eggs, 50 grams mushrooms, 30 grams feta, and Spinach.

3 · App data rows written created food_log_entry: Omelet ×1 (serving) 240 cal · 19.4g P · 4.7g C · 16.2g F
created food_log_entry: Egg ×1 (2 eggs) 143 cal · 12.6g P · 0.7g C · 9.5g F
created food_log_entry: Mushrooms ×1 (50 g) 11 cal · 1.6g P · 1.7g C · 0.2g F
created food_log_entry: Feta cheese ×1 (30 g) 79 cal · 4.3g P · 1.2g C · 6.4g 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-08-02T19:59:56.804Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 3.3 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

FAILshould log the entry"Track tacos: three corn tortillas, 5 ounces carne asada, onions, cilantro, and salsa verde." (difficulty —)2.4s

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

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

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

Pick every reason you think applies. Multiple boxes are allowed because one utterance can be wrong in more than one way. Use the note below for "Other" or extra detail.

Timing 2.4s

1 · TTS said What should I use for 5 ounces carne asada?

2 · Card shown What should I use for 5 ounces carne asada?

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T20:00:14.760Z

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 entry"Log salad: 4 cups arugula, 120 grams grilled shrimp, 20 grams walnuts, balsamic." (difficulty —)0.5s

Verdict Expected LOG — should log the entry. FAIL: WRITE-TRUTH FAIL — WRONG/MISSING item "grilled shrimp" — no saved row with matching identity (rows: Arugula, Salad); WRONG/MISSING item "walnuts" — no saved row with matching identity (rows: Arugula, Salad); WRONG/MISSING item "balsamic" — no saved row with matching identity (rows: Arugula, Salad)

Why verdict WRITE-TRUTH FAIL — WRONG/MISSING item "grilled shrimp" — no saved row with matching identity (rows: Arugula, Salad); WRONG/MISSING item "walnuts" — no saved row with matching identity (rows: Arugula, Salad); WRONG/MISSING item "balsamic" — no saved row with matching identity (rows: Arugula, Salad)

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 Logged Salad. Includes 4 cups arugula, 120 grams grilled shrimp, 20 grams walnuts, and Balsamic vinegar.

2 · Card shown Logged Salad. Includes 4 cups arugula, 120 grams grilled shrimp, 20 grams walnuts, and Balsamic vinegar.

3 · App data rows written created food_log_entry: Salad ×1 (serving) 284 cal · 34g P · 8.6g C · 14g F
created food_log_entry: Arugula ×1 (4 cup) 20 cal · 2.1g P · 3g C · 0.6g F
created food_log_entry: Shrimp ×1 (120 g) 119 cal · 28.8g P · 0.2g C · 0.4g F
created food_log_entry: Walnuts ×1 (20 g) 131 cal · 3g P · 2.7g C · 13g F
created food_log_entry: Balsamic vinegar ×1 (16 g) 14 cal · 0.1g P · 2.7g 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-08-02T20:00:26.805Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 4.1 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

UNVERIFIEDunclassifiedshould log the entry"I had ramen: noodles, broth, one egg, pork belly, and corn." (difficulty —)2.8s

Verdict Expected LOG — should log the entry. UNVERIFIED: Informational non-gating row (excluded from pass/fail tallies).

Why verdict Informational non-gating row (excluded from pass/fail tallies).

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

1 · TTS said What should I use for broth?

2 · Card shown What should I use for broth?

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T20:00:34.458Z

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 log the entry"Record burrito bowl: brown rice, pinto beans, steak, guacamole, fajita veggies, and queso." (difficulty —)3.4s

Verdict Expected LOG — should log the entry. UNVERIFIED: Informational non-gating row (excluded from pass/fail tallies).

Why verdict Informational non-gating row (excluded from pass/fail tallies).

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

1 · TTS said What should I use for fajita veggies?

2 · Card shown What should I use for fajita veggies?

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T20:00:48.530Z

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 log the entry"Add pasta dinner: 2 cups spaghetti, meat sauce, parmesan, and a side salad." (difficulty —)4.4s

Verdict Expected LOG — should log the entry. UNVERIFIED: UNVERIFIABLE — no saved row captured (untagged / lossy) — resolve via the notes.utterance_trace_id join. App claim not credited; resolve via the notes.utterance_trace_id join.

Why verdict UNVERIFIABLE — no saved row captured (untagged / lossy) — resolve via the notes.utterance_trace_id join. App claim not credited; resolve via the notes.utterance_trace_id join.

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

1 · TTS said Logging your pasta dinner: 2 cups spaghetti, meat sauce, parmesan, and a side salad — still looking up the nutrition details; they'll appear in your log shortly.

2 · Card shown Logging your pasta dinner: 2 cups spaghetti, meat sauce, parmesan, and a side salad — still looking up the nutrition details; they'll appear in your log shortly.

3 · App data rows written pending_created food_log_entry: pasta dinner: 2 cups spaghetti, meat sauce, parmesan, and a side salad (pending)

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T20:01:25.714Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 4.5 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

UNVERIFIEDunclassifiedshould log the entry"Track breakfast plate: two waffles, maple syrup, bacon, and strawberries." (difficulty —)4.5s

Why verdict UNVERIFIABLE — no saved row captured (untagged / lossy) — resolve via the notes.utterance_trace_id join. App claim not credited; resolve via the notes.utterance_trace_id join.

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 Logging your Track breakfast plate: two waffles, maple syrup, bacon, and strawberries — still looking up the nutrition details; they'll appear in your log shortly.

2 · Card shown Logging your Track breakfast plate: two waffles, maple syrup, bacon, and strawberries — still looking up the nutrition details; they'll appear in your log shortly.

3 · App data rows written pending_created food_log_entry: Track breakfast plate: two waffles, maple syrup, bacon, and strawberries (pending)

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T20:01:32.908Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 3.7 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

UNVERIFIEDunclassifiedshould log the entry"Log poke bowl with sushi rice, tuna, edamame, cucumber, avocado, spicy mayo." (difficulty —)2.6s

Verdict Expected LOG — should log the entry. UNVERIFIED: Informational non-gating row (excluded from pass/fail tallies).

Why verdict Informational non-gating row (excluded from pass/fail tallies).

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 Which tuna should I use?

2 · Card shown Which tuna 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-08-02T20:01:46.169Z

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 log the entry"I ate chicken curry plus 1.5 cups basmati rice plus naan." (difficulty —)3.1s

Verdict Expected LOG — should log the entry. UNVERIFIED: Informational non-gating row (excluded from pass/fail tallies).

Why verdict Informational non-gating row (excluded from pass/fail tallies).

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

1 · TTS said What exact food and amount should I use for chicken curry plus 1.5 cups basmati rice plus naan? I did not log it yet because I could not safely finish that food log.

2 · Card shown What exact food and amount should I use for chicken curry plus 1.5 cups basmati rice plus naan? 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-08-02T20:01:59.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 entry"Record burger night: bun, 6 ounce beef patty, cheddar, ketchup, and fries." (difficulty —)2.0s

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

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

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

Pick every reason you think applies. Multiple boxes are allowed because one utterance can be wrong in more than one way. Use the note below for "Other" or extra detail.

Timing 2.0s

1 · TTS said What should I use for bun?

2 · Card shown What should I use for bun?

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T20:02:14.163Z

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 log the entry"Add Greek plate: chicken souvlaki, pita, tzatziki, rice, and Greek salad." (difficulty —)6.6s

Verdict Expected LOG — should log the entry. UNVERIFIED: Informational non-gating row (excluded from pass/fail tallies).

Why verdict Informational non-gating row (excluded from pass/fail tallies).

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

1 · TTS said What should I use for greek?

2 · Card shown What should I use for greek?

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T20:02:27.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)

UNVERIFIEDunclassifiedshould log the entry"Track nachos: tortilla chips, black beans, chicken, queso, jalapenos, sour cream." (difficulty —)2.9s

Verdict Expected LOG — should log the entry. UNVERIFIED: Informational non-gating row (excluded from pass/fail tallies).

Why verdict Informational non-gating row (excluded from pass/fail tallies).

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 What should I use for queso?

2 · Card shown What should I use for queso?

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T20:02:44.771Z

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 log the entry"Log homemade chili: beef, kidney beans, tomato, onion, cheddar." (difficulty —)2.3s

Verdict Expected LOG — should log the entry. UNVERIFIED: Informational non-gating row (excluded from pass/fail tallies).

Why verdict Informational non-gating row (excluded from pass/fail tallies).

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

1 · TTS said Which kidney beans should I use?

2 · Card shown Which kidney beans 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-08-02T20:03:03.985Z

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 entry"I had sushi: 6 salmon avocado pieces and miso soup." (difficulty —)6.8s

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

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

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

Pick every reason you think applies. Multiple boxes are allowed because one utterance can be wrong in more than one way. Use the note below for "Other" or extra detail.

Timing 6.8s

1 · TTS said What should I use for miso?

2 · Card shown What should I use for miso?

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T20:03:21.560Z

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 log the entry"Record breakfast burrito: tortilla, eggs, potatoes, chorizo, cheese, and salsa." (difficulty —)1.4s

Verdict Expected LOG — should log the entry. UNVERIFIED: Informational non-gating row (excluded from pass/fail tallies).

Why verdict Informational non-gating row (excluded from pass/fail tallies).

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

1 · TTS said Logged Cheese Pizza Slice. Using your recent Cheese Pizza Slice history. Tell me if that is wrong.

2 · Card shown Logged Cheese Pizza Slice. Using your recent Cheese Pizza Slice history. Tell me if that is wrong.

3 · App data rows written created food_log_entry: Cheese Pizza Slice ×1 (slice) 570 cal · 24g P · 64g 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-08-02T20:03:34.973Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 3.8 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

UNVERIFIEDunclassifiedshould log the entry"Add Cobb salad: chicken, egg, bacon, avocado, blue cheese, ranch." (difficulty —)2.4s

Verdict Expected LOG — should log the entry. UNVERIFIED: Informational non-gating row (excluded from pass/fail tallies).

Why verdict Informational non-gating row (excluded from pass/fail tallies).

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 What should I use for ranch?

2 · Card shown What should I use for ranch?

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T20:03:43.147Z

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 log the entry"Track falafel bowl: hummus, tabbouleh, pita, cucumbers, tahini." (difficulty —)2.7s

Verdict Expected LOG — should log the entry. UNVERIFIED: Informational non-gating row (excluded from pass/fail tallies).

Why verdict Informational non-gating row (excluded from pass/fail tallies).

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 Logged Falafel Bowl. Includes Hummus, Tabbouleh, Pita bread, Cucumber, and Tahini.

2 · Card shown Logged Falafel Bowl. Includes Hummus, Tabbouleh, Pita bread, Cucumber, and Tahini.

3 · App data rows written created food_log_entry: Falafel Bowl ×1 (serving) 638 cal · 19.3g P · 70g C · 34g F
created food_log_entry: Hummus ×1 (100 g) 166 cal · 7.9g P · 14.3g C · 9.6g F
created food_log_entry: Tabbouleh ×1 (1 cup) 203 cal · 2.6g P · 15.5g C · 15.5g F
created food_log_entry: Pita bread ×1 (60 g) 165 cal · 5.5g P · 33.4g C · 0.7g F
created food_log_entry: Cucumber ×1 (100 g) 15 cal · 0.7g P · 3.6g C · 0.1g F
created food_log_entry: Tahini ×1 (15 g) 89 cal · 2.6g P · 3.2g 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-08-02T20:03:56.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 log the entry"Log pho: beef, rice noodles, broth, bean sprouts, hoisin." (difficulty —)3.1s

Verdict Expected LOG — should log the entry. UNVERIFIED: Informational non-gating row (excluded from pass/fail tallies).

Why verdict Informational non-gating row (excluded from pass/fail tallies).

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

1 · TTS said What should I use for broth?

2 · Card shown What should I use for broth?

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T20:04:10.371Z

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 entry"I ate enchiladas: two chicken enchiladas, rice, beans, and sour cream." (difficulty —)1.9s

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

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

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

Pick every reason you think applies. Multiple boxes are allowed because one utterance can be wrong in more than one way. Use the note below for "Other" or extra detail.

Timing 1.9s

1 · TTS said What should I use for two chicken enchiladas?

2 · Card shown What should I use for two chicken enchiladas?

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T20:04:24.309Z

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 log the entry"Record Thanksgiving plate: turkey, stuffing, mashed potatoes, gravy, green beans, cranberry sauce." (difficulty —)2.0s

Verdict Expected LOG — should log the entry. UNVERIFIED: Informational non-gating row (excluded from pass/fail tallies).

Why verdict Informational non-gating row (excluded from pass/fail tallies).

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 What should I use for stuffing?

2 · Card shown What should I use for stuffing?

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T20:04:37.770Z

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 log the entry"Add Mediterranean wrap: lavash, turkey, hummus, cucumber, tomato, feta." (difficulty —)0.7s

Verdict Expected LOG — should log the entry. UNVERIFIED: Informational non-gating row (excluded from pass/fail tallies).

Why verdict Informational non-gating row (excluded from pass/fail tallies).

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 Logged Mediterranean Wrap. Includes Lavash, Turkey breast, Hummus, Cucumber, one tomato, and Feta cheese.

2 · Card shown Logged Mediterranean Wrap. Includes Lavash, Turkey breast, Hummus, Cucumber, one tomato, and Feta cheese.

3 · App data rows written created food_log_entry: Mediterranean Wrap ×1 (serving) 740 cal · 57.4g P · 54.8g C · 33.5g F
created food_log_entry: Lavash ×1 (50 g) 138 cal · 4.5g P · 28g C · 0.6g F
created food_log_entry: Turkey breast ×1 (100 g) 135 cal · 29g P · 0g C · 1.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
created food_log_entry: Tomato ×1 (1 tomato) 22 cal · 1.1g P · 4.8g C · 0.2g F
created food_log_entry: Feta cheese ×1 (100 g) 264 cal · 14.2g P · 4.1g C · 21.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-08-02T20:04:55.195Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched the common-food list to "Lavash" at 90% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 4.4 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

UNVERIFIEDunclassifiedshould log the entry"Track loaded baked potato: chili, cheddar, sour cream, scallions." (difficulty —)1.1s

Verdict Expected LOG — should log the entry. UNVERIFIED: Informational non-gating row (excluded from pass/fail tallies).

Why verdict Informational non-gating row (excluded from pass/fail tallies).

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 Which chili should I use?

2 · Card shown Which chili 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-08-02T20:05:02.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)

UNVERIFIEDunclassifiedshould log the entry"Log acai bowl: acai base, banana, granola, almond butter, coconut." (difficulty —)6.0s

Verdict Expected LOG — should log the entry. UNVERIFIED: Informational non-gating row (excluded from pass/fail tallies).

Why verdict Informational non-gating row (excluded from pass/fail tallies).

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

1 · TTS said What should I use for acai base?

2 · Card shown What should I use for acai base?

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T20:05:14.689Z

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 log the entry"I had bibimbap: rice, beef, egg, spinach, carrots, gochujang." (difficulty —)0.7s

Verdict Expected LOG — should log the entry. UNVERIFIED: Informational non-gating row (excluded from pass/fail tallies).

Why verdict Informational non-gating row (excluded from pass/fail tallies).

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 Logged Bibimbap. Includes Cooked white rice, Beef, one egg, Spinach, Baby carrots, and Gochujang.

2 · Card shown Logged Bibimbap. Includes Cooked white rice, Beef, one egg, Spinach, Baby carrots, and Gochujang.

3 · App data rows written created food_log_entry: Bibimbap ×1 (serving) 466 cal · 33g P · 38.6g C · 18.4g F
created food_log_entry: Cooked white rice ×1 (100 g) 130 cal · 2.7g P · 28g C · 0.3g F
created food_log_entry: Beef ×1 (85 g) 213 cal · 22.1g P · 0g C · 12.8g F
created food_log_entry: Egg ×1 (1 egg) 72 cal · 6.3g P · 0.4g C · 4.8g F
created food_log_entry: Spinach ×1 (30 g) 7 cal · 0.9g P · 1.1g C · 0.1g F
created food_log_entry: Baby carrots ×1 (10 g) 4 cal · 0.1g P · 0.8g C · 0g F
created food_log_entry: Gochujang ×1 (18 g) 40 cal · 0.9g P · 8.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-08-02T20:05:31.311Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched the common-food list to "Cooked white rice" at 90% confidence.
Matched your saved foods and aliases to "spinach" at 90% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 3.3 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

UNVERIFIEDunclassifiedshould log the entry"Record tuna melt: sourdough, tuna salad, cheddar, tomato, and side chips." (difficulty —)5.6s

Verdict Expected LOG — should log the entry. UNVERIFIED: Informational non-gating row (excluded from pass/fail tallies).

Why verdict Informational non-gating row (excluded from pass/fail tallies).

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

Pick every reason you think applies. Multiple boxes are allowed because one utterance can be wrong in more than one way. Use the note below for "Other" or extra detail.

Timing 5.6s

1 · TTS said Which tuna salad should I use?

2 · Card shown Which tuna salad 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-08-02T20:05:43.844Z

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 log the entry"Add antipasto plate: salami, mozzarella, olives, peppers, crackers." (difficulty —)3.3s

Verdict Expected LOG — should log the entry. UNVERIFIED: Informational non-gating row (excluded from pass/fail tallies).

Why verdict Informational non-gating row (excluded from pass/fail tallies).

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

1 · TTS said Which salami should I use?

2 · Card shown Which salami 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-08-02T20:06:00.415Z

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 log the entry"Track breakfast bowl: oats, protein powder, blueberries, chia, and honey." (difficulty —)1.4s

Verdict Expected LOG — should log the entry. UNVERIFIED: Informational non-gating row (excluded from pass/fail tallies).

Why verdict Informational non-gating row (excluded from pass/fail tallies).

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

1 · TTS said Logged Whey protein powder. Using your recent Whey protein powder history. Tell me if that is wrong.

2 · Card shown Logged Whey protein powder. Using your recent Whey protein powder history. Tell me if that is wrong.

3 · App data rows written created food_log_entry: Whey protein powder ×1 (1 scoop) 110 cal · 24.9g P · 1g C · 0.5g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T20:06:20.652Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched the common-food list to "Protein powder" at 90% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 4.9 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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 cereal." (difficulty —)1.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 1.2s

1 · TTS said Did you have milk, yogurt, fruit, or honey with the cereal or granola? I did not log it yet because add-ons can change the nutrition.

2 · Card shown Did you have milk, yogurt, fruit, or honey with the cereal or granola? 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-08-02T20:06:42.585Z

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 some pasta." (difficulty —)3.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 3.5s

1 · TTS said How much some pasta did you have?

2 · Card shown How much some pasta did you have?

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T20:06:57.216Z

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 chicken." (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 How much should I log for Chicken breast? I did not log it yet because the amount was not clear.

2 · Card shown How much should I log for Chicken breast? 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-08-02T20:07:08.446Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched the common-food list to "Chicken breast" at 90% confidence.
Matched your past food logs to "Chicken breast" at 82% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 2.2 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

PASSshould ask a clarifying question"Record a smoothie." (difficulty —)1.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 1.1s

1 · TTS said Which type of smoothie was it? There are several with different nutrition.

2 · Card shown Which type of smoothie was it? There are several with different 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-08-02T20:07:20.706Z

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 curry." (difficulty —)0.8s

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

1 · TTS said How much curry did you have?

2 · Card shown How much curry did you have?

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T20:07:32.660Z

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 coffee." (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 How much should I log for Coffee? I did not log it yet because the amount was not clear.

2 · Card shown How much should I log for Coffee? 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-08-02T20:07:43.942Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched the common-food list to "Coffee" at 90% confidence.
Matched your past food logs to "Coffee" at 82% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 2.0 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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 sandwich." (difficulty —)0.8s

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

1 · TTS said Which type of sandwich was it? There are several with different nutrition.

2 · Card shown Which type of sandwich was it? There are several with different 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-08-02T20:07:55.894Z

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 soup." (difficulty —)0.8s

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

1 · TTS said How much soup did you have?

2 · Card shown How much soup did you have?

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T20:08:07.838Z

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"Record a protein shake." (difficulty —)3.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 3.9s

1 · TTS said I couldn't find Record A Protein Protein Shake in my nutrition database. What exact name is on the package? I did not log it because I'd only be guessing the nutrition. If you prefer, tell me to log a generic protein shake.

2 · Card shown I couldn't find Record A Protein Protein Shake in my nutrition database. What exact name is on the package? I did not log it because I'd only be guessing the nutrition. If you prefer, 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-08-02T20:08:22.928Z

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 salad." (difficulty —)1.0s

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

1 · TTS said Got it, I logged salad.

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

3 · App data rows written created food_log_entry: Salad ×1 (serving) 101 cal · 2.1g P · 11.9g C · 5.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-08-02T20:08:35.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)

PASSshould ask a clarifying question"Log leftovers." (difficulty —)0.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 0.7s

1 · TTS said What exact food and amount should I use for leftovers? I did not log it yet because I could not safely finish that food log.

2 · Card shown What exact food and amount should I use for leftovers? 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-08-02T20:08:46.864Z

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 ate the usual snack." (difficulty —)0.1s

Verdict Expected CLARIFY — should ask a clarifying question. FAIL: WRONG item vs seeded default/key — WRONG/MISSING item "usual snack" — no saved row with matching identity (rows: Coffee)

Why verdict WRONG item vs seeded default/key — WRONG/MISSING item "usual snack" — no saved row with matching identity (rows: Coffee)

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

2 · Card shown Logged Coffee. Using your recent Coffee history. Tell me if that is wrong.

3 · App data rows written created food_log_entry: Coffee ×1 (cup) 5 cal · 0g 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-08-02T20:08:58.130Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 0.2 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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 rice." (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 How much should I log for Cooked white rice? I did not log it yet because the amount was not clear.

2 · Card shown How much should I log for Cooked white rice? 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-08-02T20:09:09.454Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched the common-food list to "Cooked white rice" at 90% confidence.
Matched your past food logs to "Cooked white rice" at 82% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 2.1 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

PASSshould ask a clarifying question"Record noodles." (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 How much noodles did you have?

2 · Card shown How much noodles did you have?

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T20:09:22.519Z

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 slice." (difficulty —)0.8s

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

1 · TTS said I couldn't find Track A Bread Slice in my nutrition database. What exact name is on the package? I did not log it because I'd only be guessing the nutrition. If you prefer, tell me to log a generic bread.

2 · Card shown I couldn't find Track A Bread Slice in my nutrition database. What exact name is on the package? I did not log it because I'd only be guessing the nutrition. If you prefer, tell me to log a generic bread.

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T20:09:34.457Z

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 dip." (difficulty —)1.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 1.0s

1 · TTS said What exact food and amount should I use for dip? I did not log it yet because I could not safely finish that food log.

2 · Card shown What exact food and amount should I use for dip? 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-08-02T20:09:46.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)

PASSshould ask a clarifying question"I had a latte." (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 Which type of latte was it? There are several with different nutrition.

2 · Card shown Which type of latte was it? There are several with different 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-08-02T20:09:58.629Z

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 one serving of chips." (difficulty —)1.3s

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

1 · TTS said Logged Potato Chips with an estimated macro range.

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

3 · App data rows written created food_log_entry: Potato Chips ×1 (ounce) 150 cal · 2g P · 15g 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-08-02T20:10:11.030Z

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"Record dinner." (difficulty —)0.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 0.6s

1 · TTS said What exact food and amount should I use for dinner? I did not log it yet because I could not safely finish that food log.

2 · Card shown What exact food and amount should I use 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-08-02T20:10:22.757Z

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 sauce." (difficulty —)1.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 1.2s

1 · TTS said How much sauce did you have?

2 · Card shown How much sauce did you have?

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T20:10:35.127Z

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 a bowl from Chipotle." (difficulty —)1.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 1.1s

1 · TTS said What food did you have?

2 · Card shown What food did you have?

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T20:10:58.912Z

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 ate my meal prep." (difficulty —)0.3s

Verdict Expected CLARIFY — should ask a clarifying question. FAIL: WRONG item vs seeded default/key — WRONG/MISSING item "meal prep" — no saved row with matching identity (rows: Chicken Salad Meal)

Why verdict WRONG item vs seeded default/key — WRONG/MISSING item "meal prep" — no saved row with matching identity (rows: Chicken Salad Meal)

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 Logged Home default Chicken Salad Meal. Using your recent Home default Chicken Salad Meal history. Tell me if that is wrong.

2 · Card shown Logged Home default Chicken Salad Meal. Using your recent Home default Chicken Salad Meal history. Tell me if that is wrong.

3 · App data rows written created food_log_entry: Chicken Salad Meal ×1 (serving) 410 cal · 38g P · 16g C · 18g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T20:11:10.360Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 2.3 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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 scoop." (difficulty —)0.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 0.7s

1 · TTS said What exact food and amount should I use for a scoop? I did not log it yet because I could not safely finish that food log.

2 · Card shown What exact food and amount should I use for a scoop? 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-08-02T20:11:22.223Z

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"Record cereal with milk." (difficulty —)1.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 1.7s

1 · TTS said How much cereal with milk did you have?

2 · Card shown How much cereal with milk did you have?

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T20:11:35.046Z

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 the rest of the pizza." (difficulty —)3.3s

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

1 · TTS said What exact food and amount should I use for Pizza? I did not log it yet because I could not safely finish that food log.

2 · Card shown What exact food and amount should I use for Pizza? 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-08-02T20:11:49.715Z

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"Two cups, cooked." (difficulty —)0.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 0.7s

1 · TTS said What food did you have?

2 · Card shown What food did you have?

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T20:12:20.166Z

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"It was a turkey sandwich: Swiss plus mustard." (difficulty —)4.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 4.4s

1 · TTS said Which exact a turkey sandwich: swiss plus mustard should replace Chicken Salad Meal?

2 · Card shown Which exact a turkey sandwich: swiss plus mustard should replace Chicken Salad Meal?

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T20:12:48.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)

UNVERIFIEDunclassifiedshould complete the pending action"A grande latte with oat milk." (difficulty —)2.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 2.4s

1 · TTS said Was the grande oat milk latte sweetened, or was it just plain?

2 · Card shown Was the grande oat milk latte sweetened, or was it just plain?

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T20:13:15.230Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 2.9 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

PASSshould complete the pending action"About 150 grams cooked." (difficulty —)0.1s

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

1 · TTS said Logged Cooked white rice.

2 · Card shown Logged Cooked white rice.

3 · App data rows written created food_log_entry: Cooked white rice ×1 (150 g) 195 cal · 4.1g P · 42g C · 0.5g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T20:13:37.622Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 2.6 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

PASSshould complete the pending action"It was chicken noodle soup, one and a half cups." (difficulty —)0.8s

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

1 · TTS said I could not confirm that was saved, so I did not mark it as done.

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

3 · App data rows written update_sync_failed food_log_entry: Cooked white rice

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T20:14:04.245Z

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"Use the Quest chocolate one." (difficulty —)0.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 0.1s

1 · TTS said I need to resolve Replay setup: Replay setup: Record before I log this meal. What should I use for Replay setup: Replay setup: Record?

2 · Card shown I need to resolve Replay setup: Replay setup: Record before I log this meal. What should I use for Replay setup: Replay setup: Record?

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T20:14:32.542Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched your past food logs to "Quest Chocolate Chip Cookie Dough Protein Bar" at 82% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 2.3 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

PASSshould complete the pending action"Half a cup dry before cooking." (difficulty —)0.1s

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

1 · TTS said Logged Cooked pasta.

2 · Card shown Logged Cooked pasta.

3 · App data rows written created food_log_entry: Cooked pasta ×1 (0.5 cup) 110 cal · 4.1g P · 21.6g 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-08-02T20:15:00.121Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 3.1 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

UNVERIFIEDunclassifiedshould complete the pending action"Ranch, two tablespoons." (difficulty —)0.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 0.1s

1 · TTS said Should I add that as a to-do?

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: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T20:15:22.301Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 2.3 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

PASSshould complete the pending action"It was two slices of pepperoni pizza." (difficulty —)0.9s

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

1 · TTS said I could not confirm that was saved, so I did not mark it as done.

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

3 · App data rows written update_sync_failed food_log_entry: Cooked white rice

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T20:15: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)

PASSshould complete the pending action"Cinnamon Toast Crunch, 55 grams, and one cup 2 percent milk." (difficulty —)1.0s

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

1 · TTS said Logged Toast and one cup 2 percent milk. Assumed catalog default servings where you did not say an amount — tell me if that is not right.

2 · Card shown Logged Toast and one cup 2 percent milk. 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: Toast ×1 (100 g) 265 cal · 9g P · 49g C · 3.2g F
created food_log_entry: 2% milk ×1 (1 cup) 122 cal · 8.1g P · 11.7g C · 4.9g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T20:16:11.278Z

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"Chicken, rice, black beans, corn salsa, cheese, and guac." (difficulty —)0.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 0.1s

1 · TTS said I need to resolve Replay setup: Replay setup: Log before I log this meal. What should I use for Replay setup: Replay setup: Log?

2 · Card shown I need to resolve Replay setup: Replay setup: Log before I log this meal. What should I use for Replay setup: Replay setup: 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-08-02T20:16:38.464Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 5.0 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

PASSshould complete the pending action"Four ounces grilled chicken breast." (difficulty —)0.1s

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

1 · TTS said Logged Chicken breast.

2 · Card shown Logged Chicken breast.

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

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T20:16:59.266Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched your saved foods and aliases to "chicken breast" at 90% confidence.
Matched the common-food list to "Chicken breast" at 90% confidence.
Matched your saved foods and aliases to "Grilled Chicken Breast" at 69% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 2.4 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

PASSshould log the entry"Log my usual breakfast." (difficulty —)0.1s

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

Why verdict Logged (write-truth verified): Instant Oatmeal Packet — 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 Logged Quaker Instant Oatmeal Packet. Using your saved "my usual breakfast". Tell me if that is wrong.

2 · Card shown Logged Quaker Instant Oatmeal Packet. Using your saved "my usual breakfast". Tell me if that is wrong.

3 · App data rows written created food_log_entry: Instant Oatmeal Packet ×1 (packet) 150 cal · 4g P · 27g C · 3g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seeded value

{
  "table": "user_food_items",
  "record": {
    "id": "seed-oatmeal-packet",
    "shared_food_id": null,
    "display_name": "Instant Oatmeal Packet",
    "brand": "Quaker",
    "serving_label": "packet",
    "serving_quantity": 1,
    "serving_unit": "packet",
    "macros_per_serving": {
      "calories": 150,
      "proteinGrams": 4,
      "fatGrams": 3,
      "carbsGrams": 27
    },
    "macros_per_100g": null,
    "times_logged": 1,
    "last_logged_at": null,
    "created_at": {
      "$relativeDays": -14
    }
  }
}

Seeded value

{
  "table": "user_food_aliases",
  "record": {
    "id": "seed-alias-usual-breakfast",
    "phrase": "my usual breakfast",
    "user_food_id": "seed-oatmeal-packet",
    "use_count": 1,
    "is_default": true,
    "shortcut_settings": {
      "quickLogMode": "fixed",
      "defaultQuantity": 1,
      "defaultServingLabel": "packet",
      "displayLabel": "my usual breakfast",
      "confirmBeforeLog": false
    },
    "updated_at": {
      "$relativeDays": -1
    }
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-log-usual-bfast-1",
    "user_food_id": "seed-oatmeal-packet",
    "food_name": "Instant Oatmeal Packet",
    "brand": "Quaker",
    "quantity": 1,
    "serving_label": "packet",
    "macros": {
      "calories": 150,
      "proteinGrams": 4,
      "fatGrams": 3,
      "carbsGrams": 27
    },
    "meal": "breakfast",
    "notes": null,
    "logged_at": {
      "$relativeDays": -3
    },
    "deleted_at": null,
    "deleted_by_request_id": null
  }
}

snapshot captured 2026-08-02T20:17:10.555Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched your saved foods and aliases to "my usual breakfast" at 96% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 0.3 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

PASSshould log the entry"Add the same smoothie as yesterday." (difficulty —)0.4s

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

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

1 · TTS said Logged Berry Protein Smoothie. Using your recent Berry Protein Smoothie history. Tell me if that is wrong.

2 · Card shown Logged Berry Protein Smoothie. Using your recent Berry Protein Smoothie history. Tell me if that is wrong.

3 · App data rows written created food_log_entry: Berry Protein Smoothie ×1 (serving) 280 cal · 18g P · 42g C · 6g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seeded value

{
  "table": "user_food_items",
  "record": {
    "id": "seed-berry-smoothie",
    "shared_food_id": null,
    "display_name": "Berry Protein Smoothie",
    "brand": null,
    "serving_label": "serving",
    "serving_quantity": 1,
    "serving_unit": "serving",
    "macros_per_serving": {
      "calories": 280,
      "proteinGrams": 18,
      "fatGrams": 6,
      "carbsGrams": 42
    },
    "macros_per_100g": null,
    "times_logged": 1,
    "last_logged_at": null,
    "created_at": {
      "$relativeDays": -14
    }
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-log-yesterday-smoothie",
    "user_food_id": "seed-berry-smoothie",
    "food_name": "Berry Protein Smoothie",
    "brand": null,
    "quantity": 1,
    "serving_label": "serving",
    "macros": {
      "calories": 280,
      "proteinGrams": 18,
      "fatGrams": 6,
      "carbsGrams": 42
    },
    "meal": "snack",
    "notes": null,
    "logged_at": {
      "$relativeDays": -1
    },
    "deleted_at": null,
    "deleted_by_request_id": null
  }
}

snapshot captured 2026-08-02T20:17:22.112Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 0.6 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

FAILshould log the entry"Record my normal pre-workout snack." (difficulty —)2.6s

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

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

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

Pick every reason you think applies. Multiple boxes are allowed because one utterance can be wrong in more than one way. Use the note below for "Other" or extra detail.

Timing 2.6s

1 · TTS said I did not make any app changes. What would you like me to do with that?

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:

Seeded value

{
  "table": "user_food_items",
  "record": {
    "id": "seed-preworkout-snack",
    "shared_food_id": null,
    "display_name": "Pre-Workout Snack Pack",
    "brand": "Home default",
    "serving_label": "serving",
    "serving_quantity": 1,
    "serving_unit": "serving",
    "macros_per_serving": {
      "calories": 220,
      "proteinGrams": 12,
      "fatGrams": 8,
      "carbsGrams": 24
    },
    "macros_per_100g": null,
    "times_logged": 1,
    "last_logged_at": null,
    "created_at": {
      "$relativeDays": -14
    }
  }
}

Seeded value

{
  "table": "user_food_aliases",
  "record": {
    "id": "seed-alias-preworkout-snack",
    "phrase": "my normal pre-workout snack",
    "user_food_id": "seed-preworkout-snack",
    "use_count": 1,
    "is_default": true,
    "shortcut_settings": {
      "quickLogMode": "fixed",
      "defaultQuantity": 1,
      "defaultServingLabel": "serving",
      "displayLabel": "my normal pre-workout snack",
      "confirmBeforeLog": false
    },
    "updated_at": {
      "$relativeDays": -1
    }
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-log-preworkout-1",
    "user_food_id": "seed-preworkout-snack",
    "food_name": "Pre-Workout Snack Pack",
    "brand": "Home default",
    "quantity": 1,
    "serving_label": "serving",
    "macros": {
      "calories": 220,
      "proteinGrams": 12,
      "fatGrams": 8,
      "carbsGrams": 24
    },
    "meal": "snack",
    "notes": null,
    "logged_at": {
      "$relativeDays": -2
    },
    "deleted_at": null,
    "deleted_by_request_id": null
  }
}

snapshot captured 2026-08-02T20:17:35.802Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched your saved foods and aliases to "my normal pre-workout snack" at 96% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 2.2 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

PASSshould log the entry"Track another one of those turkey wraps." (difficulty —)0.6s

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

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

2 · Card shown Logged Home default Turkey Wrap. Using your recent Home default Turkey Wrap history. Tell me if that is wrong.

3 · App data rows written created food_log_entry: Turkey Wrap ×1 (wrap) 340 cal · 28g P · 31g C · 11g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seeded value

{
  "table": "user_food_items",
  "record": {
    "id": "seed-turkey-wrap",
    "shared_food_id": null,
    "display_name": "Turkey Wrap",
    "brand": "Home default",
    "serving_label": "wrap",
    "serving_quantity": 1,
    "serving_unit": "wrap",
    "macros_per_serving": {
      "calories": 340,
      "proteinGrams": 28,
      "fatGrams": 11,
      "carbsGrams": 31
    },
    "macros_per_100g": null,
    "times_logged": 1,
    "last_logged_at": null,
    "created_at": {
      "$relativeDays": -14
    }
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-log-turkey-wrap-recent",
    "user_food_id": "seed-turkey-wrap",
    "food_name": "Turkey Wrap",
    "brand": "Home default",
    "quantity": 1,
    "serving_label": "wrap",
    "macros": {
      "calories": 340,
      "proteinGrams": 28,
      "fatGrams": 11,
      "carbsGrams": 31
    },
    "meal": "lunch",
    "notes": null,
    "logged_at": {
      "$relativeHours": -5
    },
    "deleted_at": null,
    "deleted_by_request_id": null
  }
}

snapshot captured 2026-08-02T20:17:59.064Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 3.3 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

FAILshould log the entry"Log the same lunch I had Monday." (difficulty —)0.2s

Verdict Expected LOG — should log the entry. FAIL: WRITE-TRUTH FAIL — WRONG/MISSING item "Chicken Rice Bowl" — no saved row with matching identity (rows: Sweetgreen Harvest Bowl)

Why verdict WRITE-TRUTH FAIL — WRONG/MISSING item "Chicken Rice Bowl" — no saved row with matching identity (rows: Sweetgreen Harvest Bowl)

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 Logged Sweetgreen Sweetgreen Harvest Bowl. Using your recent Sweetgreen Sweetgreen Harvest Bowl history. Tell me if that is wrong.

2 · Card shown Logged Sweetgreen Sweetgreen Harvest Bowl. Using your recent Sweetgreen Sweetgreen Harvest Bowl history. Tell me if that is wrong.

3 · App data rows written created food_log_entry: Sweetgreen Harvest Bowl ×1 (bowl) 540 cal · 28g P · 48g C · 24g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seeded value

{
  "table": "user_food_items",
  "record": {
    "id": "seed-monday-lunch-bowl",
    "shared_food_id": null,
    "display_name": "Chicken Rice Bowl",
    "brand": "Home default",
    "serving_label": "bowl",
    "serving_quantity": 1,
    "serving_unit": "bowl",
    "macros_per_serving": {
      "calories": 520,
      "proteinGrams": 42,
      "fatGrams": 14,
      "carbsGrams": 48
    },
    "macros_per_100g": null,
    "times_logged": 1,
    "last_logged_at": null,
    "created_at": {
      "$relativeDays": -14
    }
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-log-monday-lunch",
    "user_food_id": "seed-monday-lunch-bowl",
    "food_name": "Chicken Rice Bowl",
    "brand": "Home default",
    "quantity": 1,
    "serving_label": "bowl",
    "macros": {
      "calories": 520,
      "proteinGrams": 42,
      "fatGrams": 14,
      "carbsGrams": 48
    },
    "meal": "lunch",
    "notes": "Monday lunch",
    "logged_at": {
      "$relativeDays": -3
    },
    "deleted_at": null,
    "deleted_by_request_id": null
  }
}

snapshot captured 2026-08-02T20:18:10.423Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 0.5 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

PASSshould log the entry"Add my default coffee." (difficulty —)0.1s

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

Why verdict Logged (write-truth verified): Black Coffee — 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 Logged Black Coffee. Using your saved "my default coffee". Tell me if that is wrong.

2 · Card shown Logged Black Coffee. Using your saved "my default coffee". Tell me if that is wrong.

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

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seeded value

{
  "table": "user_food_items",
  "record": {
    "id": "seed-default-coffee",
    "shared_food_id": null,
    "display_name": "Black Coffee",
    "brand": null,
    "serving_label": "cup",
    "serving_quantity": 1,
    "serving_unit": "cup",
    "macros_per_serving": {
      "calories": 5,
      "proteinGrams": 0,
      "fatGrams": 0,
      "carbsGrams": 1
    },
    "macros_per_100g": null,
    "times_logged": 1,
    "last_logged_at": null,
    "created_at": {
      "$relativeDays": -14
    }
  }
}

Seeded value

{
  "table": "user_food_aliases",
  "record": {
    "id": "seed-alias-default-coffee",
    "phrase": "my default coffee",
    "user_food_id": "seed-default-coffee",
    "use_count": 1,
    "is_default": true,
    "shortcut_settings": {
      "quickLogMode": "fixed",
      "defaultQuantity": 1,
      "defaultServingLabel": "cup",
      "displayLabel": "my default coffee",
      "confirmBeforeLog": false
    },
    "updated_at": {
      "$relativeDays": -1
    }
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-log-default-coffee",
    "user_food_id": "seed-default-coffee",
    "food_name": "Black Coffee",
    "brand": null,
    "quantity": 1,
    "serving_label": "cup",
    "macros": {
      "calories": 5,
      "proteinGrams": 0,
      "fatGrams": 0,
      "carbsGrams": 1
    },
    "meal": "breakfast",
    "notes": null,
    "logged_at": {
      "$relativeDays": -1
    },
    "deleted_at": null,
    "deleted_by_request_id": null
  }
}

snapshot captured 2026-08-02T20:18:21.717Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched your saved foods and aliases to "my default coffee" at 96% confidence.
Matched the common-food list to "Coffee" at 90% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 0.2 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

PASSshould log the entry"Record the usual oatmeal bowl." (difficulty —)0.1s

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

Why verdict Logged (write-truth verified): Cooked Oatmeal Bowl — 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 Logged Cooked Oatmeal Bowl. Using your saved "usual oatmeal bowl". Tell me if that is wrong.

2 · Card shown Logged Cooked Oatmeal Bowl. Using your saved "usual oatmeal bowl". Tell me if that is wrong.

3 · App data rows written created food_log_entry: Cooked Oatmeal Bowl ×1 (bowl) 180 cal · 6g P · 32g C · 3g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seeded value

{
  "table": "user_food_items",
  "record": {
    "id": "seed-oatmeal-bowl",
    "shared_food_id": null,
    "display_name": "Cooked Oatmeal Bowl",
    "brand": null,
    "serving_label": "bowl",
    "serving_quantity": 1,
    "serving_unit": "bowl",
    "macros_per_serving": {
      "calories": 180,
      "proteinGrams": 6,
      "fatGrams": 3,
      "carbsGrams": 32
    },
    "macros_per_100g": null,
    "times_logged": 1,
    "last_logged_at": null,
    "created_at": {
      "$relativeDays": -14
    }
  }
}

Seeded value

{
  "table": "user_food_aliases",
  "record": {
    "id": "seed-alias-usual-oatmeal-bowl",
    "phrase": "usual oatmeal bowl",
    "user_food_id": "seed-oatmeal-bowl",
    "use_count": 1,
    "is_default": true,
    "shortcut_settings": {
      "quickLogMode": "fixed",
      "defaultQuantity": 1,
      "defaultServingLabel": "bowl",
      "displayLabel": "usual oatmeal bowl",
      "confirmBeforeLog": false
    },
    "updated_at": {
      "$relativeDays": -1
    }
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-log-usual-oatmeal-bowl",
    "user_food_id": "seed-oatmeal-bowl",
    "food_name": "Cooked Oatmeal Bowl",
    "brand": null,
    "quantity": 1,
    "serving_label": "bowl",
    "macros": {
      "calories": 180,
      "proteinGrams": 6,
      "fatGrams": 3,
      "carbsGrams": 32
    },
    "meal": "breakfast",
    "notes": null,
    "logged_at": {
      "$relativeDays": -2
    },
    "deleted_at": null,
    "deleted_by_request_id": null
  }
}

snapshot captured 2026-08-02T20:18:32.996Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched your saved foods and aliases to "usual oatmeal bowl" at 96% confidence.
Matched the common-food list to "Cooked oatmeal" at 90% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 0.2 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

PASSshould log the entry"Track half of my regular burrito bowl." (difficulty —)0.1s

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

Why verdict Logged (write-truth verified): Burrito Bowl — 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 Logged Home default Burrito Bowl. Using your saved "my regular burrito bowl". Tell me if that is wrong.

2 · Card shown Logged Home default Burrito Bowl. Using your saved "my regular burrito bowl". Tell me if that is wrong.

3 · App data rows written created food_log_entry: Burrito Bowl ×1 (bowl) 620 cal · 35g P · 72g C · 18g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seeded value

{
  "table": "user_food_items",
  "record": {
    "id": "seed-burrito-bowl",
    "shared_food_id": null,
    "display_name": "Burrito Bowl",
    "brand": "Home default",
    "serving_label": "bowl",
    "serving_quantity": 1,
    "serving_unit": "bowl",
    "macros_per_serving": {
      "calories": 620,
      "proteinGrams": 35,
      "fatGrams": 18,
      "carbsGrams": 72
    },
    "macros_per_100g": null,
    "times_logged": 1,
    "last_logged_at": null,
    "created_at": {
      "$relativeDays": -14
    }
  }
}

Seeded value

{
  "table": "user_food_aliases",
  "record": {
    "id": "seed-alias-regular-burrito-bowl",
    "phrase": "my regular burrito bowl",
    "user_food_id": "seed-burrito-bowl",
    "use_count": 1,
    "is_default": true,
    "shortcut_settings": {
      "quickLogMode": "fixed",
      "defaultQuantity": 1,
      "defaultServingLabel": "bowl",
      "displayLabel": "my regular burrito bowl",
      "confirmBeforeLog": false
    },
    "updated_at": {
      "$relativeDays": -1
    }
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-log-regular-burrito",
    "user_food_id": "seed-burrito-bowl",
    "food_name": "Burrito Bowl",
    "brand": "Home default",
    "quantity": 1,
    "serving_label": "bowl",
    "macros": {
      "calories": 620,
      "proteinGrams": 35,
      "fatGrams": 18,
      "carbsGrams": 72
    },
    "meal": "lunch",
    "notes": null,
    "logged_at": {
      "$relativeDays": -2
    },
    "deleted_at": null,
    "deleted_by_request_id": null
  }
}

snapshot captured 2026-08-02T20:18:44.262Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched your saved foods and aliases to "my regular burrito bowl" at 96% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 0.4 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

FAILshould log the entry"Log another Fairlife shake like this morning." (difficulty —)3.5s

Verdict Expected LOG — should log the entry. FAIL: WRITE-TRUTH FAIL — WRONG/MISSING item "Fairlife Core Power Chocolate" — no saved row with matching identity (rows: Fairlife Core Power Elite Vanilla Protein Shake)

Why verdict WRITE-TRUTH FAIL — WRONG/MISSING item "Fairlife Core Power Chocolate" — no saved row with matching identity (rows: Fairlife Core Power Elite Vanilla Protein Shake)

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 Logged fairlife core power elite vanilla protein shake with an estimated macro range.

2 · Card shown Logged fairlife core power elite vanilla protein shake — the macros are an estimate since this food varies by brand.

3 · App data rows written created food_log_entry: Fairlife Core Power Elite Vanilla Protein Shake ×1 (one) 230 cal · 42g P · 8g C · 3.5g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seeded value

{
  "table": "user_food_items",
  "record": {
    "id": "seed-fairlife-shake",
    "shared_food_id": null,
    "display_name": "Fairlife Core Power Chocolate",
    "brand": "Fairlife",
    "serving_label": "bottle",
    "serving_quantity": 1,
    "serving_unit": "bottle",
    "macros_per_serving": {
      "calories": 170,
      "proteinGrams": 26,
      "fatGrams": 4.5,
      "carbsGrams": 8
    },
    "macros_per_100g": null,
    "times_logged": 1,
    "last_logged_at": null,
    "created_at": {
      "$relativeDays": -14
    }
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-log-fairlife-morning",
    "user_food_id": "seed-fairlife-shake",
    "food_name": "Fairlife Core Power Chocolate",
    "brand": "Fairlife",
    "quantity": 1,
    "serving_label": "bottle",
    "macros": {
      "calories": 170,
      "proteinGrams": 26,
      "fatGrams": 4.5,
      "carbsGrams": 8
    },
    "meal": "breakfast",
    "notes": null,
    "logged_at": {
      "$relativeHours": -4
    },
    "deleted_at": null,
    "deleted_by_request_id": null
  }
}

snapshot captured 2026-08-02T20:18:59.394Z

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

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

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

PASSshould log the entry"Add my saved chicken salad meal." (difficulty —)0.1s

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

Why verdict Logged (write-truth verified): Chicken Salad Meal, Chicken Salad Meal — 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 Logged Home default Chicken Salad Meal. Using your saved "my saved chicken salad meal". Tell me if that is wrong.

2 · Card shown Logged Home default Chicken Salad Meal. Using your saved "my saved chicken salad meal". Tell me if that is wrong.

3 · App data rows written created food_log_entry: Chicken Salad Meal ×1 (serving) 410 cal · 38g P · 16g C · 18g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seeded value

{
  "table": "user_food_items",
  "record": {
    "id": "seed-chicken-salad-meal",
    "shared_food_id": null,
    "display_name": "Chicken Salad Meal",
    "brand": "Home default",
    "serving_label": "serving",
    "serving_quantity": 1,
    "serving_unit": "serving",
    "macros_per_serving": {
      "calories": 410,
      "proteinGrams": 38,
      "fatGrams": 18,
      "carbsGrams": 16
    },
    "macros_per_100g": null,
    "times_logged": 1,
    "last_logged_at": null,
    "created_at": {
      "$relativeDays": -14
    }
  }
}

Seeded value

{
  "table": "user_food_aliases",
  "record": {
    "id": "seed-alias-saved-chicken-salad",
    "phrase": "my saved chicken salad meal",
    "user_food_id": "seed-chicken-salad-meal",
    "use_count": 1,
    "is_default": true,
    "shortcut_settings": {
      "quickLogMode": "fixed",
      "defaultQuantity": 1,
      "defaultServingLabel": "serving",
      "displayLabel": "my saved chicken salad meal",
      "confirmBeforeLog": false
    },
    "updated_at": {
      "$relativeDays": -1
    }
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-log-chicken-salad",
    "user_food_id": "seed-chicken-salad-meal",
    "food_name": "Chicken Salad Meal",
    "brand": "Home default",
    "quantity": 1,
    "serving_label": "serving",
    "macros": {
      "calories": 410,
      "proteinGrams": 38,
      "fatGrams": 18,
      "carbsGrams": 16
    },
    "meal": "lunch",
    "notes": null,
    "logged_at": {
      "$relativeDays": -4
    },
    "deleted_at": null,
    "deleted_by_request_id": null
  }
}

snapshot captured 2026-08-02T20:19:10.189Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched your saved foods and aliases to "my saved chicken salad meal" at 96% confidence.
Matched the common-food list to "Chicken salad with mayonnaise" at 90% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 2.7 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

PASSshould log the entry"Record what I normally eat after spin class." (difficulty —)0.1s

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

Why verdict Logged (write-truth verified): Post-Spin Recovery Meal — 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 Logged Home default Post-Spin Recovery Meal. Using your saved fixed default for "what i normally eat after spin class" (1 serving). Say a different amount if that is wrong.

2 · Card shown Logged Home default Post-Spin Recovery Meal. Using your saved fixed default for "what i normally eat after spin class" (1 serving). Say a different amount if that is wrong.

3 · App data rows written created food_log_entry: Post-Spin Recovery Meal ×1 (serving) 450 cal · 30g P · 48g C · 12g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seeded value

{
  "table": "user_food_items",
  "record": {
    "id": "seed-post-spin-meal",
    "shared_food_id": null,
    "display_name": "Post-Spin Recovery Meal",
    "brand": "Home default",
    "serving_label": "serving",
    "serving_quantity": 1,
    "serving_unit": "serving",
    "macros_per_serving": {
      "calories": 450,
      "proteinGrams": 30,
      "fatGrams": 12,
      "carbsGrams": 48
    },
    "macros_per_100g": null,
    "times_logged": 1,
    "last_logged_at": null,
    "created_at": {
      "$relativeDays": -14
    }
  }
}

Seeded value

{
  "table": "user_food_aliases",
  "record": {
    "id": "seed-alias-post-spin",
    "phrase": "what i normally eat after spin class",
    "user_food_id": "seed-post-spin-meal",
    "use_count": 1,
    "is_default": true,
    "shortcut_settings": {
      "quickLogMode": "fixed",
      "defaultQuantity": 1,
      "defaultServingLabel": "serving",
      "displayLabel": "what I normally eat after spin class",
      "confirmBeforeLog": false
    },
    "updated_at": {
      "$relativeDays": -1
    }
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-log-post-spin",
    "user_food_id": "seed-post-spin-meal",
    "food_name": "Post-Spin Recovery Meal",
    "brand": "Home default",
    "quantity": 1,
    "serving_label": "serving",
    "macros": {
      "calories": 450,
      "proteinGrams": 30,
      "fatGrams": 12,
      "carbsGrams": 48
    },
    "meal": "lunch",
    "notes": null,
    "logged_at": {
      "$relativeDays": -3
    },
    "deleted_at": null,
    "deleted_by_request_id": null
  }
}

snapshot captured 2026-08-02T20:19:21.517Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched your saved foods and aliases to "what i normally eat after spin class" at 96% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 2.5 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

FAILshould log the entry"Track the other half of dinner from last night." (difficulty —)2.7s

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

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

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

Pick every reason you think applies. Multiple boxes are allowed because one utterance can be wrong in more than one way. Use the note below for "Other" or extra detail.

Timing 2.7s

1 · TTS said I need to resolve the other before I log this meal. What should I use for the other?

2 · Card shown I need to resolve the other before I log this meal. What should I use for the other?

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seeded value

{
  "table": "user_food_items",
  "record": {
    "id": "seed-last-night-dinner",
    "shared_food_id": null,
    "display_name": "Grilled Salmon Dinner",
    "brand": "Home default",
    "serving_label": "plate",
    "serving_quantity": 1,
    "serving_unit": "plate",
    "macros_per_serving": {
      "calories": 580,
      "proteinGrams": 42,
      "fatGrams": 22,
      "carbsGrams": 38
    },
    "macros_per_100g": null,
    "times_logged": 1,
    "last_logged_at": null,
    "created_at": {
      "$relativeDays": -14
    }
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-log-last-night-dinner",
    "user_food_id": "seed-last-night-dinner",
    "food_name": "Grilled Salmon Dinner",
    "brand": "Home default",
    "quantity": 1,
    "serving_label": "plate",
    "macros": {
      "calories": 580,
      "proteinGrams": 42,
      "fatGrams": 22,
      "carbsGrams": 38
    },
    "meal": "dinner",
    "notes": null,
    "logged_at": {
      "$relativeDays": -1
    },
    "deleted_at": null,
    "deleted_by_request_id": null
  }
}

snapshot captured 2026-08-02T20:19:31.007Z

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

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

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

PASSshould log the entry"Log my usual restaurant order at Sweetgreen." (difficulty —)0.1s

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

Why verdict Logged (write-truth verified): Sweetgreen Harvest Bowl — 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 Logged Sweetgreen Sweetgreen Harvest Bowl. Using your saved "my usual restaurant order at sweetgreen". Tell me if that is wrong.

2 · Card shown Logged Sweetgreen Sweetgreen Harvest Bowl. Using your saved "my usual restaurant order at sweetgreen". Tell me if that is wrong.

3 · App data rows written created food_log_entry: Sweetgreen Harvest Bowl ×1 (bowl) 540 cal · 28g P · 48g C · 24g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seeded value

{
  "table": "user_food_items",
  "record": {
    "id": "seed-sweetgreen-usual",
    "shared_food_id": null,
    "display_name": "Sweetgreen Harvest Bowl",
    "brand": "Sweetgreen",
    "serving_label": "bowl",
    "serving_quantity": 1,
    "serving_unit": "bowl",
    "macros_per_serving": {
      "calories": 540,
      "proteinGrams": 28,
      "fatGrams": 24,
      "carbsGrams": 48
    },
    "macros_per_100g": null,
    "times_logged": 1,
    "last_logged_at": null,
    "created_at": {
      "$relativeDays": -14
    }
  }
}

Seeded value

{
  "table": "user_food_aliases",
  "record": {
    "id": "seed-alias-sweetgreen-usual",
    "phrase": "my usual restaurant order at sweetgreen",
    "user_food_id": "seed-sweetgreen-usual",
    "use_count": 1,
    "is_default": true,
    "shortcut_settings": {
      "quickLogMode": "fixed",
      "defaultQuantity": 1,
      "defaultServingLabel": "bowl",
      "displayLabel": "my usual restaurant order at Sweetgreen",
      "confirmBeforeLog": false
    },
    "updated_at": {
      "$relativeDays": -1
    }
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-log-sweetgreen",
    "user_food_id": "seed-sweetgreen-usual",
    "food_name": "Sweetgreen Harvest Bowl",
    "brand": "Sweetgreen",
    "quantity": 1,
    "serving_label": "bowl",
    "macros": {
      "calories": 540,
      "proteinGrams": 28,
      "fatGrams": 24,
      "carbsGrams": 48
    },
    "meal": "lunch",
    "notes": null,
    "logged_at": {
      "$relativeDays": -5
    },
    "deleted_at": null,
    "deleted_by_request_id": null
  }
}

snapshot captured 2026-08-02T20:19:46.615Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched your saved foods and aliases to "my usual restaurant order at sweetgreen" at 96% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 0.4 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

PASSshould log the entry"Add the protein pancakes I always make." (difficulty —)0.1s

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

Why verdict Logged (write-truth verified): Protein Pancakes — 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 Logged Home default Protein Pancakes. Using your saved "the protein pancakes i always make". Tell me if that is wrong.

2 · Card shown Logged Home default Protein Pancakes. Using your saved "the protein pancakes i always make". Tell me if that is wrong.

3 · App data rows written created food_log_entry: Protein Pancakes ×1 (serving) 320 cal · 28g P · 34g C · 8g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seeded value

{
  "table": "user_food_items",
  "record": {
    "id": "seed-protein-pancakes",
    "shared_food_id": null,
    "display_name": "Protein Pancakes",
    "brand": "Home default",
    "serving_label": "serving",
    "serving_quantity": 1,
    "serving_unit": "serving",
    "macros_per_serving": {
      "calories": 320,
      "proteinGrams": 28,
      "fatGrams": 8,
      "carbsGrams": 34
    },
    "macros_per_100g": null,
    "times_logged": 1,
    "last_logged_at": null,
    "created_at": {
      "$relativeDays": -14
    }
  }
}

Seeded value

{
  "table": "user_food_aliases",
  "record": {
    "id": "seed-alias-protein-pancakes",
    "phrase": "the protein pancakes i always make",
    "user_food_id": "seed-protein-pancakes",
    "use_count": 1,
    "is_default": true,
    "shortcut_settings": {
      "quickLogMode": "fixed",
      "defaultQuantity": 1,
      "defaultServingLabel": "serving",
      "displayLabel": "the protein pancakes I always make",
      "confirmBeforeLog": false
    },
    "updated_at": {
      "$relativeDays": -1
    }
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-log-protein-pancakes",
    "user_food_id": "seed-protein-pancakes",
    "food_name": "Protein Pancakes",
    "brand": "Home default",
    "quantity": 1,
    "serving_label": "serving",
    "macros": {
      "calories": 320,
      "proteinGrams": 28,
      "fatGrams": 8,
      "carbsGrams": 34
    },
    "meal": "breakfast",
    "notes": null,
    "logged_at": {
      "$relativeDays": -2
    },
    "deleted_at": null,
    "deleted_by_request_id": null
  }
}

snapshot captured 2026-08-02T20:19:57.972Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched your saved foods and aliases to "the protein pancakes i always make" at 96% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 2.4 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

UNVERIFIEDunclassifiedshould log the entry"Record the snack pack I built last week." (difficulty —)3.6s

Why verdict UNVERIFIABLE — no saved row captured (untagged / lossy) — resolve via the notes.utterance_trace_id join. App claim not credited; resolve via the notes.utterance_trace_id join.

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

1 · TTS said Logging your snack pack I built last week — still looking up the nutrition details; they'll appear in your log shortly.

2 · Card shown Logging your snack pack I built last week — still looking up the nutrition details; they'll appear in your log shortly.

3 · App data rows written pending_created food_log_entry: the snack pack I built last week (pending)

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seeded value

{
  "table": "user_food_items",
  "record": {
    "id": "seed-snack-pack",
    "shared_food_id": null,
    "display_name": "Snack Pack",
    "brand": "Home default",
    "serving_label": "pack",
    "serving_quantity": 1,
    "serving_unit": "pack",
    "macros_per_serving": {
      "calories": 240,
      "proteinGrams": 10,
      "fatGrams": 12,
      "carbsGrams": 22
    },
    "macros_per_100g": null,
    "times_logged": 1,
    "last_logged_at": null,
    "created_at": {
      "$relativeDays": -14
    }
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-log-snack-pack-last-week",
    "user_food_id": "seed-snack-pack",
    "food_name": "Snack Pack",
    "brand": "Home default",
    "quantity": 1,
    "serving_label": "pack",
    "macros": {
      "calories": 240,
      "proteinGrams": 10,
      "fatGrams": 12,
      "carbsGrams": 22
    },
    "meal": "snack",
    "notes": null,
    "logged_at": {
      "$relativeDays": -7
    },
    "deleted_at": null,
    "deleted_by_request_id": null
  }
}

snapshot captured 2026-08-02T20:20:19.659Z

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 my last chicken entry to 6 ounces, not 4." (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 I could not confirm that was saved, so I did not mark it as done.

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:

Seeded value

{
  "table": "user_food_items",
  "record": {
    "id": "seed-chicken-breast-4oz",
    "shared_food_id": null,
    "display_name": "Grilled Chicken Breast",
    "brand": null,
    "serving_label": "ounce",
    "serving_quantity": 4,
    "serving_unit": "oz",
    "macros_per_serving": {
      "calories": 185,
      "proteinGrams": 35,
      "fatGrams": 4,
      "carbsGrams": 0
    },
    "macros_per_100g": null,
    "times_logged": 1,
    "last_logged_at": null,
    "created_at": {
      "$relativeDays": -14
    }
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-log-last-chicken",
    "user_food_id": "seed-chicken-breast-4oz",
    "food_name": "Grilled Chicken Breast",
    "brand": null,
    "quantity": 1,
    "serving_label": "ounce",
    "macros": {
      "calories": 185,
      "proteinGrams": 35,
      "fatGrams": 4,
      "carbsGrams": 0
    },
    "meal": "lunch",
    "notes": null,
    "logged_at": {
      "$relativeHours": -2
    },
    "deleted_at": null,
    "deleted_by_request_id": null
  }
}

snapshot captured 2026-08-02T20:20:20.231Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched the common-food list to "Chicken breast" at 90% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 3.8 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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 that latte skim milk instead of whole." (difficulty —)5.0s

Verdict Expected UPDATE — should update the entry. FAIL: WRONG ACTION — created a NEW entry on an UPDATE request.

Why verdict WRONG ACTION — created a NEW entry on an UPDATE 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 5.0s

1 · TTS said I could not confirm that was saved, so I did not mark it as done.

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

3 · App data rows written update_sync_failed food_log_entry: the snack pack I built last week

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seeded value

{
  "table": "user_food_items",
  "record": {
    "id": "seed-whole-milk-latte",
    "shared_food_id": null,
    "display_name": "Whole Milk Latte",
    "brand": "Coffee shop default",
    "serving_label": "ounce",
    "serving_quantity": 12,
    "serving_unit": "oz",
    "macros_per_serving": {
      "calories": 180,
      "proteinGrams": 9,
      "fatGrams": 7,
      "carbsGrams": 18
    },
    "macros_per_100g": null,
    "times_logged": 1,
    "last_logged_at": null,
    "created_at": {
      "$relativeDays": -14
    }
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-log-last-latte",
    "user_food_id": "seed-whole-milk-latte",
    "food_name": "Whole Milk Latte",
    "brand": "Coffee shop default",
    "quantity": 1,
    "serving_label": "ounce",
    "macros": {
      "calories": 180,
      "proteinGrams": 9,
      "fatGrams": 7,
      "carbsGrams": 18
    },
    "meal": "breakfast",
    "notes": null,
    "logged_at": {
      "$relativeHours": -1
    },
    "deleted_at": null,
    "deleted_by_request_id": null
  }
}

snapshot captured 2026-08-02T20:20:41.273Z

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 update the entry"Update breakfast oats to 60 grams dry." (difficulty —)0.3s

Verdict Expected UPDATE — should update the entry. PASS: Updated as asked.

Why verdict Updated as asked.

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 Updated Dry Rolled Oats to 60 g.

2 · Card shown Updated Dry Rolled Oats to 60 g.

3 · App data rows written updated food_log_entry: Dry Rolled Oats ×1.3333333333333333 (gram) 227 cal · 8g P · 38.7g C · 4g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seeded value

{
  "table": "user_food_items",
  "record": {
    "id": "seed-breakfast-oats",
    "shared_food_id": null,
    "display_name": "Dry Rolled Oats",
    "brand": null,
    "serving_label": "gram",
    "serving_quantity": 45,
    "serving_unit": "g",
    "macros_per_serving": {
      "calories": 170,
      "proteinGrams": 6,
      "fatGrams": 3,
      "carbsGrams": 29
    },
    "macros_per_100g": null,
    "times_logged": 1,
    "last_logged_at": null,
    "created_at": {
      "$relativeDays": -14
    }
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-log-breakfast-oats",
    "user_food_id": "seed-breakfast-oats",
    "food_name": "Dry Rolled Oats",
    "brand": null,
    "quantity": 1,
    "serving_label": "gram",
    "macros": {
      "calories": 170,
      "proteinGrams": 6,
      "fatGrams": 3,
      "carbsGrams": 29
    },
    "meal": "breakfast",
    "notes": null,
    "logged_at": {
      "$relativeHours": -3
    },
    "deleted_at": null,
    "deleted_by_request_id": null
  }
}

snapshot captured 2026-08-02T20:20:58.099Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched the common-food list to "Dry oats" at 90% confidence.
Matched your past food logs to "Dry Rolled Oats" at 82% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 3.1 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

FAILshould update the entry"Correction: the rice was brown rice, not white." (difficulty —)5.2s

Verdict Expected UPDATE — should update the entry. FAIL: WRONG ACTION — created a NEW entry on an UPDATE request.

Why verdict WRONG ACTION — created a NEW entry on an UPDATE 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 5.2s

1 · TTS said I could not confirm that was saved, so I did not mark it as done.

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

3 · App data rows written update_sync_failed food_log_entry: the snack pack I built last week

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seeded value

{
  "table": "user_food_items",
  "record": {
    "id": "seed-white-rice",
    "shared_food_id": null,
    "display_name": "Cooked White Rice",
    "brand": null,
    "serving_label": "cup",
    "serving_quantity": 1,
    "serving_unit": "cup",
    "macros_per_serving": {
      "calories": 205,
      "proteinGrams": 4,
      "fatGrams": 0,
      "carbsGrams": 45
    },
    "macros_per_100g": null,
    "times_logged": 1,
    "last_logged_at": null,
    "created_at": {
      "$relativeDays": -14
    }
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-log-rice-entry",
    "user_food_id": "seed-white-rice",
    "food_name": "Cooked White Rice",
    "brand": null,
    "quantity": 1,
    "serving_label": "cup",
    "macros": {
      "calories": 205,
      "proteinGrams": 4,
      "fatGrams": 0,
      "carbsGrams": 45
    },
    "meal": "dinner",
    "notes": null,
    "logged_at": {
      "$relativeHours": -2
    },
    "deleted_at": null,
    "deleted_by_request_id": null
  }
}

snapshot captured 2026-08-02T20:21:08.566Z

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 update the entry"Make the salmon 7 ounces instead." (difficulty —)0.3s

Verdict Expected UPDATE — should update the entry. PASS: Updated as asked.

Why verdict Updated as asked.

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 Updated Smoked salmon to 7 oz.

2 · Card shown Updated Smoked salmon to 7 oz.

3 · App data rows written updated food_log_entry: Smoked salmon ×3.5 (2 oz) 231 cal · 36.4g P · 0g C · 8.4g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seeded value

{
  "table": "user_food_items",
  "record": {
    "id": "seed-baked-salmon",
    "shared_food_id": null,
    "display_name": "Baked Salmon",
    "brand": null,
    "serving_label": "ounce",
    "serving_quantity": 5,
    "serving_unit": "oz",
    "macros_per_serving": {
      "calories": 250,
      "proteinGrams": 28,
      "fatGrams": 14,
      "carbsGrams": 0
    },
    "macros_per_100g": null,
    "times_logged": 1,
    "last_logged_at": null,
    "created_at": {
      "$relativeDays": -14
    }
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-log-salmon-entry",
    "user_food_id": "seed-baked-salmon",
    "food_name": "Baked Salmon",
    "brand": null,
    "quantity": 1,
    "serving_label": "ounce",
    "macros": {
      "calories": 250,
      "proteinGrams": 28,
      "fatGrams": 14,
      "carbsGrams": 0
    },
    "meal": "dinner",
    "notes": null,
    "logged_at": {
      "$relativeHours": -2
    },
    "deleted_at": null,
    "deleted_by_request_id": null
  }
}

snapshot captured 2026-08-02T20:21:26.422Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched the common-food list to "Salmon" at 90% confidence.
Matched your past food logs to "Baked Salmon" at 82% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 2.9 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

FAILshould update the entry"Add olive oil to that salad, one tablespoon." (difficulty —)5.8s

Verdict Expected UPDATE — should update the entry. FAIL: WRONG ACTION — created a NEW entry on an UPDATE request.

Why verdict WRONG ACTION — created a NEW entry on an UPDATE 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 5.8s

1 · TTS said I could not confirm that was saved, so I did not mark it as done.

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

3 · App data rows written update_sync_failed food_log_entry: Chicken Salad Meal

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seeded value

{
  "table": "user_food_items",
  "record": {
    "id": "seed-garden-salad",
    "shared_food_id": null,
    "display_name": "Garden Salad",
    "brand": null,
    "serving_label": "bowl",
    "serving_quantity": 1,
    "serving_unit": "bowl",
    "macros_per_serving": {
      "calories": 120,
      "proteinGrams": 4,
      "fatGrams": 6,
      "carbsGrams": 12
    },
    "macros_per_100g": null,
    "times_logged": 1,
    "last_logged_at": null,
    "created_at": {
      "$relativeDays": -14
    }
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-log-salad-entry",
    "user_food_id": "seed-garden-salad",
    "food_name": "Garden Salad",
    "brand": null,
    "quantity": 1,
    "serving_label": "bowl",
    "macros": {
      "calories": 120,
      "proteinGrams": 4,
      "fatGrams": 6,
      "carbsGrams": 12
    },
    "meal": "lunch",
    "notes": null,
    "logged_at": {
      "$relativeHours": -2
    },
    "deleted_at": null,
    "deleted_by_request_id": null
  }
}

snapshot captured 2026-08-02T20:21:36.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 update the entry"Remove the cheese from that sandwich entry." (difficulty —)0.1s

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

1 · TTS said Which food entry did you want to correct?

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:

Seeded value

{
  "table": "user_food_items",
  "record": {
    "id": "seed-turkey-sandwich",
    "shared_food_id": null,
    "display_name": "Turkey Sandwich",
    "brand": "Home default",
    "serving_label": "sandwich",
    "serving_quantity": 1,
    "serving_unit": "sandwich",
    "macros_per_serving": {
      "calories": 380,
      "proteinGrams": 26,
      "fatGrams": 12,
      "carbsGrams": 38
    },
    "macros_per_100g": null,
    "times_logged": 1,
    "last_logged_at": null,
    "created_at": {
      "$relativeDays": -14
    }
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-log-sandwich-entry",
    "user_food_id": "seed-turkey-sandwich",
    "food_name": "Turkey Sandwich",
    "brand": "Home default",
    "quantity": 1,
    "serving_label": "sandwich",
    "macros": {
      "calories": 380,
      "proteinGrams": 26,
      "fatGrams": 12,
      "carbsGrams": 38
    },
    "meal": "lunch",
    "notes": null,
    "logged_at": {
      "$relativeHours": -2
    },
    "deleted_at": null,
    "deleted_by_request_id": null
  }
}

snapshot captured 2026-08-02T20:21:47.666Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 3.2 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

PASSshould update the entry"Change the yogurt to the vanilla Chobani one." (difficulty —)0.4s

Verdict Expected UPDATE — should update the entry. PASS: Updated as asked.

Why verdict Updated as asked.

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 Updated to the vanilla chobani one.

2 · Card shown Updated the food entry from "Mixed Berry Flavor Triple Zero Blended Greek Nonfat Yogurt" to "the vanilla chobani one".

3 · App data rows written updated food_log_entry: Zero Sugar Vanilla Yogurt ×1 (cup) 120 cal · 15g P · 9g C · 0g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seeded value

{
  "table": "user_food_items",
  "record": {
    "id": "seed-plain-yogurt",
    "shared_food_id": null,
    "display_name": "Plain Greek Yogurt",
    "brand": null,
    "serving_label": "cup",
    "serving_quantity": 1,
    "serving_unit": "cup",
    "macros_per_serving": {
      "calories": 130,
      "proteinGrams": 22,
      "fatGrams": 0,
      "carbsGrams": 8
    },
    "macros_per_100g": null,
    "times_logged": 1,
    "last_logged_at": null,
    "created_at": {
      "$relativeDays": -14
    }
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-log-yogurt-entry",
    "user_food_id": "seed-plain-yogurt",
    "food_name": "Plain Greek Yogurt",
    "brand": null,
    "quantity": 1,
    "serving_label": "cup",
    "macros": {
      "calories": 130,
      "proteinGrams": 22,
      "fatGrams": 0,
      "carbsGrams": 8
    },
    "meal": "snack",
    "notes": null,
    "logged_at": {
      "$relativeHours": -2
    },
    "deleted_at": null,
    "deleted_by_request_id": null
  }
}

snapshot captured 2026-08-02T20:21:59.238Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched the common-food list to "Plain Greek yogurt" at 90% confidence.
Matched your saved foods and aliases to "Chobani Zero Sugar Vanilla Yogurt" at 80% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 3.3 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

PASSshould update the entry"Actually the steak was 5 ounces cooked, not raw." (difficulty —)3.5s

Verdict Expected UPDATE — should update the entry. PASS: Updated as asked.

Why verdict Updated as asked.

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 Updated to 5 ounces cooked steak.

2 · Card shown Updated the food entry from "Grilled Steak" to "5 ounces cooked steak".

3 · App data rows written updated food_log_entry: Beef, Shoulder Steak, Boneless, Separable Lean Only, Trimmed To 0" Fat, Select, Cooked, Grilled ×5 (3 serving) 720 cal · 122g P · 0g C · 22g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seeded value

{
  "table": "user_food_items",
  "record": {
    "id": "seed-grilled-steak",
    "shared_food_id": null,
    "display_name": "Grilled Steak",
    "brand": null,
    "serving_label": "ounce",
    "serving_quantity": 6,
    "serving_unit": "oz",
    "macros_per_serving": {
      "calories": 340,
      "proteinGrams": 42,
      "fatGrams": 18,
      "carbsGrams": 0
    },
    "macros_per_100g": null,
    "times_logged": 1,
    "last_logged_at": null,
    "created_at": {
      "$relativeDays": -14
    }
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-log-steak-entry",
    "user_food_id": "seed-grilled-steak",
    "food_name": "Grilled Steak",
    "brand": null,
    "quantity": 1,
    "serving_label": "ounce",
    "macros": {
      "calories": 340,
      "proteinGrams": 42,
      "fatGrams": 18,
      "carbsGrams": 0
    },
    "meal": "dinner",
    "notes": null,
    "logged_at": {
      "$relativeHours": -3
    },
    "deleted_at": null,
    "deleted_by_request_id": null
  }
}

snapshot captured 2026-08-02T20:22:32.432Z

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"Set the smoothie to two servings." (difficulty —)1.8s

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

1 · TTS said I did not make any app changes. What would you like me to do with that?

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:

Seeded value

{
  "table": "user_food_items",
  "record": {
    "id": "seed-berry-smoothie-entry",
    "shared_food_id": null,
    "display_name": "Berry Smoothie",
    "brand": null,
    "serving_label": "serving",
    "serving_quantity": 1,
    "serving_unit": "serving",
    "macros_per_serving": {
      "calories": 260,
      "proteinGrams": 16,
      "fatGrams": 5,
      "carbsGrams": 38
    },
    "macros_per_100g": null,
    "times_logged": 1,
    "last_logged_at": null,
    "created_at": {
      "$relativeDays": -14
    }
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-log-smoothie-entry",
    "user_food_id": "seed-berry-smoothie-entry",
    "food_name": "Berry Smoothie",
    "brand": null,
    "quantity": 1,
    "serving_label": "serving",
    "macros": {
      "calories": 260,
      "proteinGrams": 16,
      "fatGrams": 5,
      "carbsGrams": 38
    },
    "meal": "snack",
    "notes": null,
    "logged_at": {
      "$relativeHours": -1
    },
    "deleted_at": null,
    "deleted_by_request_id": null
  }
}

snapshot captured 2026-08-02T20:22:38.268Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched your past food logs to "Homemade Smoothie" at 82% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 2.5 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

FAILshould update the entry"Change lunch from half avocado to a whole avocado." (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 I could not confirm that was saved, so I did not mark it as done.

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:

Seeded value

{
  "table": "user_food_items",
  "record": {
    "id": "seed-half-avocado",
    "shared_food_id": null,
    "display_name": "Avocado",
    "brand": null,
    "serving_label": "serving",
    "serving_quantity": 0.5,
    "serving_unit": "avocado",
    "macros_per_serving": {
      "calories": 120,
      "proteinGrams": 1.5,
      "fatGrams": 11,
      "carbsGrams": 6
    },
    "macros_per_100g": null,
    "times_logged": 1,
    "last_logged_at": null,
    "created_at": {
      "$relativeDays": -14
    }
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-log-avocado-lunch",
    "user_food_id": "seed-half-avocado",
    "food_name": "Avocado",
    "brand": null,
    "quantity": 1,
    "serving_label": "serving",
    "macros": {
      "calories": 120,
      "proteinGrams": 1.5,
      "fatGrams": 11,
      "carbsGrams": 6
    },
    "meal": "lunch",
    "notes": null,
    "logged_at": {
      "$relativeHours": -2
    },
    "deleted_at": null,
    "deleted_by_request_id": null
  }
}

snapshot captured 2026-08-02T20:22:49.513Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched the common-food list to "Avocado" at 90% confidence.
Matched your past food logs to "Avocado" at 82% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 3.4 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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 pasta sauce to pesto instead of marinara." (difficulty —)11.9s

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

1 · TTS said Which exact pasta sauce to pesto Protein Pancakes should replace Protein Pancakes?

2 · Card shown Which exact pasta sauce to pesto Protein Pancakes should replace Protein Pancakes?

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seeded value

{
  "table": "user_food_items",
  "record": {
    "id": "seed-pasta-marinara",
    "shared_food_id": null,
    "display_name": "Pasta with Marinara",
    "brand": "Home default",
    "serving_label": "serving",
    "serving_quantity": 1,
    "serving_unit": "serving",
    "macros_per_serving": {
      "calories": 420,
      "proteinGrams": 14,
      "fatGrams": 8,
      "carbsGrams": 72
    },
    "macros_per_100g": null,
    "times_logged": 1,
    "last_logged_at": null,
    "created_at": {
      "$relativeDays": -14
    }
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-log-pasta-entry",
    "user_food_id": "seed-pasta-marinara",
    "food_name": "Pasta with Marinara",
    "brand": "Home default",
    "quantity": 1,
    "serving_label": "serving",
    "macros": {
      "calories": 420,
      "proteinGrams": 14,
      "fatGrams": 8,
      "carbsGrams": 72
    },
    "meal": "dinner",
    "notes": null,
    "logged_at": {
      "$relativeHours": -3
    },
    "deleted_at": null,
    "deleted_by_request_id": null
  }
}

snapshot captured 2026-08-02T20:22:57.489Z

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 update the entry"Correction: those were turkey meatballs, not beef." (difficulty —)5.9s

Verdict Expected UPDATE — should update the entry. PASS: Updated as asked.

Why verdict Updated as asked.

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

1 · TTS said Updated to correction: those were turkey meatballs, not beef.

2 · Card shown Updated the food entry from "Protein Pancakes" to "correction: those were turkey meatballs, not beef".

3 · App data rows written updated food_log_entry: Turkey meatballs ×1 (28 g) 52 cal · 5g P · 1.7g C · 2.8g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seeded value

{
  "table": "user_food_items",
  "record": {
    "id": "seed-beef-meatballs",
    "shared_food_id": null,
    "display_name": "Beef Meatballs",
    "brand": null,
    "serving_label": "serving",
    "serving_quantity": 1,
    "serving_unit": "serving",
    "macros_per_serving": {
      "calories": 280,
      "proteinGrams": 22,
      "fatGrams": 18,
      "carbsGrams": 8
    },
    "macros_per_100g": null,
    "times_logged": 1,
    "last_logged_at": null,
    "created_at": {
      "$relativeDays": -14
    }
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-log-meatballs",
    "user_food_id": "seed-beef-meatballs",
    "food_name": "Beef Meatballs",
    "brand": null,
    "quantity": 1,
    "serving_label": "serving",
    "macros": {
      "calories": 280,
      "proteinGrams": 22,
      "fatGrams": 18,
      "carbsGrams": 8
    },
    "meal": "dinner",
    "notes": null,
    "logged_at": {
      "$relativeHours": -2
    },
    "deleted_at": null,
    "deleted_by_request_id": null
  }
}

snapshot captured 2026-08-02T20:23:29.584Z

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 burrito bowl no sour cream." (difficulty —)3.5s

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

1 · TTS said Which exact Burrito Bowl without sour cream should replace Burrito Bowl?

2 · Card shown Which exact Burrito Bowl without sour cream should replace Burrito Bowl?

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seeded value

{
  "table": "user_food_items",
  "record": {
    "id": "seed-burrito-bowl",
    "shared_food_id": null,
    "display_name": "Burrito Bowl",
    "brand": "Home default",
    "serving_label": "bowl",
    "serving_quantity": 1,
    "serving_unit": "bowl",
    "macros_per_serving": {
      "calories": 620,
      "proteinGrams": 35,
      "fatGrams": 18,
      "carbsGrams": 72
    },
    "macros_per_100g": null,
    "times_logged": 1,
    "last_logged_at": null,
    "created_at": {
      "$relativeDays": -14
    }
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-log-burrito-for-edit",
    "user_food_id": "seed-burrito-bowl",
    "food_name": "Burrito Bowl",
    "brand": "Home default",
    "quantity": 1,
    "serving_label": "bowl",
    "macros": {
      "calories": 620,
      "proteinGrams": 35,
      "fatGrams": 18,
      "carbsGrams": 72
    },
    "meal": "lunch",
    "notes": null,
    "logged_at": {
      "$relativeHours": -2
    },
    "deleted_at": null,
    "deleted_by_request_id": null
  }
}

snapshot captured 2026-08-02T20:23:44.242Z

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 update the entry"Change the cereal milk to almond milk." (difficulty —)0.6s

Verdict Expected UPDATE — should update the entry. PASS: Updated as asked.

Why verdict Updated as asked.

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 Updated to almond milk.

2 · Card shown Updated the food entry from "2% milk" to "almond milk".

3 · App data rows written updated food_log_entry: Unsweetened almond milk ×1 (100 g) 13 cal · 0.4g P · 0.3g C · 1.1g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seeded value

{
  "table": "user_food_items",
  "record": {
    "id": "seed-cereal-whole-milk",
    "shared_food_id": null,
    "display_name": "Cereal with Whole Milk",
    "brand": "Home default",
    "serving_label": "bowl",
    "serving_quantity": 1,
    "serving_unit": "bowl",
    "macros_per_serving": {
      "calories": 280,
      "proteinGrams": 9,
      "fatGrams": 8,
      "carbsGrams": 44
    },
    "macros_per_100g": null,
    "times_logged": 1,
    "last_logged_at": null,
    "created_at": {
      "$relativeDays": -14
    }
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-log-cereal",
    "user_food_id": "seed-cereal-whole-milk",
    "food_name": "Cereal with Whole Milk",
    "brand": "Home default",
    "quantity": 1,
    "serving_label": "bowl",
    "macros": {
      "calories": 280,
      "proteinGrams": 9,
      "fatGrams": 8,
      "carbsGrams": 44
    },
    "meal": "breakfast",
    "notes": null,
    "logged_at": {
      "$relativeHours": -3
    },
    "deleted_at": null,
    "deleted_by_request_id": null
  }
}

snapshot captured 2026-08-02T20:23:52.166Z

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 I just logged." (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 Which food entry did you want to correct?

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:

Seeded value

{
  "table": "user_food_items",
  "record": {
    "id": "seed-medium-banana",
    "shared_food_id": null,
    "display_name": "Medium Banana",
    "brand": null,
    "serving_label": "medium",
    "serving_quantity": 1,
    "serving_unit": "banana",
    "macros_per_serving": {
      "calories": 105,
      "proteinGrams": 1.3,
      "fatGrams": 0.4,
      "carbsGrams": 27
    },
    "macros_per_100g": null,
    "times_logged": 1,
    "last_logged_at": null,
    "created_at": {
      "$relativeDays": -14
    }
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-log-banana-recent",
    "user_food_id": "seed-medium-banana",
    "food_name": "Medium Banana",
    "brand": null,
    "quantity": 1,
    "serving_label": "medium",
    "macros": {
      "calories": 105,
      "proteinGrams": 1.3,
      "fatGrams": 0.4,
      "carbsGrams": 27
    },
    "meal": "snack",
    "notes": null,
    "logged_at": {
      "$relativeHours": -0.25
    },
    "deleted_at": null,
    "deleted_by_request_id": null
  }
}

snapshot captured 2026-08-02T20:24:07.211Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched the common-food list to "Banana" at 90% confidence.
Matched your saved foods and aliases to "one banana" at 64% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 2.9 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

FAILshould delete the entry"Remove breakfast oatmeal from today." (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 I could not find a list matching today. Which list has breakfast oatmeal?

2 · Card shown I could not find a list matching today. Which list has breakfast oatmeal?

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seeded value

{
  "table": "user_food_items",
  "record": {
    "id": "seed-oatmeal-bowl",
    "shared_food_id": null,
    "display_name": "Cooked Oatmeal Bowl",
    "brand": null,
    "serving_label": "bowl",
    "serving_quantity": 1,
    "serving_unit": "bowl",
    "macros_per_serving": {
      "calories": 180,
      "proteinGrams": 6,
      "fatGrams": 3,
      "carbsGrams": 32
    },
    "macros_per_100g": null,
    "times_logged": 1,
    "last_logged_at": null,
    "created_at": {
      "$relativeDays": -14
    }
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-log-today-bfast-oatmeal",
    "user_food_id": "seed-oatmeal-bowl",
    "food_name": "Cooked Oatmeal Bowl",
    "brand": null,
    "quantity": 1,
    "serving_label": "bowl",
    "macros": {
      "calories": 180,
      "proteinGrams": 6,
      "fatGrams": 3,
      "carbsGrams": 32
    },
    "meal": "breakfast",
    "notes": null,
    "logged_at": {
      "$relativeHours": -4
    },
    "deleted_at": null,
    "deleted_by_request_id": null
  }
}

snapshot captured 2026-08-02T20:24:18.399Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched the common-food list to "Cooked oatmeal" at 90% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 3.4 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

FAILshould delete the entry"Undo that protein bar 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 Which food entry did you want to correct?

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:

Seeded value

{
  "table": "user_food_items",
  "record": {
    "id": "seed-protein-bar",
    "shared_food_id": null,
    "display_name": "Chocolate Protein Bar",
    "brand": "Generic",
    "serving_label": "bar",
    "serving_quantity": 1,
    "serving_unit": "bar",
    "macros_per_serving": {
      "calories": 200,
      "proteinGrams": 20,
      "fatGrams": 7,
      "carbsGrams": 22
    },
    "macros_per_100g": null,
    "times_logged": 1,
    "last_logged_at": null,
    "created_at": {
      "$relativeDays": -14
    }
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-log-protein-bar-recent",
    "user_food_id": "seed-protein-bar",
    "food_name": "Chocolate Protein Bar",
    "brand": "Generic",
    "quantity": 1,
    "serving_label": "bar",
    "macros": {
      "calories": 200,
      "proteinGrams": 20,
      "fatGrams": 7,
      "carbsGrams": 22
    },
    "meal": "snack",
    "notes": null,
    "logged_at": {
      "$relativeHours": -0.5
    },
    "deleted_at": null,
    "deleted_by_request_id": null
  }
}

snapshot captured 2026-08-02T20:24:29.914Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched the common-food list to "Generic protein bar" at 90% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 3.5 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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 fries from dinner." (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 What would you like me to do with that?

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:

Seeded value

{
  "table": "user_food_items",
  "record": {
    "id": "seed-dinner-fries",
    "shared_food_id": null,
    "display_name": "French Fries",
    "brand": null,
    "serving_label": "serving",
    "serving_quantity": 1,
    "serving_unit": "serving",
    "macros_per_serving": {
      "calories": 320,
      "proteinGrams": 4,
      "fatGrams": 15,
      "carbsGrams": 42
    },
    "macros_per_100g": null,
    "times_logged": 1,
    "last_logged_at": null,
    "created_at": {
      "$relativeDays": -14
    }
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-log-dinner-fries",
    "user_food_id": "seed-dinner-fries",
    "food_name": "French Fries",
    "brand": null,
    "quantity": 1,
    "serving_label": "serving",
    "macros": {
      "calories": 320,
      "proteinGrams": 4,
      "fatGrams": 15,
      "carbsGrams": 42
    },
    "meal": "dinner",
    "notes": null,
    "logged_at": {
      "$relativeHours": -2
    },
    "deleted_at": null,
    "deleted_by_request_id": null
  }
}

snapshot captured 2026-08-02T20:24:42.530Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 2.8 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

FAILshould delete the entry"Delete my lunch salad." (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 Which food entry did you want to correct?

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:

Seeded value

{
  "table": "user_food_items",
  "record": {
    "id": "seed-lunch-salad",
    "shared_food_id": null,
    "display_name": "Lunch Salad",
    "brand": "Home default",
    "serving_label": "bowl",
    "serving_quantity": 1,
    "serving_unit": "bowl",
    "macros_per_serving": {
      "calories": 280,
      "proteinGrams": 18,
      "fatGrams": 14,
      "carbsGrams": 18
    },
    "macros_per_100g": null,
    "times_logged": 1,
    "last_logged_at": null,
    "created_at": {
      "$relativeDays": -14
    }
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-log-lunch-salad-del",
    "user_food_id": "seed-lunch-salad",
    "food_name": "Lunch Salad",
    "brand": "Home default",
    "quantity": 1,
    "serving_label": "bowl",
    "macros": {
      "calories": 280,
      "proteinGrams": 18,
      "fatGrams": 14,
      "carbsGrams": 18
    },
    "meal": "lunch",
    "notes": null,
    "logged_at": {
      "$relativeHours": -3
    },
    "deleted_at": null,
    "deleted_by_request_id": null
  }
}

snapshot captured 2026-08-02T20:24:53.694Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched your past food logs to "Home default Lunch Salad" at 82% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 2.6 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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 second coffee 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 Which food entry did you want to correct?

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:

Seeded value

{
  "table": "user_food_items",
  "record": {
    "id": "seed-coffee-entry",
    "shared_food_id": null,
    "display_name": "Coffee",
    "brand": null,
    "serving_label": "cup",
    "serving_quantity": 1,
    "serving_unit": "cup",
    "macros_per_serving": {
      "calories": 5,
      "proteinGrams": 0,
      "fatGrams": 0,
      "carbsGrams": 1
    },
    "macros_per_100g": null,
    "times_logged": 1,
    "last_logged_at": null,
    "created_at": {
      "$relativeDays": -14
    }
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-log-coffee-1",
    "user_food_id": "seed-coffee-entry",
    "food_name": "Coffee",
    "brand": null,
    "quantity": 1,
    "serving_label": "cup",
    "macros": {
      "calories": 5,
      "proteinGrams": 0,
      "fatGrams": 0,
      "carbsGrams": 1
    },
    "meal": "breakfast",
    "notes": null,
    "logged_at": {
      "$relativeHours": -5
    },
    "deleted_at": null,
    "deleted_by_request_id": null
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-log-coffee-2",
    "user_food_id": "seed-coffee-entry",
    "food_name": "Coffee",
    "brand": null,
    "quantity": 1,
    "serving_label": "cup",
    "macros": {
      "calories": 5,
      "proteinGrams": 0,
      "fatGrams": 0,
      "carbsGrams": 1
    },
    "meal": "snack",
    "notes": null,
    "logged_at": {
      "$relativeHours": -1
    },
    "deleted_at": null,
    "deleted_by_request_id": null
  }
}

snapshot captured 2026-08-02T20:25:04.966Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched your saved foods and aliases to "coffee" at 90% confidence.
Matched the common-food list to "Coffee" at 90% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 2.5 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

FAILshould delete the entry"Cancel the snack I added a minute ago." (difficulty —)3.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 3.0s

1 · TTS said What would you like me to do with that?

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:

Seeded value

{
  "table": "user_food_items",
  "record": {
    "id": "seed-recent-snack",
    "shared_food_id": null,
    "display_name": "Greek Yogurt Cup",
    "brand": null,
    "serving_label": "cup",
    "serving_quantity": 1,
    "serving_unit": "cup",
    "macros_per_serving": {
      "calories": 130,
      "proteinGrams": 15,
      "fatGrams": 0,
      "carbsGrams": 12
    },
    "macros_per_100g": null,
    "times_logged": 1,
    "last_logged_at": null,
    "created_at": {
      "$relativeDays": -14
    }
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-log-snack-minute-ago",
    "user_food_id": "seed-recent-snack",
    "food_name": "Greek Yogurt Cup",
    "brand": null,
    "quantity": 1,
    "serving_label": "cup",
    "macros": {
      "calories": 130,
      "proteinGrams": 15,
      "fatGrams": 0,
      "carbsGrams": 12
    },
    "meal": "snack",
    "notes": null,
    "logged_at": {
      "$relativeHours": -0.1
    },
    "deleted_at": null,
    "deleted_by_request_id": null
  }
}

snapshot captured 2026-08-02T20:25:19.099Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 2.9 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

FAILshould delete the entry"Erase the pizza from yesterday night." (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 Which food entry did you want to correct?

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:

Seeded value

{
  "table": "user_food_items",
  "record": {
    "id": "seed-yesterday-pizza",
    "shared_food_id": null,
    "display_name": "Cheese Pizza Slice",
    "brand": null,
    "serving_label": "slice",
    "serving_quantity": 2,
    "serving_unit": "slice",
    "macros_per_serving": {
      "calories": 570,
      "proteinGrams": 24,
      "fatGrams": 22,
      "carbsGrams": 64
    },
    "macros_per_100g": null,
    "times_logged": 1,
    "last_logged_at": null,
    "created_at": {
      "$relativeDays": -14
    }
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-log-yesterday-pizza",
    "user_food_id": "seed-yesterday-pizza",
    "food_name": "Cheese Pizza Slice",
    "brand": null,
    "quantity": 1,
    "serving_label": "slice",
    "macros": {
      "calories": 570,
      "proteinGrams": 24,
      "fatGrams": 22,
      "carbsGrams": 64
    },
    "meal": "dinner",
    "notes": null,
    "logged_at": {
      "$relativeDays": -1
    },
    "deleted_at": null,
    "deleted_by_request_id": null
  }
}

snapshot captured 2026-08-02T20:25:30.297Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched the common-food list to "Pizza" at 90% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 3.1 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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 guacamole line from my burrito bowl." (difficulty —)0.3s

Verdict Expected DELETE — should delete the entry. FAIL: WRONG TARGET — deleted Guacamole instead of guacamole component.

Why verdict WRONG TARGET — deleted Guacamole instead of guacamole component.

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 Deleted Guacamole.

2 · Card shown Deleted Guacamole.

3 · App data rows written deleted food_log_entry:

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seeded value

{
  "table": "user_food_items",
  "record": {
    "id": "seed-burrito-guac-parent",
    "shared_food_id": null,
    "display_name": "Burrito Bowl",
    "brand": "Home default",
    "serving_label": "bowl",
    "serving_quantity": 1,
    "serving_unit": "bowl",
    "macros_per_serving": {
      "calories": 620,
      "proteinGrams": 35,
      "fatGrams": 18,
      "carbsGrams": 72
    },
    "macros_per_100g": null,
    "times_logged": 1,
    "last_logged_at": null,
    "created_at": {
      "$relativeDays": -14
    }
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-log-burrito-parent",
    "user_food_id": "seed-burrito-guac-parent",
    "food_name": "Burrito Bowl",
    "brand": "Home default",
    "quantity": 1,
    "serving_label": "bowl",
    "macros": {
      "calories": 620,
      "proteinGrams": 35,
      "fatGrams": 18,
      "carbsGrams": 72
    },
    "meal": "lunch",
    "notes": null,
    "logged_at": {
      "$relativeHours": -2
    },
    "deleted_at": null,
    "deleted_by_request_id": null
  }
}

Seeded value

{
  "table": "user_food_items",
  "record": {
    "id": "seed-guacamole",
    "shared_food_id": null,
    "display_name": "Guacamole",
    "brand": null,
    "serving_label": "tablespoon",
    "serving_quantity": 2,
    "serving_unit": "tbsp",
    "macros_per_serving": {
      "calories": 50,
      "proteinGrams": 1,
      "fatGrams": 4.5,
      "carbsGrams": 3
    },
    "macros_per_100g": null,
    "times_logged": 1,
    "last_logged_at": null,
    "created_at": {
      "$relativeDays": -14
    }
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-log-guac-component",
    "user_food_id": "seed-guacamole",
    "food_name": "Guacamole",
    "brand": null,
    "quantity": 2,
    "serving_label": "tbsp",
    "macros": {
      "calories": 50,
      "proteinGrams": 1,
      "fatGrams": 4.5,
      "carbsGrams": 3
    },
    "meal": "lunch",
    "notes": "component of burrito bowl",
    "logged_at": {
      "$relativeHours": -2
    },
    "deleted_at": null,
    "deleted_by_request_id": null
  }
}

snapshot captured 2026-08-02T20:25:48.732Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 3.3 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

FAILshould delete the entry"Remove my post-workout shake from today." (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 Which food entry did you want to correct?

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:

Seeded value

{
  "table": "user_food_items",
  "record": {
    "id": "seed-post-workout-shake",
    "shared_food_id": null,
    "display_name": "Post-Workout Protein Shake",
    "brand": "Premier Protein",
    "serving_label": "bottle",
    "serving_quantity": 1,
    "serving_unit": "bottle",
    "macros_per_serving": {
      "calories": 160,
      "proteinGrams": 30,
      "fatGrams": 3,
      "carbsGrams": 5
    },
    "macros_per_100g": null,
    "times_logged": 1,
    "last_logged_at": null,
    "created_at": {
      "$relativeDays": -14
    }
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-log-post-workout-shake",
    "user_food_id": "seed-post-workout-shake",
    "food_name": "Post-Workout Protein Shake",
    "brand": "Premier Protein",
    "quantity": 1,
    "serving_label": "bottle",
    "macros": {
      "calories": 160,
      "proteinGrams": 30,
      "fatGrams": 3,
      "carbsGrams": 5
    },
    "meal": "snack",
    "notes": null,
    "logged_at": {
      "$relativeHours": -2
    },
    "deleted_at": null,
    "deleted_by_request_id": null
  }
}

snapshot captured 2026-08-02T20:25:52.945Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched your past food logs to "Premier Protein Post-Workout Protein Shake" at 82% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 2.8 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

UNVERIFIEDunclassifiedshould answer the query"Give me the calorie count for 100 grams of avocado." (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 Avocado has about 160 calories per 100 g.

2 · Card shown Avocado has about 160 calories per 100 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-08-02T20:26:04.196Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched the common-food list to "Avocado" at 90% confidence.
Matched your past food logs to "Avocado" at 82% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 3.0 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

UNVERIFIEDunclassifiedshould answer the query"What has more protein, Greek yogurt or cottage cheese?" (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 I understood the nutrition question, but I could not find a solid number for that food yet. Nothing was logged.

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-08-02T20:26:16.208Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched your past food logs to "Cottage cheese" at 82% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 4.1 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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 in a cup of cooked quinoa?" (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 Cooked quinoa has about 39.4g carbs per 1 cup.

2 · Card shown Cooked quinoa has about 39.4g carbs per 1 cup.

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T20:26:26.724Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched the common-food list to "Cooked quinoa" at 90% confidence.
Matched your past food logs to "Cooked quinoa" at 82% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 3.3 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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 enough protein at breakfast?" (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 — I do not see enough protein at breakfast logged today.

2 · Card shown No — I do not see enough protein at breakfast logged today.

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seeded value

{
  "table": "user_food_items",
  "record": {
    "id": "seed-breakfast-eggs",
    "shared_food_id": null,
    "display_name": "Scrambled Eggs",
    "brand": null,
    "serving_label": "serving",
    "serving_quantity": 1,
    "serving_unit": "serving",
    "macros_per_serving": {
      "calories": 220,
      "proteinGrams": 18,
      "fatGrams": 15,
      "carbsGrams": 2
    },
    "macros_per_100g": null,
    "times_logged": 1,
    "last_logged_at": null,
    "created_at": {
      "$relativeDays": -14
    }
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-log-bfast-eggs-q",
    "user_food_id": "seed-breakfast-eggs",
    "food_name": "Scrambled Eggs",
    "brand": null,
    "quantity": 1,
    "serving_label": "serving",
    "macros": {
      "calories": 220,
      "proteinGrams": 18,
      "fatGrams": 15,
      "carbsGrams": 2
    },
    "meal": "breakfast",
    "notes": null,
    "logged_at": {
      "$relativeHours": -5
    },
    "deleted_at": null,
    "deleted_by_request_id": null
  }
}

Seeded value

{
  "table": "user_food_items",
  "record": {
    "id": "seed-breakfast-toast",
    "shared_food_id": null,
    "display_name": "Whole Wheat Toast",
    "brand": null,
    "serving_label": "slice",
    "serving_quantity": 2,
    "serving_unit": "slice",
    "macros_per_serving": {
      "calories": 160,
      "proteinGrams": 8,
      "fatGrams": 2,
      "carbsGrams": 28
    },
    "macros_per_100g": null,
    "times_logged": 1,
    "last_logged_at": null,
    "created_at": {
      "$relativeDays": -14
    }
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-log-bfast-toast-q",
    "user_food_id": "seed-breakfast-toast",
    "food_name": "Whole Wheat Toast",
    "brand": null,
    "quantity": 1,
    "serving_label": "slice",
    "macros": {
      "calories": 160,
      "proteinGrams": 8,
      "fatGrams": 2,
      "carbsGrams": 28
    },
    "meal": "breakfast",
    "notes": null,
    "logged_at": {
      "$relativeHours": -5
    },
    "deleted_at": null,
    "deleted_by_request_id": null
  }
}

snapshot captured 2026-08-02T20:26:49.466Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 3.0 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

UNVERIFIEDunclassifiedshould answer the query"Show lunch from yesterday." (difficulty —)0.2s

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

1 · TTS said Opening Food History.

2 · Card shown Opening Food History.

4 · UI did navigated to "food" screen

5 · Seed/context data

Seeded starting state:

Seeded value

{
  "table": "user_food_items",
  "record": {
    "id": "seed-yesterday-lunch-sandwich",
    "shared_food_id": null,
    "display_name": "Turkey Sandwich",
    "brand": "Home default",
    "serving_label": "sandwich",
    "serving_quantity": 1,
    "serving_unit": "sandwich",
    "macros_per_serving": {
      "calories": 380,
      "proteinGrams": 26,
      "fatGrams": 12,
      "carbsGrams": 38
    },
    "macros_per_100g": null,
    "times_logged": 1,
    "last_logged_at": null,
    "created_at": {
      "$relativeDays": -14
    }
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-log-yest-lunch-sand",
    "user_food_id": "seed-yesterday-lunch-sandwich",
    "food_name": "Turkey Sandwich",
    "brand": "Home default",
    "quantity": 1,
    "serving_label": "sandwich",
    "macros": {
      "calories": 380,
      "proteinGrams": 26,
      "fatGrams": 12,
      "carbsGrams": 38
    },
    "meal": "lunch",
    "notes": null,
    "logged_at": {
      "$relativeDays": -1
    },
    "deleted_at": null,
    "deleted_by_request_id": null
  }
}

Seeded value

{
  "table": "user_food_items",
  "record": {
    "id": "seed-yesterday-lunch-chips",
    "shared_food_id": null,
    "display_name": "Potato Chips",
    "brand": null,
    "serving_label": "ounce",
    "serving_quantity": 1,
    "serving_unit": "oz",
    "macros_per_serving": {
      "calories": 150,
      "proteinGrams": 2,
      "fatGrams": 10,
      "carbsGrams": 15
    },
    "macros_per_100g": null,
    "times_logged": 1,
    "last_logged_at": null,
    "created_at": {
      "$relativeDays": -14
    }
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-log-yest-lunch-chips",
    "user_food_id": "seed-yesterday-lunch-chips",
    "food_name": "Potato Chips",
    "brand": null,
    "quantity": 1,
    "serving_label": "ounce",
    "macros": {
      "calories": 150,
      "proteinGrams": 2,
      "fatGrams": 10,
      "carbsGrams": 15
    },
    "meal": "lunch",
    "notes": null,
    "logged_at": {
      "$relativeDays": -1
    },
    "deleted_at": null,
    "deleted_by_request_id": null
  }
}

snapshot captured 2026-08-02T20:27:00.773Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 2.9 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

FAILshould answer the query"Give me the sodium count for a Subway turkey sandwich." (difficulty —)0.6s

Verdict Expected QUERY — should answer the query. FAIL: answer did not state expected numeric value(s): sodiumMg

Why verdict answer did not state expected numeric value(s): sodiumMg

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 I understood the nutrition question, but I could not find a solid number for that food yet. Nothing was logged.

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-08-02T20:27:12.622Z

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"Which is lower calorie, ranch or balsamic vinaigrette?" (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 I understood the nutrition question, but I could not find a solid number for that food yet. Nothing was logged.

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-08-02T20:27:20.041Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched the common-food list to "Balsamic vinaigrette" at 90% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 4.7 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

UNVERIFIEDunclassifiedshould answer the query"Estimate calories added by two tablespoons of olive oil." (difficulty —)0.2s

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

1 · TTS said Olive oil has about 241 calories per 2 tbsp.

2 · Card shown Olive oil has about 241 calories per 2 tbsp.

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T20:27:35.087Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched the common-food list to "Olive oil" at 90% confidence.
Matched your past food logs to "Olive oil" at 82% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 3.3 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

UNVERIFIEDunclassifiedshould answer the query"What is my average breakfast calories this week?" (difficulty —)0.1s

Verdict Expected QUERY — should answer the query. UNVERIFIED: Informational non-gating row (excluded from pass/fail tallies).

Why verdict Informational non-gating row (excluded from pass/fail tallies).

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 Average breakfast calories: 361 calories.

2 · Card shown Average breakfast calories: 361 calories.

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seeded value

{
  "table": "user_food_items",
  "record": {
    "id": "seed-week-bfast-oats",
    "shared_food_id": null,
    "display_name": "Cooked Oatmeal",
    "brand": null,
    "serving_label": "cup",
    "serving_quantity": 1,
    "serving_unit": "cup",
    "macros_per_serving": {
      "calories": 150,
      "proteinGrams": 6,
      "fatGrams": 3,
      "carbsGrams": 27
    },
    "macros_per_100g": null,
    "times_logged": 1,
    "last_logged_at": null,
    "created_at": {
      "$relativeDays": -14
    }
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-log-week-bfast-1",
    "user_food_id": "seed-week-bfast-oats",
    "food_name": "Cooked Oatmeal",
    "brand": null,
    "quantity": 1,
    "serving_label": "cup",
    "macros": {
      "calories": 150,
      "proteinGrams": 6,
      "fatGrams": 3,
      "carbsGrams": 27
    },
    "meal": "breakfast",
    "notes": null,
    "logged_at": {
      "$relativeDays": -1
    },
    "deleted_at": null,
    "deleted_by_request_id": null
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-log-week-bfast-2",
    "user_food_id": "seed-week-bfast-oats",
    "food_name": "Cooked Oatmeal",
    "brand": null,
    "quantity": 1,
    "serving_label": "cup",
    "macros": {
      "calories": 150,
      "proteinGrams": 6,
      "fatGrams": 3,
      "carbsGrams": 27
    },
    "meal": "breakfast",
    "notes": null,
    "logged_at": {
      "$relativeDays": -3
    },
    "deleted_at": null,
    "deleted_by_request_id": null
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-log-week-bfast-3",
    "user_food_id": "seed-week-bfast-oats",
    "food_name": "Cooked Oatmeal",
    "brand": null,
    "quantity": 1,
    "serving_label": "cup",
    "macros": {
      "calories": 150,
      "proteinGrams": 6,
      "fatGrams": 3,
      "carbsGrams": 27
    },
    "meal": "breakfast",
    "notes": null,
    "logged_at": {
      "$relativeDays": -5
    },
    "deleted_at": null,
    "deleted_by_request_id": null
  }
}

snapshot captured 2026-08-02T20:27:46.998Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 3.9 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

PASSshould answer the query"Give me the fiber count for black beans." (difficulty —)0.2s

Verdict Expected QUERY — should answer the query. PASS: Query answered within tolerance.

Why verdict Query answered within tolerance.

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 Black beans has about 8.7g fiber per 100 g.

2 · Card shown Black beans has about 8.7g fiber per 100 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-08-02T20:27:57.724Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched the common-food list to "Black beans" at 90% confidence.
Matched your past food logs to "Black beans" at 82% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 3.2 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

FAILshould answer the query"Was dinner higher calorie than lunch today?" (difficulty —)0.1s

Verdict Expected QUERY — should answer the query. FAIL: answer did not state expected numeric value(s): calories

Why verdict answer did not state expected numeric value(s): calories

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 Yes — lunch was higher calorie today (6855 vs 4405 for dinner).

2 · Card shown Yes — lunch was higher calorie today (6855 vs 4405 for dinner).

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seeded value

{
  "table": "user_food_items",
  "record": {
    "id": "seed-today-lunch-salad",
    "shared_food_id": null,
    "display_name": "Chicken Salad",
    "brand": "Home default",
    "serving_label": "bowl",
    "serving_quantity": 1,
    "serving_unit": "bowl",
    "macros_per_serving": {
      "calories": 350,
      "proteinGrams": 32,
      "fatGrams": 14,
      "carbsGrams": 18
    },
    "macros_per_100g": null,
    "times_logged": 1,
    "last_logged_at": null,
    "created_at": {
      "$relativeDays": -14
    }
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-log-today-lunch-cmp",
    "user_food_id": "seed-today-lunch-salad",
    "food_name": "Chicken Salad",
    "brand": "Home default",
    "quantity": 1,
    "serving_label": "bowl",
    "macros": {
      "calories": 350,
      "proteinGrams": 32,
      "fatGrams": 14,
      "carbsGrams": 18
    },
    "meal": "lunch",
    "notes": null,
    "logged_at": {
      "$relativeHours": -5
    },
    "deleted_at": null,
    "deleted_by_request_id": null
  }
}

Seeded value

{
  "table": "user_food_items",
  "record": {
    "id": "seed-today-dinner-steak",
    "shared_food_id": null,
    "display_name": "Grilled Steak Dinner",
    "brand": "Home default",
    "serving_label": "plate",
    "serving_quantity": 1,
    "serving_unit": "plate",
    "macros_per_serving": {
      "calories": 720,
      "proteinGrams": 48,
      "fatGrams": 32,
      "carbsGrams": 40
    },
    "macros_per_100g": null,
    "times_logged": 1,
    "last_logged_at": null,
    "created_at": {
      "$relativeDays": -14
    }
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-log-today-dinner-cmp",
    "user_food_id": "seed-today-dinner-steak",
    "food_name": "Grilled Steak Dinner",
    "brand": "Home default",
    "quantity": 1,
    "serving_label": "plate",
    "macros": {
      "calories": 720,
      "proteinGrams": 48,
      "fatGrams": 32,
      "carbsGrams": 40
    },
    "meal": "dinner",
    "notes": null,
    "logged_at": {
      "$relativeHours": -1
    },
    "deleted_at": null,
    "deleted_by_request_id": null
  }
}

snapshot captured 2026-08-02T20:28:09.571Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 3.9 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

UNVERIFIEDunclassifiedshould answer the query"What are macros for a large egg?" (difficulty —)0.2s

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

1 · TTS said Egg per 1 egg: 72 calories, 6.3g protein, 0.4g carbs, 4.8g fat.

2 · Card shown Egg per 1 egg: 72 calories, 6.3g protein, 0.4g carbs, 4.8g fat.

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T20:28:20.339Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched the common-food list to "Egg" at 90% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 3.3 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

FAILshould answer the query"Show today’s protein total so far." (difficulty —)4.9s

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

1 · TTS said What exact food and amount should I use for show todays protein total so far? I did not log it yet because I could not safely finish that food log.

2 · Card shown What exact food and amount should I use for show todays protein total so far? 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:

Seeded value

{
  "table": "user_food_items",
  "record": {
    "id": "seed-today-protein-entry",
    "shared_food_id": null,
    "display_name": "Grilled Chicken Breast",
    "brand": null,
    "serving_label": "ounce",
    "serving_quantity": 6,
    "serving_unit": "oz",
    "macros_per_serving": {
      "calories": 280,
      "proteinGrams": 52,
      "fatGrams": 6,
      "carbsGrams": 0
    },
    "macros_per_100g": null,
    "times_logged": 1,
    "last_logged_at": null,
    "created_at": {
      "$relativeDays": -14
    }
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-log-today-protein",
    "user_food_id": "seed-today-protein-entry",
    "food_name": "Grilled Chicken Breast",
    "brand": null,
    "quantity": 1,
    "serving_label": "ounce",
    "macros": {
      "calories": 280,
      "proteinGrams": 52,
      "fatGrams": 6,
      "carbsGrams": 0
    },
    "meal": "lunch",
    "notes": null,
    "logged_at": {
      "$relativeHours": -3
    },
    "deleted_at": null,
    "deleted_by_request_id": null
  }
}

snapshot captured 2026-08-02T20:28:36.389Z

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 answer the query"Is quinoa or white rice better for fiber?" (difficulty —)0.2s

Verdict Expected QUERY — should answer the query. PASS: Query answered within tolerance.

Why verdict Query answered within tolerance.

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 Cooked quinoa is higher in fiber (2.8g fiber per 100 g) than Cooked white rice (0.4g fiber per 100 g).

2 · Card shown Cooked quinoa is higher in fiber (2.8g fiber per 100 g) than Cooked white rice (0.4g fiber per 100 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-08-02T20:28:48.197Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched the common-food list to "Cooked white rice" at 90% confidence.
Matched your past food logs to "Cooked white rice" at 82% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 3.7 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

UNVERIFIEDunclassifiedshould answer the query"Give me calories for a Chick-fil-A grilled chicken sandwich." (difficulty —)0.7s

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

1 · TTS said I understood the nutrition question, but I could not find a solid number for that food yet. Nothing was logged.

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-08-02T20:28:59.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)

UNVERIFIEDunclassifiedshould answer the query"What was my biggest meal yesterday?" (difficulty —)2.2s

Verdict Expected QUERY — should answer the query. UNVERIFIED: Informational non-gating row (excluded from pass/fail tallies).

Why verdict Informational non-gating row (excluded from pass/fail tallies).

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 I understood your nutrition question, but I can't access your meal history directly. To compare your meals from yesterday, please say: "Open Food History" or "Show yesterday's meals".

2 · Card shown I understood your nutrition question, but I can't access your meal history directly. To compare your meals from yesterday, please say: "Open Food History" or "Show yesterday's meals".

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seeded value

{
  "table": "user_food_items",
  "record": {
    "id": "seed-today-lunch-salad",
    "shared_food_id": null,
    "display_name": "Chicken Salad",
    "brand": "Home default",
    "serving_label": "bowl",
    "serving_quantity": 1,
    "serving_unit": "bowl",
    "macros_per_serving": {
      "calories": 350,
      "proteinGrams": 32,
      "fatGrams": 14,
      "carbsGrams": 18
    },
    "macros_per_100g": null,
    "times_logged": 1,
    "last_logged_at": null,
    "created_at": {
      "$relativeDays": -14
    }
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-log-yest-meal-lunch",
    "user_food_id": "seed-today-lunch-salad",
    "food_name": "Chicken Salad",
    "brand": "Home default",
    "quantity": 1,
    "serving_label": "bowl",
    "macros": {
      "calories": 350,
      "proteinGrams": 32,
      "fatGrams": 14,
      "carbsGrams": 18
    },
    "meal": "lunch",
    "notes": null,
    "logged_at": {
      "$relativeDays": -1
    },
    "deleted_at": null,
    "deleted_by_request_id": null
  }
}

Seeded value

{
  "table": "user_food_items",
  "record": {
    "id": "seed-today-dinner-steak",
    "shared_food_id": null,
    "display_name": "Grilled Steak Dinner",
    "brand": "Home default",
    "serving_label": "plate",
    "serving_quantity": 1,
    "serving_unit": "plate",
    "macros_per_serving": {
      "calories": 720,
      "proteinGrams": 48,
      "fatGrams": 32,
      "carbsGrams": 40
    },
    "macros_per_100g": null,
    "times_logged": 1,
    "last_logged_at": null,
    "created_at": {
      "$relativeDays": -14
    }
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-log-yest-meal-dinner",
    "user_food_id": "seed-today-dinner-steak",
    "food_name": "Grilled Steak Dinner",
    "brand": "Home default",
    "quantity": 1,
    "serving_label": "plate",
    "macros": {
      "calories": 720,
      "proteinGrams": 48,
      "fatGrams": 32,
      "carbsGrams": 40
    },
    "meal": "dinner",
    "notes": null,
    "logged_at": {
      "$relativeDays": -1
    },
    "deleted_at": null,
    "deleted_by_request_id": null
  }
}

snapshot captured 2026-08-02T20:29:07.476Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 3.2 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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 grams of carbs are in a medium banana?" (difficulty —)0.2s

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

1 · TTS said Banana has about 27.1g carbs per 1 medium banana.

2 · Card shown Banana has about 27.1g carbs per 1 medium 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-08-02T20:29:24.470Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched your saved foods and aliases to "a medium banana" at 90% confidence.
Matched the common-food list to "Banana" at 90% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 2.6 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

UNVERIFIEDunclassifiedshould answer the query"What foods did I log with more than 30 grams protein today?" (difficulty —)0.1s

Verdict Expected QUERY — should answer the query. UNVERIFIED: Informational non-gating row (excluded from pass/fail tallies).

Why verdict Informational non-gating row (excluded from pass/fail tallies).

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 — I do not see with more than 30 grams protein logged today.

2 · Card shown No — I do not see with more than 30 grams protein logged today.

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seeded value

{
  "table": "user_food_items",
  "record": {
    "id": "seed-high-protein-meal",
    "shared_food_id": null,
    "display_name": "Chicken and Rice",
    "brand": "Home default",
    "serving_label": "plate",
    "serving_quantity": 1,
    "serving_unit": "plate",
    "macros_per_serving": {
      "calories": 480,
      "proteinGrams": 45,
      "fatGrams": 10,
      "carbsGrams": 48
    },
    "macros_per_100g": null,
    "times_logged": 1,
    "last_logged_at": null,
    "created_at": {
      "$relativeDays": -14
    }
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-log-high-protein-today",
    "user_food_id": "seed-high-protein-meal",
    "food_name": "Chicken and Rice",
    "brand": "Home default",
    "quantity": 1,
    "serving_label": "plate",
    "macros": {
      "calories": 480,
      "proteinGrams": 45,
      "fatGrams": 10,
      "carbsGrams": 48
    },
    "meal": "lunch",
    "notes": null,
    "logged_at": {
      "$relativeHours": -2
    },
    "deleted_at": null,
    "deleted_by_request_id": null
  }
}

snapshot captured 2026-08-02T20:29:36.711Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 4.2 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

UNVERIFIEDunclassifiedshould answer the query"Does peanut butter have more fat than almond butter?" (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 I understood the nutrition question, but I could not find a solid number for that food yet. Nothing was logged.

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-08-02T20:29:48.181Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched the common-food list to "Peanut butter" at 90% confidence.
Matched your past food logs to "Peanut butter" at 82% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 4.5 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

UNVERIFIEDunclassifiedshould answer the query"Show calories remaining for a 2200 calorie 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 You are about 29162 calories over today's 2100 calorie budget (31262 logged).

2 · Card shown You are about 29162 calories over today's 2100 calorie budget (31262 logged).

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seeded value

{
  "table": "user_food_items",
  "record": {
    "id": "seed-today-protein-entry",
    "shared_food_id": null,
    "display_name": "Grilled Chicken Breast",
    "brand": null,
    "serving_label": "ounce",
    "serving_quantity": 6,
    "serving_unit": "oz",
    "macros_per_serving": {
      "calories": 280,
      "proteinGrams": 52,
      "fatGrams": 6,
      "carbsGrams": 0
    },
    "macros_per_100g": null,
    "times_logged": 1,
    "last_logged_at": null,
    "created_at": {
      "$relativeDays": -14
    }
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-log-today-cals-1",
    "user_food_id": "seed-today-protein-entry",
    "food_name": "Grilled Chicken Breast",
    "brand": null,
    "quantity": 1,
    "serving_label": "ounce",
    "macros": {
      "calories": 280,
      "proteinGrams": 52,
      "fatGrams": 6,
      "carbsGrams": 0
    },
    "meal": "lunch",
    "notes": null,
    "logged_at": {
      "$relativeHours": -4
    },
    "deleted_at": null,
    "deleted_by_request_id": null
  }
}

Seeded value

{
  "table": "user_module_preferences",
  "record": {
    "id": "seed-pref-nutrition-2200",
    "module_key": "nutrition",
    "preferences": {
      "dailyCalorieGoal": 2200,
      "proteinGoalGrams": 150,
      "fatGoalGrams": 70,
      "carbsGoalGrams": 220
    },
    "updated_at": {
      "$relativeDays": -1
    },
    "deleted_at": null,
    "deleted_by_request_id": null
  }
}

snapshot captured 2026-08-02T20:29:58.683Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 3.7 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

PASSshould apply the setting"Set my daily protein goal to 150 grams." (difficulty —)0.2s

Verdict Expected SETTINGS — should apply the setting. PASS: Applied setting.

Why verdict Applied setting.

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 Okay, I updated your daily protein goal to 150 grams.

2 · Card shown Okay, I updated your daily protein goal to 150 grams.

4 · UI did navigated to "settings" 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-08-02T20:30:09.692Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 3.3 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

PASSshould apply the setting"Change my calorie target to 2100 per day." (difficulty —)0.1s

Verdict Expected SETTINGS — should apply the setting. PASS: Applied setting.

Why verdict Applied setting.

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 Okay, I updated your daily calorie goal to 2100 calories.

2 · Card shown Okay, I updated your daily calorie goal to 2100 calories.

4 · UI did navigated to "settings" 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-08-02T20:30:17.240Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 3.4 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

UNVERIFIEDunclassifiedshould apply the setting"Use grams by default for food weights." (difficulty —)0.1s

Verdict Expected SETTINGS — should apply the setting. UNVERIFIED: Informational non-gating row (excluded from pass/fail tallies).

Why verdict Informational non-gating row (excluded from pass/fail tallies).

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 Okay, I will use grams by default for food weights.

2 · Card shown Okay, I will use grams by default for food weights.

4 · UI did navigated to "settings" 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-08-02T20:30:32.168Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 1.3 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

PASSshould apply the setting"Remember my usual breakfast: oats, whey, blueberries." (difficulty —)0.5s

Verdict Expected SETTINGS — should apply the setting. PASS: Applied setting.

Why verdict Applied setting.

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 Saved food note: my usual breakfast: oats, whey, blueberries.

2 · Card shown Saved food note: my usual breakfast: oats, whey, blueberries.

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-08-02T20:30:55.448Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched your saved foods and aliases to "my usual breakfast" at 96% confidence.
Matched the common-food list to "Blueberries" at 90% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 1.5 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

PASSshould apply the setting"Make my default coffee a grande oat milk latte." (difficulty —)0.2s

Verdict Expected SETTINGS — should apply the setting. PASS: Applied setting.

Why verdict Applied setting.

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 Okay, I saved grande oat milk latte as your default coffee.

2 · Card shown Okay, I saved grande oat milk latte as your default coffee.

4 · UI did navigated to "settings" 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-08-02T20:31:06.828Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched your saved foods and aliases to "my default coffee" at 96% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 0.5 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

UNVERIFIEDunclassifiedshould apply the setting"Turn on reminders to log dinner." (difficulty —)0.1s

Verdict Expected SETTINGS — should apply the setting. UNVERIFIED: Informational non-gating row (excluded from pass/fail tallies).

Why verdict Informational non-gating row (excluded from pass/fail tallies).

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 Okay, I turned on reminders to log dinner.

2 · Card shown Okay, I turned on reminders to log dinner.

4 · UI did navigated to "settings" 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-08-02T20:31:18.068Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 2.8 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

PASSshould apply the setting"Set my carb goal to 250 grams." (difficulty —)0.1s

Verdict Expected SETTINGS — should apply the setting. PASS: Applied setting.

Why verdict Applied setting.

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 Okay, I updated your daily carb goal to 250 grams.

2 · Card shown Okay, I updated your daily carb goal to 250 grams.

4 · UI did navigated to "settings" 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-08-02T20:31:29.284Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 2.9 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

UNVERIFIEDunclassifiedshould apply the setting"Save my meal prep as chicken rice broccoli." (difficulty —)0.1s

Verdict Expected SETTINGS — should apply the setting. UNVERIFIED: Informational non-gating row (excluded from pass/fail tallies).

Why verdict Informational non-gating row (excluded from pass/fail tallies).

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 Okay, I saved your meal prep as chicken rice broccoli.

2 · Card shown Okay, I saved your meal prep as chicken rice broccoli.

4 · UI did navigated to "settings" 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-08-02T20:31:36.830Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched the common-food list to "Cooked white rice" at 90% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 4.1 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

UNVERIFIEDunclassifiedshould apply the setting"Use cooked weights unless I say dry." (difficulty —)0.1s

Verdict Expected SETTINGS — should apply the setting. UNVERIFIED: Informational non-gating row (excluded from pass/fail tallies).

Why verdict Informational non-gating row (excluded from pass/fail tallies).

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 Okay, I will treat food weights as cooked unless you say otherwise.

2 · Card shown Okay, I will treat food weights as cooked unless you say otherwise.

4 · UI did navigated to "settings" 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-08-02T20:31:48.062Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 3.6 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

UNVERIFIEDunclassifiedshould apply the setting"Stop reminding me to log snacks." (difficulty —)0.1s

Verdict Expected SETTINGS — should apply the setting. UNVERIFIED: Informational non-gating row (excluded from pass/fail tallies).

Why verdict Informational non-gating row (excluded from pass/fail tallies).

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 Okay, I turned off reminders to log snacks.

2 · Card shown Okay, I turned off reminders to log snacks.

4 · UI did navigated to "settings" 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-08-02T20:32:02.994Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 2.7 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

PASSshould decline"Never mind, don’t log that." (difficulty —)0.1s

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

1 · TTS said Okay — no food was logged for replay setup replay setup cereal..

2 · Card shown Okay — no food was logged for replay setup replay setup cereal..

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T20:32:28.406Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 3.1 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

PASSshould decline"Cancel that food entry." (difficulty —)0.1s

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

1 · TTS said Okay — no food was logged for replay setup replay setup pasta..

2 · Card shown Okay — no food was logged for replay setup replay setup pasta..

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T20:32:57.476Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 3.1 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

PASSshould decline"No, skip the smoothie." (difficulty —)0.1s

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

1 · TTS said Okay — no food was logged for replay setup replay setup smoothie..

2 · Card shown Okay — no food was logged for replay setup replay setup smoothie..

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T20:33:22.819Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 2.4 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

PASSshould decline"Actually forget dinner." (difficulty —)0.1s

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

1 · TTS said Should I add that as a to-do?

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: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T20:33:48.646Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 2.8 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

PASSshould decline"Don’t add the coffee." (difficulty —)0.1s

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

1 · TTS said Okay — no food was logged for replay setup replay setup coffee..

2 · Card shown Okay — no food was logged for replay setup replay setup coffee..

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T20:34:10.939Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched your saved foods and aliases to "coffee" at 90% confidence.
Matched the common-food list to "Coffee" at 90% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 2.2 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

PASSshould decline"Stop, that was for tomorrow, not today." (difficulty —)0.1s

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

1 · TTS said 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.

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-08-02T20:34:38.053Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 3.4 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

PASSshould decline"No food log needed." (difficulty —)0.1s

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

1 · TTS said Okay — no food was logged for replay setup replay setup salad..

2 · Card shown Okay — no food was logged for replay setup replay setup salad..

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T20:35:03.278Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 2.5 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

PASSshould decline"Ignore that last nutrition thing." (difficulty —)4.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 4.0s

1 · TTS said Understood — focusing on what’s next. What would you like to log, check, or plan?

2 · Card shown Understood — focusing on what’s next. What would you like to log, check, or plan?

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T20:35:29.500Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 3.5 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

PASSshould handle appropriately"What is the weather tomorrow?" (difficulty —)2.6s

Verdict Expected OTHER — should handle appropriately. PASS: OTHER weather — no write, general route, and weather response shape passed.

Why verdict OTHER weather — no write, general route, and weather response shape passed.

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 I don’t have weather info here — this app is for logging health and productivity. For weather, try asking your phone’s assistant or checking a weather app. What would you like to log or plan next?

2 · Card shown I don’t have weather info here — this app is for logging health and productivity. For weather, try asking your phone’s assistant or checking a weather app. What would you like to log or plan next?

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T20:35:43.259Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 2.8 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

PASSshould handle appropriately"Text Sarah that I am running late." (difficulty —)0.1s

Verdict Expected OTHER — should handle appropriately. PASS: OTHER text — declined out-of-domain messaging.

Why verdict OTHER text — declined out-of-domain messaging.

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 I can't send texts or messages. You can still log food, workouts, notes, and to-dos here.

2 · Card shown I can't send texts or messages. You can still log food, workouts, notes, and to-dos here.

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T20:35:54.550Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 3.5 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

UNVERIFIEDunclassifiedshould handle appropriately"Start a timer for ten minutes." (difficulty —)0.1s

Verdict Expected OTHER — should handle appropriately. UNVERIFIED: OTHER timer — response not mechanically confirmable as a timer action

Why verdict OTHER timer — response not mechanically confirmable as a timer 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 0.1s

1 · TTS said Work time logging isn't available. I can help with food, strength workouts, notes, and to-dos.

2 · Card shown Work time logging isn't available. I can help with food, strength workouts, notes, and to-dos.

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T20:36:05.634Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 2.9 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

UNVERIFIEDunclassifiedshould handle appropriately"How many miles is a 10K?" (difficulty —)0.1s

Verdict Expected OTHER — should handle appropriately. UNVERIFIED: OTHER distance — response has no parseable miles figure

Why verdict OTHER distance — response has no parseable miles figure

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 I understood the nutrition question, but I could not find a solid number for that food yet. Nothing was logged.

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-08-02T20:36:16.871Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 2.7 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

PASSshould handle appropriately"Play my workout playlist." (difficulty —)0.1s

Verdict Expected OTHER — should handle appropriately. PASS: OTHER music — music action acknowledged.

Why verdict OTHER music — music action acknowledged.

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 I can't play music or playlists. I can help with food, workouts, notes, and to-dos.

2 · Card shown I can't play music or playlists. I can help with food, workouts, notes, and to-dos.

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T20:36:28.045Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 2.9 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

PASSshould handle appropriately"Remind me to call the dentist." (difficulty —)0.3s

Verdict Expected OTHER — should handle appropriately. PASS: OTHER reminder — reminder/todo acknowledged.

Why verdict OTHER reminder — reminder/todo acknowledged.

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 Added to-do: call the dentist. Priority 3. Tell me if the title or due date should be different.

2 · Card shown Added to-do: call the dentist. Priority 3. Tell me if the title or due date should be different.

3 · App data rows written created todo_item: call the dentist

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-08-02T20:36:50.973Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 2.9 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

PASSshould handle appropriately"What time is sunset?" (difficulty —)2.3s

Verdict Expected OTHER — should handle appropriately. PASS: OTHER general_query — no write, general route, and general-information response shape passed.

Why verdict OTHER general_query — no write, general route, and general-information response shape passed.

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

1 · TTS said I don’t have sunset times here — this app is for logging health and productivity. For sunset info, try asking your phone’s assistant or checking a weather app. What would you like to log or plan next?

2 · Card shown I don’t have sunset times here — this app is for logging health and productivity. For sunset info, try asking your phone’s assistant or checking a weather app. What would you like to log or plan next?

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T20:37:04.440Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 2.7 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

PASSshould handle appropriately"Open my calendar." (difficulty —)0.1s

Verdict Expected OTHER — should handle appropriately. PASS: OTHER navigation — navigated.

Why verdict OTHER navigation — 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 Opening To-dos Calendar.

2 · Card shown Opening To-dos Calendar.

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-08-02T20:37:15.687Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 2.5 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

UNVERIFIEDunclassifiedshould handle appropriately"Tell me a joke." (difficulty —)1.8s

Verdict Expected OTHER — should handle appropriately. UNVERIFIED: OTHER conversation — conversational quality not mechanically gradeable

Why verdict OTHER conversation — conversational quality not mechanically gradeable

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 Why did the dumbbell break up with the treadmill? It said, “You’re always running away from commitment.” What would you like to log or plan next?

2 · Card shown Why did the dumbbell break up with the treadmill? It said, “You’re always running away from commitment.” What would you like to log or plan next?

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T20:37:28.752Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 2.4 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

UNVERIFIEDunclassifiedshould handle appropriately"How much should I deadlift today?" (difficulty —)0.1s

Verdict Expected OTHER — should handle appropriately. UNVERIFIED: OTHER workout_not_food — workout recommendation quality not mechanically gradeable

Why verdict OTHER workout_not_food — workout recommendation quality not mechanically gradeable

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 That can be a good addition if it fits your goal and recovery. Add it gradually and keep the first few sets conservative.

2 · Card shown That can be a good addition if it fits your goal and recovery. Add it gradually and keep the first few sets conservative.

4 · UI did navigated to "workouts" 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-08-02T20:37:40.024Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched the exercise list to "Deadlift" at 88% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 3.4 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

PASSshould navigate"Open my food log." (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 Opening Food History.

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-08-02T20:37:51.235Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 2.4 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

PASSshould navigate"Show today’s nutrition summary." (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 Opening Food Today.

2 · Card shown Opening Food Today.

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-08-02T20:38:02.531Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 3.3 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

PASSshould navigate"Take me to meal history." (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 Opening Food History.

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-08-02T20:38:13.788Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 2.8 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

PASSshould navigate"Open food settings." (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 Opening Food Prefs.

2 · Card shown Opening Food Prefs.

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-08-02T20:38:25.109Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 2.8 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

UNVERIFIEDunclassifiedshould navigate"Show my macro dashboard." (difficulty —)0.1s

Verdict Expected NAVIGATE — should navigate. UNVERIFIED: Informational non-gating row (excluded from pass/fail tallies).

Why verdict Informational non-gating row (excluded from pass/fail tallies).

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 Opening Home.

2 · Card shown Opening Home.

4 · UI did navigated to "main" 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-08-02T20:38:36.356Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 2.9 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

PASSshould navigate"Go to saved meals." (difficulty —)0.2s

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

1 · TTS said Opening Food Library.

2 · Card shown Opening Food Library.

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-08-02T20:38:47.659Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched your past food logs to "Home default Post-Spin Recovery Meal" at 82% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 0.3 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

UNVERIFIEDunclassifiedshould navigate"Open barcode scan for food." (difficulty —)0.1s

Verdict Expected NAVIGATE — should navigate. UNVERIFIED: Informational non-gating row (excluded from pass/fail tallies).

Why verdict Informational non-gating row (excluded from pass/fail tallies).

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 Opening Food.

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-08-02T20:38:59.045Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 3.2 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

UNVERIFIEDunclassifiedshould navigate"Show weekly food trends." (difficulty —)0.1s

Verdict Expected NAVIGATE — should navigate. UNVERIFIED: Informational non-gating row (excluded from pass/fail tallies).

Why verdict Informational non-gating row (excluded from pass/fail tallies).

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 Opening Food.

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-08-02T20:39:10.318Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 3.2 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

PASSshould navigate"Pull up yesterday’s meals." (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 Opening Food History.

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-08-02T20:39:21.553Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 2.9 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

UNVERIFIEDunclassifiedshould navigate"Open my grocery list." (difficulty —)0.1s

Verdict Expected NAVIGATE — should navigate. UNVERIFIED: Informational non-gating row (excluded from pass/fail tallies).

Why verdict Informational non-gating row (excluded from pass/fail tallies).

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 You do not have any general lists yet.

2 · Card shown You do not have any general lists yet.

4 · UI did navigated to "lists" 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-08-02T20:39:32.847Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 2.8 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

UNVERIFIEDunclassifiedshould log the entry"Note that the soup tasted too salty." (difficulty —)1.2s

Verdict Expected LOG — should log the entry. UNVERIFIED: UNVERIFIABLE — FOOD_NOTE row with no local capture this turn.

Why verdict UNVERIFIABLE — FOOD_NOTE row with no local capture this turn.

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 Saved food note: the soup tasted too salty.

2 · Card shown Saved food note: the soup tasted too salty.

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-08-02T20:39:41.390Z

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 log the entry"Remember this brand of yogurt upset my stomach." (difficulty —)0.5s

Verdict Expected LOG — should log the entry. UNVERIFIED: UNVERIFIABLE — FOOD_NOTE row with no local capture this turn.

Why verdict UNVERIFIABLE — FOOD_NOTE row with no local capture this turn.

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 Saved food note: this brand of yogurt upset my stomach.

2 · Card shown Saved food note: this brand of yogurt upset my stomach.

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-08-02T20:39:53.144Z

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 log the entry"Add a note: the chicken recipe needs more lemon." (difficulty —)0.4s

Verdict Expected LOG — should log the entry. UNVERIFIED: UNVERIFIABLE — FOOD_NOTE row with no local capture this turn.

Why verdict UNVERIFIABLE — FOOD_NOTE row with no local capture this turn.

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 Saved food note: the chicken recipe needs more lemon.

2 · Card shown Saved food note: the chicken recipe needs more lemon.

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-08-02T20:40:04.680Z

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 log the entry"Remember I liked the lower sugar granola." (difficulty —)0.4s

Verdict Expected LOG — should log the entry. UNVERIFIED: UNVERIFIABLE — FOOD_NOTE row with no local capture this turn.

Why verdict UNVERIFIABLE — FOOD_NOTE row with no local capture this turn.

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 Saved food note: I liked the lower sugar granola.

2 · Card shown Saved food note: I liked the lower sugar granola.

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-08-02T20:40:16.241Z

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 log the entry"Note that dinner was at the airport." (difficulty —)1.2s

Verdict Expected LOG — should log the entry. UNVERIFIED: UNVERIFIABLE — FOOD_NOTE row with no local capture this turn.

Why verdict UNVERIFIABLE — FOOD_NOTE row with no local capture this turn.

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 Saved food note: dinner was at the airport.

2 · Card shown Saved food note: dinner was at the airport.

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-08-02T20:40:28.610Z

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 log the entry"Add note to lunch: ate while driving." (difficulty —)1.0s

Verdict Expected LOG — should log the entry. UNVERIFIED: UNVERIFIABLE — FOOD_NOTE row with no local capture this turn.

Why verdict UNVERIFIABLE — FOOD_NOTE row with no local capture this turn.

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 Saved food note: lunch: ate while driving.

2 · Card shown Saved food note: lunch: ate while driving.

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-08-02T20:40:52.305Z

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 log the entry"Remember the protein powder was too sweet." (difficulty —)0.4s

Verdict Expected LOG — should log the entry. UNVERIFIED: UNVERIFIABLE — FOOD_NOTE row with no local capture this turn.

Why verdict UNVERIFIABLE — FOOD_NOTE row with no local capture this turn.

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 Saved food note: the protein powder was too sweet.

2 · Card shown Saved food note: the protein powder was too sweet.

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-08-02T20:41:03.946Z

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 log the entry"Note: meal prep portion felt small." (difficulty —)1.2s

Verdict Expected LOG — should log the entry. UNVERIFIED: UNVERIFIABLE — FOOD_NOTE row with no local capture this turn.

Why verdict UNVERIFIABLE — FOOD_NOTE row with no local capture this turn.

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 Saved food note: meal prep portion felt small.

2 · Card shown Saved food note: meal prep portion felt small.

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-08-02T20:41:16.334Z

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 log the entry"Save a food note that spicy ramen triggered reflux." (difficulty —)0.9s

Verdict Expected LOG — should log the entry. UNVERIFIED: UNVERIFIABLE — FOOD_NOTE row with no local capture this turn.

Why verdict UNVERIFIABLE — FOOD_NOTE row with no local capture this turn.

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 Saved food note: spicy ramen triggered reflux.

2 · Card shown Saved food note: spicy ramen triggered reflux.

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-08-02T20:41:28.473Z

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 log the entry"Remember to buy that salsa again." (difficulty —)0.4s

Verdict Expected LOG — should log the entry. UNVERIFIED: UNVERIFIABLE — FOOD_NOTE row with no local capture this turn.

Why verdict UNVERIFIABLE — FOOD_NOTE row with no local capture this turn.

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 Saved food note: buy that salsa again.

2 · Card shown Saved food note: buy that salsa again.

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-08-02T20:41:40.050Z

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 entry"Log 3 ounces canned tuna in water with 1 tablespoon light mayo." (difficulty —)1.1s

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

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

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

Pick every reason you think applies. Multiple boxes are allowed because one utterance can be wrong in more than one way. Use the note below for "Other" or extra detail.

Timing 1.1s

1 · TTS said I need to resolve Light mayonnaise before I log this meal. What should I use for Light mayonnaise?

2 · Card shown I need to resolve Light mayonnaise before I log this meal. What should I use for Light mayonnaise?

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T20:41:57.111Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched the common-food list to "Canned tuna in water" at 90% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 4.4 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

FAILshould log the entry"Record a 16 ounce homemade green juice: kale, apple, cucumber, ginger." (difficulty —)2.1s

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

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

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

Pick every reason you think applies. Multiple boxes are allowed because one utterance can be wrong in more than one way. Use the note below for "Other" or extra detail.

Timing 2.1s

1 · TTS said Which kale should I use?

2 · Card shown Which kale 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-08-02T20:42:09.512Z

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

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

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

PASSshould log the entry"Add 2 tablespoons powdered creamer to my coffee." (difficulty —)2.4s

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

Why verdict Logged (write-truth verified): Powdered coffee creamer — 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 2.4s

1 · TTS said Logged 2 tablespoons powdered creamer.

2 · Card shown Logged 2 tablespoons powdered creamer.

3 · App data rows written created food_log_entry: Powdered coffee creamer ×1 (2 tbsp) 62 cal · 0.3g P · 7g C · 3.9g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T20:42:22.961Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched the common-food list to "Powdered coffee creamer" at 90% confidence.
Matched your saved foods and aliases to "coffee" at 90% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 2.8 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

PASSshould log the entry"Track 1 cup cooked barley and 4 ounces roasted chicken thigh." (difficulty —)0.5s

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

Why verdict Logged (write-truth verified): Cooked barley, 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.5s

1 · TTS said Logged 1 cup cooked barley and 4 ounces roasted chicken thigh.

2 · Card shown Logged 1 cup cooked barley and 4 ounces roasted chicken thigh.

3 · App data rows written created food_log_entry: Cooked barley ×1 (1 cup) 193 cal · 3.6g P · 44.3g C · 0.6g F
created food_log_entry: Chicken thigh ×1 (4 oz) 237 cal · 29.5g P · 0g C · 12.4g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T20:42:36.174Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 4.4 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

PASSshould log the entry"Log 30 grams whey isolate mixed in water." (difficulty —)0.3s

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

Why verdict Logged (write-truth verified): Whey isolate — 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 Logged Whey isolate.

2 · Card shown Logged Whey isolate.

3 · App data rows written created food_log_entry: Whey isolate ×1 (30 g) 108 cal · 25.8g P · 0.9g C · 0.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-08-02T20:42:47.139Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched the common-food list to "Whey isolate" at 90% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 3.8 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

PASSshould log the entry"Record half a medium cantaloupe." (difficulty —)0.4s

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

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

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

3 · App data rows written created food_log_entry: Cantaloupe ×1 (half a medium cantaloupe) 94 cal · 2.2g P · 22.6g 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-08-02T20:42:57.889Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched the common-food list to "Cantaloupe" at 90% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 2.9 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

PASSshould log the entry"Add 5 ounces cooked ground turkey, 93 percent lean." (difficulty —)0.5s

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

Why verdict Logged (write-truth verified): Lean ground turkey — 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 Logged 5 ounces cooked ground turkey 93 percent lean.

2 · Card shown Logged 5 ounces cooked ground turkey 93 percent lean.

3 · App data rows written created food_log_entry: Lean ground turkey ×1 (5 oz) 241 cal · 38.3g P · 0g C · 9.9g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T20:43:10.903Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched the common-food list to "Lean ground turkey" at 90% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 4.2 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

PASSshould log the entry"Track 2 cups vegetable stir fry cooked with 2 teaspoons sesame oil." (difficulty —)0.8s

Verdict Expected LOG — should log the entry. PASS: Logged (write-truth verified): Sesame oil, Vegetable stir fry — card not captured.

Why verdict Logged (write-truth verified): Sesame oil, Vegetable stir fry — 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.8s

1 · TTS said Logged 2 cups vegetable stir fry cooked and 2 teaspoons sesame oil.

2 · Card shown Logged 2 cups vegetable stir fry cooked and 2 teaspoons sesame oil.

3 · App data rows written created food_log_entry: Vegetable stir fry ×1 (2 cup) 225 cal · 7.5g P · 30g C · 9g F
created food_log_entry: Sesame oil ×1 (2 tsp) 80 cal · 0g P · 0g C · 9.1g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T20:43:23.555Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched the common-food list to "Vegetable stir fry" at 90% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 4.8 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

FAILshould log the entry"Log one bakery blueberry muffin, large." (difficulty —)2.3s

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

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

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

Pick every reason you think applies. Multiple boxes are allowed because one utterance can be wrong in more than one way. Use the note below for "Other" or extra detail.

Timing 2.3s

1 · TTS said I need to resolve large before I log this meal. What should I use for large?

2 · Card shown I need to resolve large before I log this meal. What should I use for large?

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T20:43:35.159Z

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 entry"Record 1 cup chicken salad made with mayo." (difficulty —)5.7s

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

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

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

Pick every reason you think applies. Multiple boxes are allowed because one utterance can be wrong in more than one way. Use the note below for "Other" or extra detail.

Timing 5.7s

1 · TTS said What exact food and amount should I use for 1 cup chicken salad made with mayo? I did not log it yet because I could not safely finish that food log.

2 · Card shown What exact food and amount should I use for 1 cup chicken salad made with mayo? 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-08-02T20:43:52.038Z

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

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

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

PASSshould log the entry"Add 90 grams smoked tofu." (difficulty —)0.3s

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

Why verdict Logged (write-truth verified): Smoked tofu — 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 Logged 90 grams smoked tofu.

2 · Card shown Logged 90 grams smoked tofu.

3 · App data rows written created food_log_entry: Smoked tofu ×1 (90 g) 158 cal · 17.1g P · 1.8g C · 9.9g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T20:44:03.524Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched the common-food list to "Smoked tofu" at 90% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 3.1 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

PASSshould log the entry"Track 1 ounce nutritional yeast on popcorn." (difficulty —)0.5s

Verdict Expected LOG — should log the entry. PASS: Logged (write-truth verified): Nutritional yeast, Air-popped popcorn — card not captured.

Why verdict Logged (write-truth verified): Nutritional yeast, Air-popped popcorn — 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 Logged 1 ounce nutritional yeast and Air-popped popcorn. Assumed catalog default servings where you did not say an amount — tell me if that is not right.

2 · Card shown Logged 1 ounce nutritional yeast and Air-popped popcorn. 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: Nutritional yeast ×1 (1 oz) 92 cal · 14.2g P · 10.2g C · 1.4g F
created food_log_entry: Air-popped popcorn ×1 (100 g) 387 cal · 12.9g P · 78g C · 4.5g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T20:44:15.878Z

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

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

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

PASSshould log the entry"Log 12 ounces coconut water." (difficulty —)0.3s

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

Why verdict Logged (write-truth verified): Coconut water — 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 Logged 12 ounces coconut water.

2 · Card shown Logged 12 ounces coconut water.

3 · App data rows written created food_log_entry: Coconut water ×1 (12 oz) 65 cal · 2.4g P · 12.6g 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-08-02T20:44:26.735Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched the common-food list to "Coconut water" at 90% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 3.1 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

FAILshould log the entry"Record 3 dates stuffed with almond butter." (difficulty —)0.6s

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

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

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

Pick every reason you think applies. Multiple boxes are allowed because one utterance can be wrong in more than one way. Use the note below for "Other" or extra detail.

Timing 0.6s

1 · TTS said How much should I log for Almond butter? I did not log them yet because the amounts were not clear.

2 · Card shown How much should I log for Almond butter? I did not log them yet because the amounts were 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-08-02T20:44:38.683Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched the common-food list to "Dates" at 90% confidence.
Matched your past food logs to "Almond butter" at 82% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 3.4 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

PASSshould log the entry"Add one cup matzo ball soup." (difficulty —)0.3s

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

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

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

3 · App data rows written created food_log_entry: Matzo ball soup ×1 (1 cup) 140 cal · 8.1g P · 15.2g C · 5.4g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T20:44:50.088Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched the common-food list to "Matzo ball soup" at 90% confidence.

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 3.3 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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