food-corpus-mixed-C-324f4ab3-c63-20260802

Supposed to	N	Correct	Wrong	Unverified
▸ LOG — log the entry	81	61 (75%)	20 (25%)	0 (0%)
20 handled wrong — click one to jump to its full detail below "I had one cup cooked oatmeal with no toppings." OVER-ASK — asked instead of logging (no saved row). "Log two Eggo waffles." OVER-ASK — asked instead of logging (no saved row). "Log one medium sweet potato." OVER-ASK — asked instead of logging (no saved row). "Dinner was five ounces tilapia." WRITE-TRUTH FAIL — MACROS off for "tilapia": logged 183 kcal vs expected ~128 (§14 15pct/25cal band) "Track one tablespoon hummus." OVER-ASK — asked instead of logging (no saved row). "Same protein bar as yesterday." WRITE-TRUTH FAIL — WRONG/MISSING item "Chocolate Peanut Protein Bar" — no saved row with matching identity (rows: Quest Chocolate Brownie Protein Bar) "Log the same salad I had last night." OVER-ASK — asked instead of logging (no saved row). "Log the chicken I had last time." WRITE-TRUTH FAIL — WRONG/MISSING item "Grilled Chicken Breast" — no saved row with matching identity (rows: beer) "Snack was one blueberry RX bar." WRITE-TRUTH FAIL — WRONG item/product identity "blueberry rxbar" — saved row does not hit product alias (rows: beer) "Finished one Fairlife Core Power chocolate 42 gram bottle." OVER-ASK — asked instead of logging (no saved row). "Track one Chobani zero sugar vanilla cup." WRITE-TRUTH FAIL — MACROS off for "chobani zero sugar vanilla": logged 120 kcal vs expected ~60 (§14 15pct/25cal band) "Save one Quest chocolate brownie protein bar." WRITE-TRUTH FAIL — WRONG item/product identity "quest chocolate brownie bar" — saved row does not hit product alias (rows: cookie) "I ate one KIND dark chocolate nuts and sea salt bar." WRITE-TRUTH FAIL — WRONG item/product identity "kind dark chocolate nuts sea salt" — saved row does not hit product alias (rows: Dark chocolate, No Cow Chocolate Sea Salt Bar) "Log a medium Fuji apple and one KIND peanut butter dark chocolate bar." WRITE-TRUTH FAIL — WRONG/MISSING item "one kind peanut butter dark chocolat" — no saved row with matching identity (rows: Chocolate Candy, Peanut Butter Filled, Apple, Chocolate Candy, Peanut Butter Filled) "Breakfast was an omelet with cheddar and olive oil." OVER-ASK — asked instead of logging (no saved row). "Dinner was a burrito bowl with rice, beans, steak, and queso." OVER-ASK — asked instead of logging (no saved row). "I had ramen with pork and egg." OVER-ASK — asked instead of logging (no saved row). "Log a turkey sandwich with mayo and cheddar." OVER-ASK — asked instead of logging (no saved row). "Dinner was pad thai with chicken, peanuts, and bean sprouts." OVER-ASK — asked instead of logging (no saved row). "I had a bowl of plain cooked oatmeal." WRITE-TRUTH FAIL — WRONG/MISSING item "estimated three-quarters to one cup" — no saved row with matching identity (rows: Cooked oatmeal, Cooked oatmeal)
▸ CLARIFY — ask a clarifying question	53	46 (87%)	7 (13%)	0 (0%)
7 handled wrong — click one to jump to its full detail below "Track chicken breast and brown rice." Logged a BLIND guess — no stated assumption, no correction invited. "Log a protein shake with banana, peanut butter, and oats." Logged a BLIND guess — no stated assumption, no correction invited. "I built a yogurt bowl with granola, honey, and blueberries." Logged a BLIND guess — no stated assumption, no correction invited. "I had a protein bar." WRONG item vs seeded default/key — no saved food row to verify good-guess write against seed/key "Log a yogurt." Logged a BLIND guess — no stated assumption, no correction invited. "Track a burger." Logged a BLIND guess — no stated assumption, no correction invited. "Add a muffin." Logged a BLIND guess — no stated assumption, no correction invited.
▸ QUERY — answer the query	18	0 (0%)	1 (6%)	17 (94%)
1 handled wrong — click one to jump to its full detail below "What did I eat after my workout?" Query not answered — asked back instead of answering.
▸ DELETE — delete the entry	14	4 (29%)	10 (71%)	0 (0%)
10 handled wrong — click one to jump to its full detail below "Delete the banana from earlier." Did not delete (not understood / no removal). "Remove that Quest bar." Did not delete (not understood / no removal). "Delete the oatmeal entry." Did not delete (not understood / no removal). "Take off the eggs." Did not delete (not understood / no removal). "Remove the blueberries." Did not delete (not understood / no removal). "Delete the chicken log." Did not delete (not understood / no removal). "Scratch the peanut butter." Did not delete (not understood / no removal). "Remove the milk entry." Did not delete (not understood / no removal). "Take out the beer from last night." Did not delete (not understood / no removal). "Remove the cookie log from earlier this week." Did not delete (not understood / no removal).
▸ UPDATE — update the entry	14	6 (43%)	8 (57%)	0 (0%)
8 handled wrong — click one to jump to its full detail below "Change the sequence banana quantity to two." Reported could-not-confirm (write-confirmation false negative). "Update the oatmeal to one and a half cups." Reported could-not-confirm (write-confirmation false negative). "Change the eggs to three." Reported could-not-confirm (write-confirmation false negative). "Make the blueberries a half cup." Reported could-not-confirm (write-confirmation false negative). "Change peanut butter to two tablespoons." Reported could-not-confirm (write-confirmation false negative). "Change the portion to two cups." Reported could-not-confirm (write-confirmation false negative). "Make it half a cup instead." Reported could-not-confirm (write-confirmation false negative). "Update that to six ounces." Reported could-not-confirm (write-confirmation false negative).
▸ CLARIFY_ANSWER — complete the pending action	13	1 (8%)	1 (8%)	11 (85%)
1 handled wrong — click one to jump to its full detail below "The Quest chocolate brownie." Reported could-not-confirm (write-confirmation false negative).
▸ NAVIGATE — navigate	2	2 (100%)	0 (0%)	0 (0%)
No errors — all handled correctly.
▸ DECLINE — decline	1	1 (100%)	0 (0%)	0 (0%)
No errors — all handled correctly.
▸ SETTINGS — apply the setting	1	0 (0%)	1 (100%)	0 (0%)
1 handled wrong — click one to jump to its full detail below "Set my calorie goal to twenty two hundred." Reported could-not-confirm (write-confirmation false negative).
Total	197	121 (72%)	48	28

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

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

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

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.2s

1 · TTS said Logged one medium banana for the sequence. Assumed 1 medium banana as the default serving. Tell me if you want a different amount.

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

3 · App data rows written created food_log_entry: Banana ×1 (1 medium banana) 105 cal · 1.3g P · 27.1g C · 0.4g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

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

snapshot captured 2026-08-02T21:20:43.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 "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 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 one Quest chocolate chip cookie dough bar." (difficulty —)0.6s

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

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

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.6s

1 · TTS said Logged Quest chocolate chip cookie dough bar with an estimated macro range.

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

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

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

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

snapshot captured 2026-08-02T21:20:55.031Z

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 cup cooked oatmeal with no toppings." (difficulty —)5.6s

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

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

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 5.6s

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

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

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

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

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

snapshot captured 2026-08-02T21:21:11.721Z

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

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

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

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

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

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

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.4s

1 · TTS said Logged two hard boiled eggs for lunch.

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

3 · App data rows written created food_log_entry: Egg ×1 (2 eggs) 143 cal · 12.6g P · 0.7g C · 9.5g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

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

snapshot captured 2026-08-02T21:21:23.291Z

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

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

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

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.3s

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

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

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

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

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

snapshot captured 2026-08-02T21:21:34.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 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.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 four ounces grilled chicken." (difficulty —)0.2s

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

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

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.2s

1 · TTS said Logged four ounces grilled chicken.

2 · Card shown Logged four ounces grilled chicken.

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

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

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

snapshot captured 2026-08-02T21:21:46.082Z

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 "Grilled 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 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 one tablespoon peanut butter." (difficulty —)0.2s

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

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

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.2s

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

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

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

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

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

snapshot captured 2026-08-02T21:21:57.662Z

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 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"I drank one cup two percent milk." (difficulty —)0.3s

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

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

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.3s

1 · TTS said Logged one cup two percent milk.

2 · Card shown Logged one cup two percent milk.

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

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

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

snapshot captured 2026-08-02T21:22:08.770Z

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 "2% milk" at 90% confidence.
Matched your past food logs to "2 Percent Milk" 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)

PASSshould log the entry"I had one medium banana." (difficulty —)0.2s

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

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

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.2s

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

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

3 · App data rows written created food_log_entry: Banana ×1 (1 medium banana) 105 cal · 1.3g P · 27.1g C · 0.4g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

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

snapshot captured 2026-08-02T21:22:20.085Z

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 "Banana" at 83% 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"Breakfast was two hard boiled eggs." (difficulty —)0.2s

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

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

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.2s

1 · TTS said Logged two hard boiled eggs.

2 · Card shown Logged two hard boiled eggs.

3 · App data rows written created food_log_entry: Egg ×1 (2 eggs) 143 cal · 12.6g P · 0.7g C · 9.5g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

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

snapshot captured 2026-08-02T21:22:31.382Z

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.
Matched your saved foods and aliases to "two hard boiled eggs for lunch" at 63% 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"Put down four ounces grilled chicken breast." (difficulty —)0.2s

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

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

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.2s

1 · TTS said Logged four ounces grilled chicken breast.

2 · Card shown Logged four ounces grilled chicken breast.

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

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

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

snapshot captured 2026-08-02T21:22:42.693Z

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 "four ounces grilled chicken" at 90% confidence.
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 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"Record one cup cooked white rice." (difficulty —)0.2s

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

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

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.2s

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

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

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

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

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

snapshot captured 2026-08-02T21:22:53.977Z

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 Jasmine 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 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"Snack was a small apple." (difficulty —)0.2s

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

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

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

3 · App data rows written created food_log_entry: Apple ×1 (1 small apple) 77 cal · 0.4g P · 20.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-02T21:23:05.340Z

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 "Apple" 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 ate five ounces baked salmon." (difficulty —)0.1s

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

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

1 · TTS said Logged five ounces baked salmon.

2 · Card shown Logged five ounces baked salmon.

3 · App data rows written created food_log_entry: Salmon ×1 (5 oz) 295 cal · 28.3g P · 0g C · 18.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-02T21:23:16.628Z

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.

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"Track one cup blueberries." (difficulty —)0.2s

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

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

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

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

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

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

snapshot captured 2026-08-02T21:23:27.959Z

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.
Matched your past food logs to "Blueberries" 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)

PASSshould log the entry"Count twelve 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 twelve almonds.

2 · Card shown Logged twelve almonds.

3 · App data rows written created food_log_entry: Almonds ×1 (12 almonds) 83 cal · 3.1g P · 3.1g C · 7.2g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

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

snapshot captured 2026-08-02T21:23:39.286Z

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.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"Lunch included three ounces 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 three ounces turkey breast.

2 · Card shown Logged three ounces turkey breast.

3 · App data rows written created food_log_entry: Turkey breast ×1 (3 oz) 115 cal · 24.7g P · 0g C · 1.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-02T21:23:50.620Z

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.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"Save one cup steamed broccoli." (difficulty —)0.2s

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

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

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

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

3 · App data rows written created food_log_entry: Broccoli ×1 (1 cup) 55 cal · 3.8g P · 11.3g 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-02T21:24:01.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 "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.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 drank eight ounces orange juice." (difficulty —)0.2s

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

Why verdict Logged (write-truth verified): Orange juice — 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 eight ounces orange juice.

2 · Card shown Logged eight ounces orange juice.

3 · App data rows written created food_log_entry: Orange juice ×1 (8 oz) 102 cal · 1.6g P · 23.6g 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-02T21:24:13.188Z

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 "Orange juice" 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"Note two slices turkey bacon." (difficulty —)0.3s

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

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

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.3s

1 · TTS said Logged note two slices turkey bacon.

2 · Card shown Logged note two slices turkey bacon.

3 · App data rows written created food_log_entry: Turkey bacon ×1 (2 slices) 60 cal · 8.1g P · 1g 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-02T21:24:24.675Z

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 bacon" 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"Supper was one cup cooked lentils." (difficulty —)0.3s

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

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

2 · Card shown Logged one cup cooked lentils. Assumed 1 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 cup) 230 cal · 17.8g P · 39.8g C · 0.8g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

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

snapshot captured 2026-08-02T21:24:47.808Z

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"Enter one large orange." (difficulty —)0.2s

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

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

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

3 · App data rows written created food_log_entry: Orange ×1 (1 large orange) 86 cal · 1.7g P · 21.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-02T21:24:59.094Z

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 "Orange" 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"Ate a quarter cup raisins." (difficulty —)0.3s

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

1 · TTS said Logged ate a quarter cup raisins. Assumed 0.25 cup as the default serving. Tell me if you want a different amount.

2 · Card shown Logged ate a quarter cup raisins. Assumed 0.25 cup as the default serving. Tell me if you want a different amount.

3 · App data rows written created food_log_entry: Raisins ×1 (0.25 cup) 108 cal · 1.1g P · 28.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-02T21:25:10.527Z

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.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"Track one tablespoon peanut butter." (difficulty —)0.2s

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

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

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.2s

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

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

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

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

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

snapshot captured 2026-08-02T21:25:21.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 your saved foods and aliases to "one tablespoon peanut butter" at 90% confidence.
Matched the common-food list to "Peanut butter" 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"Dinner side was three quarters cup green beans." (difficulty —)0.5s

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

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

1 · TTS said Logged three quarters cup green beans.

2 · Card shown Logged three quarters cup green beans.

3 · App data rows written created food_log_entry: Green beans ×1 (0.75 cup) 33 cal · 1.8g P · 7.4g 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-02T21:25:33.452Z

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 "Green 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 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"I had one and a quarter cups strawberries." (difficulty —)0.5s

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

Why verdict Logged (write-truth verified): Strawberries — 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 one and a quarter cups strawberries. Assumed 1.25 cup as the default serving. Tell me if you want a different amount.

2 · Card shown Logged one and a quarter cups strawberries. Assumed 1.25 cup as the default serving. Tell me if you want a different amount.

3 · App data rows written created food_log_entry: Strawberries ×1 (1.25 cup) 61 cal · 1.3g P · 14.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-02T21:25:45.054Z

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 "Strawberries" 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"Put in two hundred grams nonfat Greek yogurt." (difficulty —)0.2s

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

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

1 · TTS said Logged two hundred grams nonfat greek yogurt.

2 · Card shown Logged two hundred grams nonfat greek yogurt.

3 · App data rows written created food_log_entry: Nonfat Greek yogurt ×1 (200 g) 118 cal · 20.6g P · 7.2g C · 0.8g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

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

snapshot captured 2026-08-02T21:25:56.379Z

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.

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 cup two percent milk." (difficulty —)0.3s

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

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

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.3s

1 · TTS said Logged one cup two percent milk.

2 · Card shown Logged one cup two percent milk.

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

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

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

snapshot captured 2026-08-02T21:26:07.851Z

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 "one cup two percent milk" at 90% confidence.
Matched the common-food list to "2% milk" at 90% confidence.
Matched your saved foods and aliases to "2 Percent Milk" at 62% 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"Breakfast was one cup low fat cottage cheese." (difficulty —)0.2s

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

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

1 · TTS said Logged one cup low fat cottage cheese. Assumed 1 cup as the default serving. Tell me if you want a different amount.

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

3 · App data rows written created food_log_entry: 1% cottage cheese ×1 (1 cup) 163 cal · 28g P · 6.1g 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-02T21:26:19.168Z

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 "1% cottage cheese" at 90% confidence.
Matched your past food logs to "Codex Test Dairy Low Fat 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 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"Count one medium corn tortilla." (difficulty —)0.2s

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

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

1 · TTS said Logged one medium corn tortilla. Assumed 1 medium corn tortilla as the default serving. Tell me if you want a different amount.

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

3 · App data rows written created food_log_entry: Corn tortilla ×1 (1 medium corn tortilla) 61 cal · 1.6g P · 12.5g C · 0.8g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

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

snapshot captured 2026-08-02T21:26:30.477Z

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 "Corn 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 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 six ounces sirloin steak." (difficulty —)0.2s

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

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

1 · TTS said Logged six ounces sirloin steak.

2 · Card shown Logged six ounces sirloin steak.

3 · App data rows written created food_log_entry: Sirloin steak ×1 (6 oz) 364 cal · 49.3g P · 0g 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-02T21:26:41.763Z

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 "Sirloin steak" 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"Add one cup black beans." (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 one cup black beans. Assumed 1 cup as the default serving. Tell me if you want a different amount.

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

3 · App data rows written created food_log_entry: 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-02T21:26:53.100Z

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 "Green 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 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"Track half an avocado." (difficulty —)0.3s

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

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

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

3 · App data rows written created food_log_entry: Avocado ×1 (half an avocado) 120 cal · 1.5g P · 6.4g C · 11g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

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

snapshot captured 2026-08-02T21:27:04.557Z

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.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 two Eggo waffles." (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 Which one did you mean? 1. Kellogg's Homestyle Eggo Waffles, 2. EGGO Homestyle Waffles, Homestyle

2 · Card shown Which one did you mean? 1. Kellogg's Homestyle Eggo Waffles, 2. EGGO Homestyle Waffles, Homestyle

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

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

snapshot captured 2026-08-02T21:27:16.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)

PASSshould log the entry"I ate one English muffin." (difficulty —)0.4s

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

Why verdict Logged (write-truth verified): Muffin, English — 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 Muffin, English with an estimated macro range.

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

3 · App data rows written created food_log_entry: Muffin, English ×1 (1 muffin) 132 cal · 5.2g P · 25.6g C · 1g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

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

snapshot captured 2026-08-02T21:27:27.654Z

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 three ounces shrimp." (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 three ounces shrimp.

2 · Card shown Logged three ounces shrimp.

3 · App data rows written created food_log_entry: Shrimp ×1 (3 oz) 84 cal · 20.4g P · 0.2g 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-02T21:27:38.956Z

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 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"Snack was one string cheese." (difficulty —)0.2s

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

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

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

3 · App data rows written created food_log_entry: Mozzarella string cheese ×1 (1 string cheese) 80 cal · 7g P · 1g 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-02T21:27:50.277Z

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 "Mozzarella string 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"Add one tablespoon olive oil." (difficulty —)0.2s

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

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

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

3 · App data rows written created food_log_entry: Olive oil ×1 (1 tbsp) 120 cal · 0g P · 0g C · 13.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-02T21:28:01.599Z

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.

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

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

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

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.2s

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

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

3 · App data rows written created food_log_entry: Cooked brown rice ×1 (1 cup) 218 cal · 4.5g P · 45.8g C · 1.6g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

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

snapshot captured 2026-08-02T21:28:12.874Z

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 brown 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.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 medium sweet potato." (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 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-02T21:28:24.816Z

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 eight ounces black coffee." (difficulty —)0.2s

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

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

1 · TTS said Logged eight ounces black coffee.

2 · Card shown Logged eight ounces black coffee.

3 · App data rows written created food_log_entry: Coffee ×1 (8 oz) 2 cal · 0.2g P · 0g C · 0g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

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

snapshot captured 2026-08-02T21:28:47.657Z

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.

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"Count ten baby carrots." (difficulty —)0.2s

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

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

1 · TTS said Logged ten baby carrots.

2 · Card shown Logged ten baby carrots.

3 · App data rows written created food_log_entry: Baby carrots ×1 (10 baby carrots) 35 cal · 0.6g P · 8.2g 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-02T21:28:58.944Z

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 "Baby carrots" 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.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"Dinner was five ounces tilapia." (difficulty —)0.2s

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

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

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.2s

1 · TTS said Logged five ounces tilapia.

2 · Card shown Logged five ounces tilapia.

3 · App data rows written created food_log_entry: Tilapia ×1 (5 oz) 183 cal · 36.9g P · 0g C · 3.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-02T21:29:10.254Z

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 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"I had one cup tomato soup." (difficulty —)0.2s

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

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

2 · Card shown Logged one cup tomato 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: Tomato soup ×1 (1 cup) 93 cal · 2g P · 18.9g C · 1g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

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

snapshot captured 2026-08-02T21:29:21.577Z

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 "Tomato 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 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"Add two rice cakes." (difficulty —)0.2s

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

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

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.2s

1 · TTS said Logged two rice cakes.

2 · Card shown Logged two rice cakes.

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

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

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

snapshot captured 2026-08-02T21:29:32.865Z

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

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

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

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

3 · App data rows written created food_log_entry: Grapes ×1 (1 cup) 104 cal · 1.1g P · 27.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-02T21:29:44.188Z

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 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)

FAILshould log the entry"Track one tablespoon hummus." (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 one tablespoon of Hummus 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 one tablespoon of Hummus 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-02T21:29:55.481Z

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 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"I ate one small pear." (difficulty —)0.2s

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

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

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.2s

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

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

3 · App data rows written created food_log_entry: Pear ×1 (1 pear) 101 cal · 0.7g P · 27.1g C · 0.2g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

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

snapshot captured 2026-08-02T21:30:06.808Z

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 "Pear" 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.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"Put down 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-02T21:30:18.129Z

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 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 four ounces 93 percent lean ground turkey." (difficulty —)0.3s

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

1 · TTS said Logged four ounces 93 percent lean ground turkey.

2 · Card shown Logged four ounces 93 percent lean ground turkey.

3 · App data rows written created food_log_entry: Lean ground turkey ×1 (4 oz) 193 cal · 30.6g P · 0g C · 7.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-02T21:30:29.598Z

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 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 my usual Quest bar." (difficulty —)0.1s

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

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

1 · TTS said Logged Quest Quest Chocolate Brownie Protein Bar. Using your saved "my usual quest bar". Tell me if that is wrong.

2 · Card shown Logged Quest Quest Chocolate Brownie Protein Bar. Using your saved "my usual quest bar". Tell me if that is wrong.

3 · App data rows written created food_log_entry: Quest Chocolate Brownie Protein Bar ×1 (bar) 190 cal · 20g P · 21g C · 7g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seed food: Quest Quest Chocolate Brownie Protein Bar

{
  "type": "food_item",
  "foodItem": {
    "id": "seed-c-quest-brownie",
    "name": "Quest Chocolate Brownie Protein Bar",
    "brand": "Quest",
    "source": "manual",
    "servingLabel": "bar",
    "servingQuantity": 1,
    "servingUnit": "bar",
    "macrosPerServing": {
      "calories": 190,
      "proteinGrams": 20,
      "fatGrams": 7,
      "carbsGrams": 21
    },
    "aliases": [],
    "timesLogged": 0,
    "createdAt": "2026-07-16T12:00:00.000Z"
  }
}

food_default

{
  "type": "food_default",
  "phrase": "my usual Quest bar",
  "foodItemId": "seed-c-quest-brownie",
  "settings": {
    "quickLogMode": "fixed",
    "defaultQuantity": 1,
    "defaultServingLabel": "bar",
    "displayLabel": "my usual Quest bar",
    "confirmBeforeLog": false
  }
}

snapshot captured 2026-08-02T21:30:40.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 usual quest bar" 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.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"I had my usual yogurt." (difficulty —)0.1s

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

Why verdict Logged (write-truth verified): Vanilla Greek Yogurt Cup — 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 Codex Test Dairy Vanilla Greek Yogurt Cup. Using your saved "my usual yogurt". Tell me if that is wrong.

2 · Card shown Logged Codex Test Dairy Vanilla Greek Yogurt Cup. Using your saved "my usual yogurt". Tell me if that is wrong.

3 · App data rows written created food_log_entry: Vanilla Greek Yogurt Cup ×1 (cup) 130 cal · 15g P · 12g C · 0g F
created food_log_entry: Vanilla Greek Yogurt Cup ×1 (cup) 130 cal · 15g P · 12g C · 0g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seed food: Codex Test Dairy Vanilla Greek Yogurt Cup

{
  "type": "food_item",
  "foodItem": {
    "id": "seed-c-usual-yogurt",
    "name": "Vanilla Greek Yogurt Cup",
    "brand": "Codex Test Dairy",
    "source": "manual",
    "servingLabel": "cup",
    "servingQuantity": 1,
    "servingUnit": "cup",
    "macrosPerServing": {
      "calories": 130,
      "proteinGrams": 15,
      "fatGrams": 0,
      "carbsGrams": 12
    },
    "aliases": [],
    "timesLogged": 0,
    "createdAt": "2026-07-16T12:00:00.000Z"
  }
}

food_default

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

snapshot captured 2026-08-02T21:30:52.148Z

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 yogurt" at 96% confidence.
Matched the common-food list to "Plain Greek yogurt" at 90% confidence.
Matched your past food logs to "Nonfat 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.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"Lunch was my usual tuna packet." (difficulty —)0.1s

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

Why verdict Logged (write-truth verified): Tuna 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 Codex Test Pantry Tuna Packet. Using your saved "my usual tuna packet". Tell me if that is wrong.

2 · Card shown Logged Codex Test Pantry Tuna Packet. Using your saved "my usual tuna packet". Tell me if that is wrong.

3 · App data rows written created food_log_entry: Tuna Packet ×1 (packet) 100 cal · 22g P · 0g C · 1g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seed food: Codex Test Pantry Tuna Packet

{
  "type": "food_item",
  "foodItem": {
    "id": "seed-c-tuna",
    "name": "Tuna Packet",
    "brand": "Codex Test Pantry",
    "source": "manual",
    "servingLabel": "packet",
    "servingQuantity": 1,
    "servingUnit": "packet",
    "macrosPerServing": {
      "calories": 100,
      "proteinGrams": 22,
      "fatGrams": 1,
      "carbsGrams": 0
    },
    "aliases": [],
    "timesLogged": 0,
    "createdAt": "2026-07-16T12:00:00.000Z"
  }
}

food_default

{
  "type": "food_default",
  "phrase": "my usual tuna packet",
  "foodItemId": "seed-c-tuna",
  "settings": {
    "quickLogMode": "fixed",
    "defaultQuantity": 1,
    "defaultServingLabel": "packet",
    "displayLabel": "my usual tuna packet",
    "confirmBeforeLog": false
  }
}

snapshot captured 2026-08-02T21:31:03.382Z

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 tuna packet" 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.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"Dinner side was my usual rice." (difficulty —)0.1s

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

1 · TTS said Logged Cooked Jasmine Rice. Using your saved "my usual rice". Tell me if that is wrong.

2 · Card shown Logged Cooked Jasmine Rice. Using your saved "my usual rice". Tell me if that is wrong.

3 · App data rows written created food_log_entry: Cooked Jasmine Rice ×1 (cup) 205 cal · 4g P · 45g C · 0g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seed food: Cooked Jasmine Rice

{
  "type": "food_item",
  "foodItem": {
    "id": "seed-c-rice",
    "name": "Cooked Jasmine Rice",
    "brand": null,
    "source": "manual",
    "servingLabel": "cup",
    "servingQuantity": 1,
    "servingUnit": "cup",
    "macrosPerServing": {
      "calories": 205,
      "proteinGrams": 4,
      "fatGrams": 0,
      "carbsGrams": 45
    },
    "aliases": [],
    "timesLogged": 0,
    "createdAt": "2026-07-16T12:00:00.000Z"
  }
}

food_default

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

snapshot captured 2026-08-02T21:31:14.722Z

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 rice" at 96% confidence.
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 0.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 my usual almonds." (difficulty —)0.1s

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

1 · TTS said Logged Almonds. Using your saved "my usual almonds". Tell me if that is wrong.

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

3 · App data rows written created food_log_entry: Almonds ×1 (20 almonds) 140 cal · 5g P · 5g C · 12g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seed food: Almonds

{
  "type": "food_item",
  "foodItem": {
    "id": "seed-c-almonds",
    "name": "Almonds",
    "brand": null,
    "source": "manual",
    "servingLabel": "20 almonds",
    "servingQuantity": 1,
    "servingUnit": "almonds",
    "macrosPerServing": {
      "calories": 140,
      "proteinGrams": 5,
      "fatGrams": 12,
      "carbsGrams": 5
    },
    "aliases": [],
    "timesLogged": 0,
    "createdAt": "2026-07-16T12:00:00.000Z"
  }
}

food_default

{
  "type": "food_default",
  "phrase": "my usual almonds",
  "foodItemId": "seed-c-almonds",
  "settings": {
    "quickLogMode": "fixed",
    "defaultQuantity": 1,
    "defaultServingLabel": "20 almonds",
    "displayLabel": "my usual almonds",
    "confirmBeforeLog": false
  }
}

snapshot captured 2026-08-02T21:31:26.126Z

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 almonds" at 96% confidence.
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.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 my default milk." (difficulty —)0.1s

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

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

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.1s

1 · TTS said Logged 2 Percent Milk. Using your saved "my default milk". Tell me if that is wrong.

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

3 · App data rows written created food_log_entry: 2 Percent Milk ×1 (cup) 122 cal · 8g P · 12g C · 5g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seed food: 2 Percent Milk

{
  "type": "food_item",
  "foodItem": {
    "id": "seed-c-milk",
    "name": "2 Percent Milk",
    "brand": null,
    "source": "manual",
    "servingLabel": "cup",
    "servingQuantity": 1,
    "servingUnit": "cup",
    "macrosPerServing": {
      "calories": 122,
      "proteinGrams": 8,
      "fatGrams": 5,
      "carbsGrams": 12
    },
    "aliases": [],
    "timesLogged": 0,
    "createdAt": "2026-07-16T12:00:00.000Z"
  }
}

food_default

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

snapshot captured 2026-08-02T21:31:37.310Z

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 milk" at 96% confidence.
Matched the common-food list to "Milk" 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.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 my usual morning shake." (difficulty —)0.1s

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

Why verdict Logged (write-truth verified): Morning Shake Recipe — 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 Codex Test Recipe Morning Shake Recipe. Using your saved "my usual morning shake". Tell me if that is wrong.

2 · Card shown Logged Codex Test Recipe Morning Shake Recipe. Using your saved "my usual morning shake". Tell me if that is wrong.

3 · App data rows written created food_log_entry: Morning Shake Recipe ×1 (shake) 310 cal · 32g P · 28g C · 9g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seed food: Codex Test Recipe Morning Shake Recipe

{
  "type": "food_item",
  "foodItem": {
    "id": "seed-c-shake",
    "name": "Morning Shake Recipe",
    "brand": "Codex Test Recipe",
    "source": "manual",
    "servingLabel": "shake",
    "servingQuantity": 1,
    "servingUnit": "shake",
    "macrosPerServing": {
      "calories": 310,
      "proteinGrams": 32,
      "fatGrams": 9,
      "carbsGrams": 28
    },
    "aliases": [],
    "timesLogged": 0,
    "createdAt": "2026-07-16T12:00:00.000Z"
  }
}

food_default

{
  "type": "food_default",
  "phrase": "my usual morning shake",
  "foodItemId": "seed-c-shake",
  "settings": {
    "quickLogMode": "fixed",
    "defaultQuantity": 1,
    "defaultServingLabel": "shake",
    "displayLabel": "my usual morning shake",
    "confirmBeforeLog": false
  }
}

snapshot captured 2026-08-02T21:31:48.556Z

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 morning shake" 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.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"I had my normal oatmeal." (difficulty —)0.1s

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

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

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.1s

1 · TTS said Logged Cooked Oatmeal. Using your saved "my normal oatmeal". Tell me if that is wrong.

2 · Card shown Logged Cooked Oatmeal. Using your saved "my normal oatmeal". Tell me if that is wrong.

3 · App data rows written created food_log_entry: Cooked Oatmeal ×1 (cup) 150 cal · 6g P · 27g C · 3g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seed food: Cooked Oatmeal

{
  "type": "food_item",
  "foodItem": {
    "id": "seed-c-oatmeal",
    "name": "Cooked Oatmeal",
    "brand": null,
    "source": "manual",
    "servingLabel": "cup",
    "servingQuantity": 1,
    "servingUnit": "cup",
    "macrosPerServing": {
      "calories": 150,
      "proteinGrams": 6,
      "fatGrams": 3,
      "carbsGrams": 27
    },
    "aliases": [],
    "timesLogged": 0,
    "createdAt": "2026-07-16T12:00:00.000Z"
  }
}

food_default

{
  "type": "food_default",
  "phrase": "my normal oatmeal",
  "foodItemId": "seed-c-oatmeal",
  "settings": {
    "quickLogMode": "fixed",
    "defaultQuantity": 1,
    "defaultServingLabel": "cup",
    "displayLabel": "my normal oatmeal",
    "confirmBeforeLog": false
  }
}

snapshot captured 2026-08-02T21:31:59.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 "my normal oatmeal" 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.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 my go-to protein coffee." (difficulty —)0.1s

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

Why verdict Logged (write-truth verified): Protein 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 Codex Test Cafe Protein Coffee. Using your saved "my go to protein coffee". Tell me if that is wrong.

2 · Card shown Logged Codex Test Cafe Protein Coffee. Using your saved "my go to protein coffee". Tell me if that is wrong.

3 · App data rows written created food_log_entry: Protein Coffee ×1 (cup) 120 cal · 15g P · 8g C · 2g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seed food: Codex Test Cafe Protein Coffee

{
  "type": "food_item",
  "foodItem": {
    "id": "seed-c-prot-coffee",
    "name": "Protein Coffee",
    "brand": "Codex Test Cafe",
    "source": "manual",
    "servingLabel": "cup",
    "servingQuantity": 1,
    "servingUnit": "cup",
    "macrosPerServing": {
      "calories": 120,
      "proteinGrams": 15,
      "fatGrams": 2,
      "carbsGrams": 8
    },
    "aliases": [],
    "timesLogged": 0,
    "createdAt": "2026-07-16T12:00:00.000Z"
  }
}

food_default

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

snapshot captured 2026-08-02T21:32:11.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 your saved foods and aliases to "my go to protein 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"Log my usual evening herbal tea." (difficulty —)0.1s

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

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

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.1s

1 · TTS said Logged Herbal Tea. Using your saved "my usual evening herbal tea". Tell me if that is wrong.

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

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

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seed food: Herbal Tea

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

food_default

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

snapshot captured 2026-08-02T21:32:22.527Z

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 evening herbal tea" 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.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"Add the same cottage cheese as yesterday." (difficulty —)0.3s

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

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

1 · TTS said Logged 1% cottage cheese. Using your recent 1% cottage cheese history. Tell me if that is wrong.

2 · Card shown Logged 1% cottage cheese. Using your recent 1% cottage cheese history. Tell me if that is wrong.

3 · App data rows written created food_log_entry: 1% cottage cheese ×1 (1 cup) 163 cal · 28g P · 6.1g C · 2.3g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seed food: Codex Test Dairy Low Fat Cottage Cheese

{
  "type": "food_item",
  "foodItem": {
    "id": "seed-c-cottage",
    "name": "Low Fat Cottage Cheese",
    "brand": "Codex Test Dairy",
    "source": "manual",
    "servingLabel": "cup",
    "servingQuantity": 1,
    "servingUnit": "cup",
    "macrosPerServing": {
      "calories": 160,
      "proteinGrams": 28,
      "fatGrams": 2,
      "carbsGrams": 8
    },
    "aliases": [],
    "timesLogged": 0,
    "createdAt": "2026-07-16T12:00:00.000Z"
  }
}

Seed food history: 0.5 for seed-c-cottage at 2026-07-17T13:00:00.000Z

{
  "type": "food_history",
  "foodItemId": "seed-c-cottage",
  "quantity": 0.5,
  "loggedAt": "2026-07-17T13:00:00.000Z"
}

snapshot captured 2026-08-02T21:32:45.487Z

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.
Matched your past food logs to "1% 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 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)

FAILshould log the entry"Same protein bar as yesterday." (difficulty —)0.6s

Verdict Expected LOG — should log the entry. FAIL: WRITE-TRUTH FAIL — WRONG/MISSING item "Chocolate Peanut Protein Bar" — no saved row with matching identity (rows: Quest Chocolate Brownie Protein Bar)

Why verdict WRITE-TRUTH FAIL — WRONG/MISSING item "Chocolate Peanut Protein Bar" — no saved row with matching identity (rows: Quest Chocolate Brownie Protein Bar)

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.6s

1 · TTS said Logged Quest Quest Chocolate Brownie Protein Bar. Using your recent Quest Quest Chocolate Brownie Protein Bar history. Tell me if that is wrong.

2 · Card shown Logged Quest Quest Chocolate Brownie Protein Bar. Using your recent Quest Quest Chocolate Brownie Protein Bar history. Tell me if that is wrong.

3 · App data rows written created food_log_entry: Quest Chocolate Brownie Protein Bar ×1 (bar) 190 cal · 20g P · 21g C · 7g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seed food: Codex Test Pantry Chocolate Peanut Protein Bar

{
  "type": "food_item",
  "foodItem": {
    "id": "seed-c-yest-bar",
    "name": "Chocolate Peanut Protein Bar",
    "brand": "Codex Test Pantry",
    "source": "manual",
    "servingLabel": "bar",
    "servingQuantity": 1,
    "servingUnit": "bar",
    "macrosPerServing": {
      "calories": 210,
      "proteinGrams": 14,
      "fatGrams": 9,
      "carbsGrams": 23
    },
    "aliases": [],
    "timesLogged": 0,
    "createdAt": "2026-07-16T12:00:00.000Z"
  }
}

Seed food history: 1 for seed-c-yest-bar at 2026-07-17T17:00:00.000Z

{
  "type": "food_history",
  "foodItemId": "seed-c-yest-bar",
  "quantity": 1,
  "loggedAt": "2026-07-17T17:00:00.000Z"
}

snapshot captured 2026-08-02T21:32:57.248Z

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.
Matched your past food logs to "Quest Chocolate Brownie 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 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)

FAILshould log the entry"Log the same salad I had last night." (difficulty —)0.5s

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

1 · TTS said I heard you want the same the same salad I had last night as before, but I do not have a matching saved log yet. Which exact food and amount should I log?

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

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seed food: Codex Test Kitchen Chicken Garden Salad

{
  "type": "food_item",
  "foodItem": {
    "id": "seed-c-salad",
    "name": "Chicken Garden Salad",
    "brand": "Codex Test Kitchen",
    "source": "manual",
    "servingLabel": "bowl",
    "servingQuantity": 1,
    "servingUnit": "bowl",
    "macrosPerServing": {
      "calories": 320,
      "proteinGrams": 28,
      "fatGrams": 14,
      "carbsGrams": 18
    },
    "aliases": [],
    "timesLogged": 0,
    "createdAt": "2026-07-16T12:00:00.000Z"
  }
}

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

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

snapshot captured 2026-08-02T21:33:08.931Z

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"Same oatmeal as this morning." (difficulty —)0.1s

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

Why verdict Logged (write-truth verified): Cooked Oatmeal, Cooked Oatmeal — 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. Using your saved "my normal oatmeal". Tell me if that is wrong.

2 · Card shown Logged Cooked Oatmeal. Using your saved "my normal oatmeal". Tell me if that is wrong.

3 · App data rows written created food_log_entry: Cooked Oatmeal ×1 (cup) 150 cal · 6g P · 27g C · 3g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seed food: Cooked Oatmeal Bowl

{
  "type": "food_item",
  "foodItem": {
    "id": "seed-c-hist-oats",
    "name": "Cooked Oatmeal Bowl",
    "brand": null,
    "source": "manual",
    "servingLabel": "bowl",
    "servingQuantity": 1,
    "servingUnit": "bowl",
    "macrosPerServing": {
      "calories": 180,
      "proteinGrams": 6,
      "fatGrams": 3,
      "carbsGrams": 32
    },
    "aliases": [],
    "timesLogged": 0,
    "createdAt": "2026-07-16T12:00:00.000Z"
  }
}

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

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

snapshot captured 2026-08-02T21:33:20.182Z

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 same eggs I had earlier." (difficulty —)0.2s

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

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

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.2s

1 · TTS said Logged Egg. Using your recent Egg history. Tell me if that is wrong.

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

3 · App data rows written created food_log_entry: Egg ×1 (2 eggs) 143 cal · 12.6g P · 0.7g C · 9.5g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seed food: Scrambled Eggs

{
  "type": "food_item",
  "foodItem": {
    "id": "seed-c-hist-eggs",
    "name": "Scrambled Eggs",
    "brand": null,
    "source": "manual",
    "servingLabel": "serving",
    "servingQuantity": 1,
    "servingUnit": "serving",
    "macrosPerServing": {
      "calories": 180,
      "proteinGrams": 14,
      "fatGrams": 12,
      "carbsGrams": 2
    },
    "aliases": [],
    "timesLogged": 0,
    "createdAt": "2026-07-16T12:00:00.000Z"
  }
}

Seed food history: 1 for seed-c-hist-eggs at 2026-07-18T08:00:00.000Z

{
  "type": "food_history",
  "foodItemId": "seed-c-hist-eggs",
  "quantity": 1,
  "loggedAt": "2026-07-18T08:00:00.000Z"
}

snapshot captured 2026-08-02T21:33:31.598Z

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

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

1 · TTS said Logged Codex Test Recipe Berry Protein Smoothie. Using your saved "Codex Test Recipe Berry Protein Smoothie". Tell me if that is wrong.

2 · Card shown Logged Codex Test Recipe Berry Protein Smoothie. Using your saved "Codex Test Recipe Berry Protein Smoothie". Tell me if that is wrong.

3 · App data rows written created food_log_entry: Berry Protein Smoothie ×1 (smoothie) 280 cal · 22g P · 34g C · 6g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seed food: Codex Test Recipe Berry Protein Smoothie

{
  "type": "food_item",
  "foodItem": {
    "id": "seed-c-smoothie",
    "name": "Berry Protein Smoothie",
    "brand": "Codex Test Recipe",
    "source": "manual",
    "servingLabel": "smoothie",
    "servingQuantity": 1,
    "servingUnit": "smoothie",
    "macrosPerServing": {
      "calories": 280,
      "proteinGrams": 22,
      "fatGrams": 6,
      "carbsGrams": 34
    },
    "aliases": [],
    "timesLogged": 0,
    "createdAt": "2026-07-16T12:00:00.000Z"
  }
}

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

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

snapshot captured 2026-08-02T21:33:42.958Z

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)

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

Verdict Expected LOG — should log the entry. FAIL: WRITE-TRUTH FAIL — WRONG/MISSING item "Grilled Chicken Breast" — no saved row with matching identity (rows: beer)

Why verdict WRITE-TRUTH FAIL — WRONG/MISSING item "Grilled Chicken Breast" — no saved row with matching identity (rows: beer)

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

Pick every reason you think applies. Multiple boxes 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 heard you want the same the chicken I had last time as before, but I do not have a matching saved log yet. Which exact food and amount should I log?

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

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seed food: Grilled Chicken Breast

{
  "type": "food_item",
  "foodItem": {
    "id": "seed-c-hist-chicken",
    "name": "Grilled Chicken Breast",
    "brand": null,
    "source": "manual",
    "servingLabel": "serving",
    "servingQuantity": 1,
    "servingUnit": "serving",
    "macrosPerServing": {
      "calories": 200,
      "proteinGrams": 36,
      "fatGrams": 5,
      "carbsGrams": 0
    },
    "aliases": [],
    "timesLogged": 0,
    "createdAt": "2026-07-16T12:00:00.000Z"
  }
}

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

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

snapshot captured 2026-08-02T21:33:54.267Z

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

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

Why verdict Logged (write-truth verified): Whole Wheat Toast — card not captured.

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.2s

1 · TTS said Logged Whole Wheat Toast. Using your recent Whole Wheat Toast history. Tell me if that is wrong.

2 · Card shown Logged Whole Wheat Toast. Using your recent Whole Wheat Toast history. Tell me if that is wrong.

3 · App data rows written created food_log_entry: Whole Wheat Toast ×1 (slice) 80 cal · 4g P · 14g C · 1g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seed food: Whole Wheat Toast

{
  "type": "food_item",
  "foodItem": {
    "id": "seed-c-toast",
    "name": "Whole Wheat Toast",
    "brand": null,
    "source": "manual",
    "servingLabel": "slice",
    "servingQuantity": 1,
    "servingUnit": "slice",
    "macrosPerServing": {
      "calories": 80,
      "proteinGrams": 4,
      "fatGrams": 1,
      "carbsGrams": 14
    },
    "aliases": [],
    "timesLogged": 0,
    "createdAt": "2026-07-16T12:00:00.000Z"
  }
}

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

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

snapshot captured 2026-08-02T21:34:05.751Z

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 "Toast" 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)

FAILshould log the entry"Snack was one blueberry RX bar." (difficulty —)2.7s

Verdict Expected LOG — should log the entry. FAIL: WRITE-TRUTH FAIL — WRONG item/product identity "blueberry rxbar" — saved row does not hit product alias (rows: beer)

Why verdict WRITE-TRUTH FAIL — WRONG item/product identity "blueberry rxbar" — saved row does not hit product alias (rows: beer)

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

Pick every reason you think applies. Multiple 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 one blueberry rx bar? 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 one blueberry rx bar? 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-02T21:34:19.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 log the entry"Finished one Fairlife Core Power chocolate 42 gram bottle." (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 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-02T21:34:32.958Z

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

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

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

FAILshould log the entry"Track one Chobani zero sugar vanilla cup." (difficulty —)0.5s

Verdict Expected LOG — should log the entry. FAIL: WRITE-TRUTH FAIL — MACROS off for "chobani zero sugar vanilla": logged 120 kcal vs expected ~60 (§14 15pct/25cal band)

Why verdict WRITE-TRUTH FAIL — MACROS off for "chobani zero sugar vanilla": logged 120 kcal vs expected ~60 (§14 15pct/25cal band)

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.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-02T21:34:44.617Z

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"Save one Quest chocolate brownie protein bar." (difficulty —)1.1s

Verdict Expected LOG — should log the entry. FAIL: WRITE-TRUTH FAIL — WRONG item/product identity "quest chocolate brownie bar" — saved row does not hit product alias (rows: cookie)

Why verdict WRITE-TRUTH FAIL — WRONG item/product identity "quest chocolate brownie bar" — saved row does not hit product alias (rows: cookie)

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

Pick every reason you think applies. Multiple 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 found a likely match for quest quest chocolate brownie protein bar, but I still need a clearer amount or product detail before I can log it. What exact food and amount should I use? I did not log it yet.

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

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

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

snapshot captured 2026-08-02T21:34:56.883Z

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 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 sea salt" — saved row does not hit product alias (rows: Dark chocolate, No Cow Chocolate Sea Salt Bar)

Why verdict WRITE-TRUTH FAIL — WRONG item/product identity "kind dark chocolate nuts sea salt" — saved row does not hit product alias (rows: Dark chocolate, No Cow Chocolate Sea Salt Bar)

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.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-02T21:35:08.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)

FAILshould log the entry"Log a medium Fuji apple and one KIND peanut butter dark chocolate bar." (difficulty —)0.9s

Verdict Expected LOG — should log the entry. FAIL: WRITE-TRUTH FAIL — WRONG/MISSING item "one kind peanut butter dark chocolat" — no saved row with matching identity (rows: Chocolate Candy, Peanut Butter Filled, Apple, Chocolate Candy, Peanut Butter Filled)

Why verdict WRITE-TRUTH FAIL — WRONG/MISSING item "one kind peanut butter dark chocolat" — no saved row with matching identity (rows: Chocolate Candy, Peanut Butter Filled, Apple, Chocolate Candy, Peanut Butter Filled)

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

Pick every reason you think applies. Multiple boxes 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 Logged Apple and Chocolate Candy, Peanut Butter Filled. Assumed catalog default servings where you did not say an amount — tell me if that is not right.

2 · Card shown Logged Apple and Chocolate Candy, Peanut Butter Filled. 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: Apple ×1 (182 g) 95 cal · 0.5g P · 25.5g C · 0.4g F
created food_log_entry: Chocolate Candy, Peanut Butter Filled ×1 (1 large/king size) 438 cal · 7g P · 57.7g C · 22.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-02T21:35:20.513Z

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 oatmeal and black coffee." (difficulty —)0.3s

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

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

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.3s

1 · TTS said Logged Cooked oatmeal and Coffee. Assumed catalog default servings where you did not say an amount — tell me if that is not right.

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

3 · App data rows written created food_log_entry: Cooked oatmeal ×1 (100 g) 71 cal · 2.5g P · 12g C · 1.5g F
created food_log_entry: Coffee ×1 (100 g) 1 cal · 0.1g P · 0g C · 0g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

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

snapshot captured 2026-08-02T21:35:31.959Z

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"Breakfast was two eggs and one slice toast." (difficulty —)0.3s

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

Why verdict Logged (write-truth verified): Egg, Toast — card not captured.

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.3s

1 · TTS said Logged two eggs and Toast.

2 · Card shown Logged two eggs and Toast.

3 · App data rows written created food_log_entry: Egg ×1 (2 eggs) 143 cal · 12.6g P · 0.7g C · 9.5g F
created food_log_entry: Toast ×1 (1 slice) 69 cal · 2.3g P · 12.7g C · 0.8g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

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

snapshot captured 2026-08-02T21:35:43.472Z

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"Lunch was a turkey sandwich and an apple." (difficulty —)1.6s

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

Why verdict Asked a clarification as expected.

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 1.6s

1 · TTS said I need to resolve a turkey sandwich before I log this meal. What should I use for a turkey sandwich?

2 · Card shown I need to resolve a turkey sandwich before I log this meal. What should I use for a turkey sandwich?

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

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

snapshot captured 2026-08-02T21:35:56.244Z

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"Snack was almonds and a banana." (difficulty —)0.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 0.3s

1 · TTS said How much should I log for Almonds? I did not log them yet because the amounts were not clear.

2 · Card shown How much should I log for Almonds? 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-02T21:36:07.704Z

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 "almonds" at 90% confidence.
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 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 ask a clarifying question"Dinner was salmon and steamed broccoli." (difficulty —)0.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 0.3s

1 · TTS said How much should I log for Salmon and Broccoli? I did not log them yet because the amounts were not clear.

2 · Card shown How much should I log for Salmon and Broccoli? 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-02T21:36:19.098Z

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.
Matched your past food logs to "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 1.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 ask a clarifying question"I ate Greek yogurt and blueberries." (difficulty —)0.6s

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

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

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.6s

1 · TTS said Logged Plain Greek yogurt and Blueberries. Assumed catalog default servings where you did not say an amount — tell me if that is not right.

2 · Card shown Logged Plain Greek yogurt and Blueberries. 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: Plain Greek yogurt ×1 (100 g) 97 cal · 9g P · 3.9g C · 5g F
created food_log_entry: Blueberries ×1 (148 g) 84 cal · 1g P · 21.5g C · 0.4g F
created food_log_entry: Plain Greek yogurt ×1 (100 g) 97 cal · 9g P · 3.9g C · 5g F
created food_log_entry: Blueberries ×1 (148 g) 84 cal · 1g P · 21.5g C · 0.4g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

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

snapshot captured 2026-08-02T21:36:30.848Z

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"Track chicken breast and brown rice." (difficulty —)0.2s

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

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

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.2s

1 · TTS said How much should I log for Chicken breast and Cooked brown rice? I did not log them yet because the amounts were not clear.

2 · Card shown How much should I log for Chicken breast and Cooked brown rice? 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-02T21:36:53.798Z

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 "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 1.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 ask a clarifying question"Add cottage cheese and strawberries." (difficulty —)0.5s

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

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

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.5s

1 · TTS said Logged Cottage cheese and Strawberries. Assumed catalog default servings where you did not say an amount — tell me if that is not right.

2 · Card shown Logged Cottage cheese and Strawberries. 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: Cottage cheese ×1 (100 g) 98 cal · 11.1g P · 3.4g C · 4.3g F
created food_log_entry: Strawberries ×1 (12 g) 4 cal · 0.1g P · 0.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-02T21:37:05.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)

PASSshould ask a clarifying question"I had a protein bar and sparkling water." (difficulty —)0.6s

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

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

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.6s

1 · TTS said Logged a protein bar and Water. Assumed catalog default servings where you did not say an amount — tell me if that is not right.

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

3 · App data rows written created food_log_entry: Generic protein bar ×1 (1 protein bar) 200 cal · 20g P · 22g C · 7g F
created food_log_entry: Water ×1 (240 g) 0 cal · 0g P · 0g C · 0g F
created food_log_entry: Generic protein bar ×1 (1 protein bar) 200 cal · 20g P · 22g C · 7g F
created food_log_entry: Water ×1 (240 g) 0 cal · 0g P · 0g C · 0g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

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

snapshot captured 2026-08-02T21:37:17.120Z

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 soup and a side salad." (difficulty —)0.6s

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

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

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.6s

1 · TTS said Logged Soup and Side salad. Assumed catalog default servings where you did not say an amount — tell me if that is not right.

2 · Card shown Logged Soup and Side salad. 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: Soup ×1 (245 g) 123 cal · 6.1g P · 15.9g C · 4.4g F
created food_log_entry: Side salad ×1 (85 g) 17 cal · 1g P · 3.4g 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-02T21:37:28.892Z

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"Breakfast was oatmeal, banana, and coffee." (difficulty —)0.5s

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

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

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.5s

1 · TTS said Logged Cooked oatmeal, Banana, and Coffee. Assumed catalog default servings where you did not say an amount — tell me if that is not right.

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

3 · App data rows written created food_log_entry: Cooked oatmeal ×1 (100 g) 71 cal · 2.5g P · 12g C · 1.5g F
created food_log_entry: Banana ×1 (118 g) 105 cal · 1.3g P · 27.1g C · 0.4g F
created food_log_entry: Coffee ×1 (100 g) 1 cal · 0.1g P · 0g C · 0g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

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

snapshot captured 2026-08-02T21:37:40.496Z

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

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

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

PASSshould ask a clarifying question"I ate an apple, a cheese stick, and crackers." (difficulty —)0.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 0.2s

1 · TTS said How much should I log for Crackers? I did not log them yet because the amounts were not clear.

2 · Card shown How much should I log for Crackers? 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-02T21:37:51.843Z

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 "apple" 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 ask a clarifying question"Dinner was steak, potatoes, and green beans." (difficulty —)0.5s

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

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

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.5s

1 · TTS said Logged Steak, Potato, and Green beans. Assumed catalog default servings where you did not say an amount — tell me if that is not right.

2 · Card shown Logged Steak, Potato, and Green beans. 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: Steak ×1 (85 g) 213 cal · 23g P · 0g C · 12.8g F
created food_log_entry: Potato ×1 (138 g) 120 cal · 2.6g P · 27.7g C · 0.1g F
created food_log_entry: Green beans ×1 (100 g) 35 cal · 1.9g P · 7.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-02T21:38:03.525Z

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"Snack was carrots and hummus." (difficulty —)0.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 0.3s

1 · TTS said How much should I log for Baby carrots and Hummus? I did not log them yet because the amounts were not clear.

2 · Card shown How much should I log for Baby carrots and Hummus? 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-02T21:38:14.930Z

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 "Baby carrots" 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 ask a clarifying question"Lunch was a salad and a roll." (difficulty —)1.4s

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

1 · TTS said What should I use for a salad? I did not log it yet because I could not match it safely.

2 · Card shown What should I use for a salad? 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-02T21:38:27.513Z

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 rice, beans, and chicken." (difficulty —)0.4s

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

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

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.4s

1 · TTS said Logged Cooked white rice, Beans, and Chicken breast. Assumed catalog default servings where you did not say an amount — tell me if that is not right.

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

3 · App data rows written created food_log_entry: Cooked white rice ×1 (100 g) 130 cal · 2.7g P · 28g C · 0.3g F
created food_log_entry: Beans ×1 (86 g) 109 cal · 7.5g P · 19.6g C · 0.4g F
created food_log_entry: Chicken breast ×1 (100 g) 165 cal · 31g P · 0g C · 3.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-02T21:38:39.116Z

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 yogurt, granola, and honey." (difficulty —)0.7s

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

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

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.7s

1 · TTS said Logged Plain Greek yogurt, Granola, and Honey. Assumed catalog default servings where you did not say an amount — tell me if that is not right.

2 · Card shown Logged Plain Greek yogurt, Granola, and Honey. 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: Plain Greek yogurt ×1 (100 g) 97 cal · 9g P · 3.9g C · 5g F
created food_log_entry: Granola ×1 (100 g) 471 cal · 10g P · 64g C · 20g F
created food_log_entry: Honey ×1 (21 g) 64 cal · 0.1g P · 17.3g 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-02T21:38:51.000Z

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 eggs, bacon, and orange juice." (difficulty —)0.6s

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

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

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.6s

1 · TTS said Logged Egg, Bacon, and Orange juice. Assumed catalog default servings where you did not say an amount — tell me if that is not right.

2 · Card shown Logged Egg, Bacon, and Orange juice. Assumed catalog default servings where you did not say an amount — tell me if that is not right.

3 · App data rows written created food_log_entry: Egg ×1 (50 g) 72 cal · 6.3g P · 0.4g C · 4.8g F
created food_log_entry: Bacon ×1 (24 g) 130 cal · 8.9g P · 0.3g C · 10.1g F
created food_log_entry: Orange juice ×1 (100 g) 45 cal · 0.7g P · 10.4g 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-02T21:39:02.753Z

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

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

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

PASSshould ask a clarifying question"I ate pasta and a side of broccoli." (difficulty —)0.8s

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

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

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.8s

1 · TTS said Logged Cooked pasta and Broccoli. Assumed catalog default servings where you did not say an amount — tell me if that is not right.

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

3 · App data rows written created food_log_entry: Cooked pasta ×1 (140 g) 220 cal · 8.1g P · 43.3g C · 1.3g F
created food_log_entry: Broccoli ×1 (100 g) 35 cal · 2.4g P · 7.2g C · 0.4g F
created food_log_entry: Cooked pasta ×1 (140 g) 220 cal · 8.1g P · 43.3g C · 1.3g F
created food_log_entry: Broccoli ×1 (100 g) 35 cal · 2.4g P · 7.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-02T21:39:14.692Z

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 banana and peanut butter." (difficulty —)0.4s

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

1 · TTS said How much should I log for Peanut butter? I did not log them yet because the amounts were not clear.

2 · Card shown How much should I log for Peanut 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-02T21:39:26.245Z

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 1.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 ask a clarifying question"Breakfast was cereal and milk." (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 I need to resolve cereal before I log this meal. What should I use for cereal?

2 · Card shown I need to resolve cereal before I log this meal. What should I use for 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-02T21:39:38.517Z

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

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

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

PASSshould log the entry"I had an omelet with three eggs, one ounce of cheddar cheese and a tomato" (difficulty —)0.5s

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

Why verdict Logged (write-truth verified): Egg, Cheddar cheese, Omelet, Tomato — 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 Omelet. Includes three eggs, one ounce of cheddar cheese, and a tomato.

2 · Card shown Logged Omelet. Includes three eggs, one ounce of cheddar cheese, and a tomato.

3 · App data rows written created food_log_entry: Omelet ×1 (serving) 351 cal · 26.5g P · 6.8g C · 23.9g F
created food_log_entry: Egg ×1 (3 eggs) 215 cal · 18.9g P · 1g C · 14.3g F
created food_log_entry: Cheddar cheese ×1 (1 oz) 114 cal · 6.5g P · 1g C · 9.4g F
created food_log_entry: Tomato ×1 (1 tomato) 22 cal · 1.1g P · 4.8g 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-02T21:39:50.119Z

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 "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.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 ask a clarifying question"Log a protein shake with banana, peanut butter, and oats." (difficulty —)7.6s

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

1 · TTS said Logging your protein shake with banana, peanut butter, and oats — still looking up the nutrition details; they'll appear in your log shortly.

2 · Card shown Logging your protein shake with banana, peanut butter, and oats — still looking up the nutrition details; they'll appear in your log shortly.

3 · App data rows written created food_log_entry: Protein Shake ×1 (serving) 682 cal · 26.2g P · 99.7g C · 23.4g F
created food_log_entry: Banana ×1 (1 banana) 105 cal · 1.3g P · 27.1g C · 0.4g F
created food_log_entry: Peanut butter ×1 (32 g) 188 cal · 8g P · 6.3g C · 16.1g F
created food_log_entry: Dry oats ×1 (100 g) 389 cal · 16.9g P · 66.3g C · 6.9g F
pending_created food_log_entry: a protein shake with banana, peanut butter, and oats (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-02T21:40:08.935Z

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 salad with chicken, walnuts, and ranch." (difficulty —)3.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 3.2s

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-02T21:42:08.934Z

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

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

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

FAILshould log the entry"Breakfast was an omelet with cheddar and olive oil." (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 How much cheddar should I use? I did not log it yet because the amount can change the nutrition.

2 · Card shown How much cheddar should I use? I did not log it yet because the amount 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-02T21:42:21.406Z

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

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

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

PASSshould ask a clarifying question"I made chili with beef, beans, tomatoes, and oil." (difficulty —)2.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 2.3s

1 · TTS said Which beans should I use?

2 · Card shown Which 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-02T21:42:34.848Z

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"Dinner was a burrito bowl with rice, beans, steak, and queso." (difficulty —)1.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 1.6s

1 · TTS said Which beans should I use?

2 · Card shown Which 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-02T21:42:59.196Z

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 ramen with pork and egg." (difficulty —)0.5s

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

1 · TTS said How much should I log for Pork? I did not log it yet because the amount was not clear.

2 · Card shown How much should I log for Pork? 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-02T21:43:10.812Z

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" 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.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"Log a turkey sandwich with mayo and cheddar." (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 What should I use for mayo?

2 · Card shown What should I use for mayo?

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

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

snapshot captured 2026-08-02T21:43:23.112Z

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 built a yogurt bowl with granola, honey, and blueberries." (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 Yogurt Bowl. Includes granola, Honey, and blueberries.

2 · Card shown Logged Yogurt Bowl. Includes granola, Honey, and blueberries.

3 · App data rows written created food_log_entry: Yogurt Bowl ×1 (serving) 619 cal · 11.1g P · 102.8g C · 20.4g F
created food_log_entry: Granola ×1 (100 g) 471 cal · 10g P · 64g C · 20g F
created food_log_entry: Honey ×1 (21 g) 64 cal · 0.1g P · 17.3g C · 0g F
created food_log_entry: Blueberries ×1 (148 g) 84 cal · 1g P · 21.5g C · 0.4g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

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

snapshot captured 2026-08-02T21:43:35.592Z

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"Dinner was pad thai with chicken, peanuts, and bean sprouts." (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 What should I use for peanuts?

2 · Card shown What should I use for peanuts?

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

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

snapshot captured 2026-08-02T21:43:49.053Z

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

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

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

PASSshould ask a clarifying question"Add some oatmeal." (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 some oatmeal did you have?

2 · Card shown How much some oatmeal 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-02T21:44:01.073Z

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 cereal." (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 food did you log? Could you be more specific?

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

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

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

snapshot captured 2026-08-02T21:44:12.988Z

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 rice for dinner." (difficulty —)1.5s

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

Why verdict Asked a clarification as expected.

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 1.5s

1 · TTS said 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-02T21:44:25.632Z

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 1.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 ask a clarifying question"Track pasta." (difficulty —)0.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 0.3s

1 · TTS said How much pasta did you have?

2 · Card shown How much 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-02T21:44:37.056Z

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

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

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

PASSshould ask a clarifying question"I ate chips." (difficulty —)0.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 0.3s

1 · TTS said How much chips did you have?

2 · Card shown How much chips 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-02T21:44:48.580Z

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 nuts." (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 nuts? 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 nuts? 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-02T21:45:00.851Z

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

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

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

PASSshould ask a clarifying question"Log a bowl of soup." (difficulty —)2.7s

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

Why verdict Asked a clarification as expected.

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 2.7s

1 · TTS said What exact food and amount should I use for a bowl of soup? 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 bowl of soup? 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-02T21:45:14.868Z

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

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

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

PASSshould ask a clarifying question"I had a plate of pasta." (difficulty —)11.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 11.8s

1 · TTS said Was the pasta plain, or did it have sauce, butter, or oil? I did not log it yet because add-ons can change the nutrition.

2 · Card shown Was the pasta plain, or did it have sauce, butter, or oil? 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-02T21:45:37.774Z

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

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

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

PASSshould ask a clarifying question"Track juice." (difficulty —)0.5s

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

Why verdict Asked a clarification as expected.

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.5s

1 · TTS said How much juice did you have?

2 · Card shown How much juice 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-02T21:45:49.430Z

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 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-02T21:46:00.664Z

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 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 ask a clarifying question"I drank wine." (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 What exact food and amount should I use for wine? 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 wine? 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-02T21:46:12.618Z

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

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

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

PASSshould ask a clarifying question"Log ice cream." (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 Vanilla ice cream? I did not log it yet because the amount was not clear.

2 · Card shown How much should I log for Vanilla ice cream? 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-02T21:46:23.851Z

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 "Vanilla ice cream" at 90% confidence.
Matched your past food logs to "ice cream" 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.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 ask a clarifying question"Had some trail mix." (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 What exact food and amount should I use for trail mix? 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 trail mix? 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-02T21:46:36.766Z

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

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

Why verdict Asked a clarification as expected.

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 1.6s

1 · TTS said How much popcorn did you have?

2 · Card shown How much popcorn 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-02T21:46:49.481Z

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

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

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

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

Verdict Expected CLARIFY — should ask a clarifying question. FAIL: WRONG item vs seeded default/key — no saved food row to verify good-guess write against seed/key

Why verdict WRONG item vs seeded default/key — no saved food row to verify good-guess write against seed/key

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

Pick every reason you think applies. Multiple boxes 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 a protein bar. Assumed 1 protein bar as the default serving. Tell me if you want a different amount.

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

3 · App data rows written created food_log_entry: Generic protein bar ×1 (1 protein bar) 200 cal · 20g P · 22g C · 7g F
created food_log_entry: Generic protein bar ×1 (1 protein bar) 200 cal · 20g P · 22g C · 7g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

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

snapshot captured 2026-08-02T21:47:11.745Z

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.
Matched your saved foods and aliases to "a 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 6.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 ask a clarifying question"Log a yogurt." (difficulty —)0.2s

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

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

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.2s

1 · TTS said Logged Plain Greek yogurt.

2 · Card shown Logged Plain Greek yogurt.

3 · App data rows written created food_log_entry: Plain Greek yogurt ×1 (100 g) 97 cal · 9g P · 3.9g C · 5g F
created food_log_entry: Plain Greek yogurt ×1 (100 g) 97 cal · 9g P · 3.9g 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-02T21:47:25.763Z

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 past food logs to "Yogurt Bowl" 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.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 ask a clarifying question"Track milk." (difficulty —)1.4s

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

1 · TTS said How much milk did you have?

2 · Card shown How much 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-02T21:47:38.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)

PASSshould ask a clarifying question"I ate a sandwich." (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 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-02T21:47:51.170Z

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

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

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

PASSshould ask a clarifying question"Add a shake." (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 one did you mean? 1. protein shake, 2. my usual morning shake, 3. codex test recipe morning shake recipe, 4. Morning Shake Recipe — Codex Test Recipe

2 · Card shown Which one did you mean? 1. protein shake, 2. my usual morning shake, 3. codex test recipe morning shake recipe, 4. Morning Shake Recipe — Codex Test Recipe

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

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

snapshot captured 2026-08-02T21:48:03.386Z

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

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

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

PASSshould ask a clarifying question"I had coffee with milk." (difficulty —)5.2s

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

Why verdict Asked a clarification as expected.

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 5.2s

1 · TTS said How much coffee with milk did you have?

2 · Card shown How much coffee 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-02T21:48:19.726Z

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 bread." (difficulty —)2.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 2.1s

1 · TTS said How much bread did you have?

2 · Card shown How much bread 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-02T21:48:33.004Z

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"Track a burger." (difficulty —)0.2s

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

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

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.2s

1 · TTS said Logged Hamburger.

2 · Card shown Logged Hamburger.

3 · App data rows written created food_log_entry: Hamburger ×1 (1 burger) 381 cal · 18.8g P · 39.2g C · 16.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-02T21:48:44.270Z

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

1 · TTS said How much pizza did you have?

2 · Card shown How much pizza 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-02T21:48:55.865Z

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

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

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

FAILshould ask a clarifying question"Add a muffin." (difficulty —)0.8s

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

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

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.8s

1 · TTS said Logged Muffin, Plain (1 muffin (1 small)) with an estimated macro range.

2 · Card shown Logged Muffin, Plain (1 muffin (1 small)) — the macros are an estimate since this food varies by brand.

3 · App data rows written created food_log_entry: Muffin, Plain ×1 (1 muffin (1 small)) 262 cal · 4.1g P · 36.4g 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-02T21:49:07.820Z

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

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

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

PASSshould ask a clarifying question"Log my usual coffee size." (difficulty —)0.1s

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

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

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.1s

1 · TTS said Logged coffee. Using your saved "log my usual coffee size". Tell me if that is wrong.

2 · Card shown Logged coffee. Using your saved "log my usual coffee size". Tell me if that is wrong.

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

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seed food: coffee

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

food_default

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

snapshot captured 2026-08-02T21:49:19.066Z

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 "log my usual coffee size" 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 ask a clarifying question"Add the regular breakfast portion." (difficulty —)0.1s

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

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

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.1s

1 · TTS said Logged breakfast portion. Using your saved "add the regular breakfast portion". Tell me if that is wrong.

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

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

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seed food: breakfast portion

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

food_default

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

snapshot captured 2026-08-02T21:49:30.341Z

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 "add the regular breakfast portion" 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.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"Track my default snack amount." (difficulty —)0.1s

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

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

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.1s

1 · TTS said Logged snack. Using your saved "track my default snack amount". Tell me if that is wrong.

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

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

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seed food: snack

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

food_default

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

snapshot captured 2026-08-02T21:49:41.630Z

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 "track my default snack amount" 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 ask a clarifying question"I had the usual lunch size." (difficulty —)0.1s

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

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

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.1s

1 · TTS said Logged lunch. Using your saved "i had the usual lunch size". Tell me if that is wrong.

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

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

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seed food: lunch

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

food_default

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

snapshot captured 2026-08-02T21:49:52.848Z

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 "i had the usual lunch size" 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.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"Half a cup." (difficulty —)0.5s

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

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-02T21:50:05.988Z

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"One cup, plain." (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-02T21:50:17.221Z

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.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 complete the pending action"The Quest chocolate brownie." (difficulty —)1.7s

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

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

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 1.7s

1 · TTS said I could not finish that request safely.

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

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

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

snapshot captured 2026-08-02T21:50:30.066Z

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 "Quest Chocolate Brownie 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 1.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 complete the pending action"Two percent milk." (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 How much should I log for 2% milk? I did not log it yet because the amount was not clear.

2 · Card shown How much should I log for 2% milk? 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-02T21:50:41.364Z

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 "2% milk" at 98% confidence.
Matched your saved foods and aliases to "one cup two percent milk" 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.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 complete the pending action"No, that's not it — the plain 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 What should I change about lunch?

2 · Card shown What should I change about lunch?

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

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

snapshot captured 2026-08-02T21:50:52.581Z

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)

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

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

1 · TTS said Got it — chocolate, not vanilla. Do you want to log the chocolate muffin now?

2 · Card shown Got it — chocolate, not vanilla. Do you want to log the chocolate muffin now?

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

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

snapshot captured 2026-08-02T21:51:06.639Z

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)

UNVERIFIEDunclassifiedshould complete the pending action"No, not the sweetened yogurt." (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 What should I change about lunch?

2 · Card shown What should I change about lunch?

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

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

snapshot captured 2026-08-02T21:51:17.950Z

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.

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

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

Why verdict Declined / no unwanted write.

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.0s

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

Seed food: Pending Food Item

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

Seed food history: 1 for seed-c-corr-pending-3 at 2026-07-18T11:00:00.000Z

{
  "type": "food_history",
  "foodItemId": "seed-c-corr-pending-3",
  "quantity": 1,
  "loggedAt": "2026-07-18T11:00:00.000Z"
}

snapshot captured 2026-08-02T21:51:40.601Z

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.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 complete the pending action"No, that's not the bar I meant." (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 What should I change about lunch?

2 · Card shown What should I change about lunch?

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

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

snapshot captured 2026-08-02T21:52:03.047Z

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)

UNVERIFIEDunclassifiedshould complete the pending action"Not the large — the small apple." (difficulty —)5.3s

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

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 5.3s

1 · TTS said What exact food and amount should I use for Apple? 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 Apple? 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-02T21:52:19.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)

UNVERIFIEDunclassifiedshould complete the pending action"Wrong item. Pick the grilled chicken." (difficulty —)5.3s

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

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 5.3s

1 · TTS said What exact food and amount should I use for wrong item pick the grilled chicken? 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 wrong item pick the grilled chicken? 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-02T21:52:36.116Z

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"That's not it; the unsweetened one." (difficulty —)2.6s

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

1 · TTS said Got it — unsweetened, not sweetened. Do you want to log the unsweetened version now?

2 · Card shown Got it — unsweetened, not sweetened. Do you want to log the unsweetened version now?

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

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

snapshot captured 2026-08-02T21:53:01.304Z

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 complete the pending action"No, the other yogurt." (difficulty —)6.5s

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

1 · TTS said Updated to the other yogurt.

2 · Card shown Updated the food entry from "lunch" to "the other yogurt".

3 · App data rows written updated food_log_entry: Plain Greek yogurt ×1 (100 g) 97 cal · 9g P · 3.9g 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-02T21:53:18.932Z

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

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

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

UNVERIFIEDunclassifiedshould complete the pending action"Not those almonds — the dry roasted." (difficulty —)7.5s

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

My override

Things I think are wrong

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

Comprehension

Picked wrong food Wrong quantity Should have asked (over-logged) Shouldn't have asked (over-asked) Wrong action entirely

Execution

Didn't save to DB Wrong data saved No voice/TTS Card missing/wrong No chat

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

Use this when the report failed something that should have passed.

Actually right

Food/action was right Quantity/serving was right Asking was right Not asking was right Answer was right No app data row was expected App data row was right Voice/card/chat was acceptable

Report/grader issue

Report expected the wrong result Evidence was enough to judge Failure reason was not valid

Other thing actually right (describe below)

Pick every reason you think applies. Multiple boxes are allowed because one utterance can be wrong in more than one way. Use the note below for "Other" or extra detail.

Timing 7.5s

1 · TTS said What exact food and amount should I use for Almonds? 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 Almonds? 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-02T21:53:48.701Z

6 · Why this food No food-decision explanation was captured for this path.

7 · Lookup method No lookup method was captured for this path.

8 · Candidates → decider no candidate list captured (this path did not run DB resolution — e.g. provisional branded log)

FAILshould delete the entry"Delete the banana from earlier." (difficulty —)0.1s

Verdict Expected DELETE — should delete the entry. FAIL: Did not delete (not understood / no removal).

Why verdict Did not delete (not understood / no removal).

My override

Things I think are wrong

Use this when the report passed something that should have failed.

Comprehension

Picked wrong food Wrong quantity Should have asked (over-logged) Shouldn't have asked (over-asked) Wrong action entirely

Execution

Didn't save to DB Wrong data saved No voice/TTS Card missing/wrong No chat

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

Use this when the report failed something that should have passed.

Actually right

Food/action was right Quantity/serving was right Asking was right Not asking was right Answer was right No app data row was expected App data row was right Voice/card/chat was acceptable

Report/grader issue

Report expected the wrong result Evidence was enough to judge Failure reason was not valid

Other thing actually right (describe below)

Pick every reason you think applies. Multiple boxes are allowed because one utterance can be wrong in more than one way. Use the note below for "Other" or extra detail.

Timing 0.1s

1 · TTS said I could not find a list matching earlier. Which list has banana?

2 · Card shown I could not find a list matching earlier. Which list has banana?

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T21:54:11.165Z

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 "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 1.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"Remove that Quest bar." (difficulty —)0.1s

Verdict Expected DELETE — should delete the entry. FAIL: Did not delete (not understood / no removal).

Why verdict Did not delete (not understood / no removal).

My override

Things I think are wrong

Use this when the report passed something that should have failed.

Comprehension

Picked wrong food Wrong quantity Should have asked (over-logged) Shouldn't have asked (over-asked) Wrong action entirely

Execution

Didn't save to DB Wrong data saved No voice/TTS Card missing/wrong No chat

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

Use this when the report failed something that should have passed.

Actually right

Food/action was right Quantity/serving was right Asking was right Not asking was right Answer was right No app data row was expected App data row was right Voice/card/chat was acceptable

Report/grader issue

Report expected the wrong result Evidence was enough to judge Failure reason was not valid

Other thing actually right (describe below)

Pick every reason you think applies. Multiple boxes are allowed because one utterance can be wrong in more than one way. Use the note below for "Other" or extra detail.

Timing 0.1s

1 · TTS said 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: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T21:54:22.413Z

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 "Quest Chocolate Brownie 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.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 delete the entry"Delete the oatmeal 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: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T21:54:33.632Z

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 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)

FAILshould delete the entry"Take off the eggs." (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: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T21:54:44.843Z

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 "egg" at 90% confidence.
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.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"Remove the blueberries." (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: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T21:54:56.058Z

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 "blueberries" at 90% 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.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 the chicken log." (difficulty —)0.1s

Verdict Expected DELETE — should delete the entry. FAIL: Did not delete (not understood / no removal).

Why verdict Did not delete (not understood / no removal).

My override

Things I think are wrong

Use this when the report passed something that should have failed.

Comprehension

Picked wrong food Wrong quantity Should have asked (over-logged) Shouldn't have asked (over-asked) Wrong action entirely

Execution

Didn't save to DB Wrong data saved No voice/TTS Card missing/wrong No chat

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

Use this when the report failed something that should have passed.

Actually right

Food/action was right Quantity/serving was right Asking was right Not asking was right Answer was right No app data row was expected App data row was right Voice/card/chat was acceptable

Report/grader issue

Report expected the wrong result Evidence was enough to judge Failure reason was not valid

Other thing actually right (describe below)

Pick every reason you think applies. Multiple boxes are allowed because one utterance can be wrong in more than one way. Use the note below for "Other" or extra detail.

Timing 0.1s

1 · TTS said 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: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T21:55:07.269Z

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 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)

FAILshould delete the entry"Scratch the peanut butter." (difficulty —)0.1s

Verdict Expected DELETE — should delete the entry. FAIL: Did not delete (not understood / no removal).

Why verdict Did not delete (not understood / no removal).

My override

Things I think are wrong

Use this when the report passed something that should have failed.

Comprehension

Picked wrong food Wrong quantity Should have asked (over-logged) Shouldn't have asked (over-asked) Wrong action entirely

Execution

Didn't save to DB Wrong data saved No voice/TTS Card missing/wrong No chat

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

Use this when the report failed something that should have passed.

Actually right

Food/action was right Quantity/serving was right Asking was right Not asking was right Answer was right No app data row was expected App data row was right Voice/card/chat was acceptable

Report/grader issue

Report expected the wrong result Evidence was enough to judge Failure reason was not valid

Other thing actually right (describe below)

Pick every reason you think applies. Multiple boxes are allowed because one utterance can be wrong in more than one way. Use the note below for "Other" or extra detail.

Timing 0.1s

1 · TTS said 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: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T21:55:18.474Z

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 "peanut butter" at 90% confidence.
Matched the common-food list to "Peanut butter" 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.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 the milk entry." (difficulty —)0.1s

Verdict Expected DELETE — should delete the entry. FAIL: Did not delete (not understood / no removal).

Why verdict Did not delete (not understood / no removal).

My override

Things I think are wrong

Use this when the report passed something that should have failed.

Comprehension

Picked wrong food Wrong quantity Should have asked (over-logged) Shouldn't have asked (over-asked) Wrong action entirely

Execution

Didn't save to DB Wrong data saved No voice/TTS Card missing/wrong No chat

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

Use this when the report failed something that should have passed.

Actually right

Food/action was right Quantity/serving was right Asking was right Not asking was right Answer was right No app data row was expected App data row was right Voice/card/chat was acceptable

Report/grader issue

Report expected the wrong result Evidence was enough to judge Failure reason was not valid

Other thing actually right (describe below)

Pick every reason you think applies. Multiple boxes are allowed because one utterance can be wrong in more than one way. Use the note below for "Other" or extra detail.

Timing 0.1s

1 · TTS said 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: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T21:55:29.712Z

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 "Milk" 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 delete the entry"Delete that avocado I logged last night." (difficulty —)0.2s

Verdict Expected DELETE — should delete the entry. PASS: Deleted/removed the requested food with database removal proof.

Why verdict Deleted/removed the requested food with database removal proof.

My override

Things I think are wrong

Use this when the report passed something that should have failed.

Comprehension

Picked wrong food Wrong quantity Should have asked (over-logged) Shouldn't have asked (over-asked) Wrong action entirely

Execution

Didn't save to DB Wrong data saved No voice/TTS Card missing/wrong No chat

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

Use this when the report failed something that should have passed.

Actually right

Food/action was right Quantity/serving was right Asking was right Not asking was right Answer was right No app data row was expected App data row was right Voice/card/chat was acceptable

Report/grader issue

Report expected the wrong result Evidence was enough to judge Failure reason was not valid

Other thing actually right (describe below)

Pick every reason you think applies. Multiple boxes 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 Deleted Avocado.

2 · Card shown Deleted Avocado.

3 · App data rows written deleted food_log_entry:

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seed food: avocado

{
  "type": "food_item",
  "foodItem": {
    "id": "seed-c-del-0-avocado",
    "name": "avocado",
    "brand": null,
    "source": "manual",
    "servingLabel": "serving",
    "servingQuantity": 1,
    "servingUnit": "serving",
    "macrosPerServing": {
      "calories": 200,
      "proteinGrams": 5,
      "fatGrams": 10,
      "carbsGrams": 20
    },
    "aliases": [],
    "timesLogged": 0,
    "createdAt": "2026-07-16T12:00:00.000Z"
  }
}

Seed food history: 1 for seed-c-del-0-avocado at 2026-07-17T20:00:00.000Z

{
  "type": "food_history",
  "foodItemId": "seed-c-del-0-avocado",
  "quantity": 1,
  "loggedAt": "2026-07-17T20:00:00.000Z"
}

snapshot captured 2026-08-02T21:55:47.799Z

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 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 delete the entry"Remove yesterday's ice cream." (difficulty —)0.2s

Verdict Expected DELETE — should delete the entry. PASS: Deleted/removed the requested food with database removal proof.

Why verdict Deleted/removed the requested food with database removal proof.

My override

Things I think are wrong

Use this when the report passed something that should have failed.

Comprehension

Picked wrong food Wrong quantity Should have asked (over-logged) Shouldn't have asked (over-asked) Wrong action entirely

Execution

Didn't save to DB Wrong data saved No voice/TTS Card missing/wrong No chat

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

Use this when the report failed something that should have passed.

Actually right

Food/action was right Quantity/serving was right Asking was right Not asking was right Answer was right No app data row was expected App data row was right Voice/card/chat was acceptable

Report/grader issue

Report expected the wrong result Evidence was enough to judge Failure reason was not valid

Other thing actually right (describe below)

Pick every reason you think applies. Multiple boxes 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 Deleted ice cream.

2 · Card shown Deleted ice cream.

3 · App data rows written deleted food_log_entry:

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seed food: ice cream

{
  "type": "food_item",
  "foodItem": {
    "id": "seed-c-del-1-ice-cream",
    "name": "ice cream",
    "brand": null,
    "source": "manual",
    "servingLabel": "serving",
    "servingQuantity": 1,
    "servingUnit": "serving",
    "macrosPerServing": {
      "calories": 200,
      "proteinGrams": 5,
      "fatGrams": 10,
      "carbsGrams": 20
    },
    "aliases": [],
    "timesLogged": 0,
    "createdAt": "2026-07-16T12:00:00.000Z"
  }
}

Seed food history: 1 for seed-c-del-1-ice-cream at 2026-07-17T20:00:00.000Z

{
  "type": "food_history",
  "foodItemId": "seed-c-del-1-ice-cream",
  "quantity": 1,
  "loggedAt": "2026-07-17T20:00:00.000Z"
}

snapshot captured 2026-08-02T21:56:10.917Z

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 "Vanilla ice cream" at 90% confidence.
Matched your past food logs to "ice cream" 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 delete the entry"Delete the leftover pizza entry." (difficulty —)0.2s

Verdict Expected DELETE — should delete the entry. PASS: Deleted/removed the requested food with database removal proof.

Why verdict Deleted/removed the requested food with database removal proof.

My override

Things I think are wrong

Use this when the report passed something that should have failed.

Comprehension

Picked wrong food Wrong quantity Should have asked (over-logged) Shouldn't have asked (over-asked) Wrong action entirely

Execution

Didn't save to DB Wrong data saved No voice/TTS Card missing/wrong No chat

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

Use this when the report failed something that should have passed.

Actually right

Food/action was right Quantity/serving was right Asking was right Not asking was right Answer was right No app data row was expected App data row was right Voice/card/chat was acceptable

Report/grader issue

Report expected the wrong result Evidence was enough to judge Failure reason was not valid

Other thing actually right (describe below)

Pick every reason you think applies. Multiple boxes 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 Deleted pizza.

2 · Card shown Deleted pizza.

3 · App data rows written deleted food_log_entry:

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seed food: pizza

{
  "type": "food_item",
  "foodItem": {
    "id": "seed-c-del-2-pizza",
    "name": "pizza",
    "brand": null,
    "source": "manual",
    "servingLabel": "serving",
    "servingQuantity": 1,
    "servingUnit": "serving",
    "macrosPerServing": {
      "calories": 200,
      "proteinGrams": 5,
      "fatGrams": 10,
      "carbsGrams": 20
    },
    "aliases": [],
    "timesLogged": 0,
    "createdAt": "2026-07-16T12:00:00.000Z"
  }
}

Seed food history: 1 for seed-c-del-2-pizza at 2026-07-17T20:00:00.000Z

{
  "type": "food_history",
  "foodItemId": "seed-c-del-2-pizza",
  "quantity": 1,
  "loggedAt": "2026-07-17T20:00:00.000Z"
}

snapshot captured 2026-08-02T21:56:22.616Z

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 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)

FAILshould delete the entry"Take out the beer from last night." (difficulty —)2.3s

Verdict Expected DELETE — should delete the entry. FAIL: Did not delete (not understood / no removal).

Why verdict Did not delete (not understood / no removal).

My override

Things I think are wrong

Use this when the report passed something that should have failed.

Comprehension

Picked wrong food Wrong quantity Should have asked (over-logged) Shouldn't have asked (over-asked) Wrong action entirely

Execution

Didn't save to DB Wrong data saved No voice/TTS Card missing/wrong No chat

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

Use this when the report failed something that should have passed.

Actually right

Food/action was right Quantity/serving was right Asking was right Not asking was right Answer was right No app data row was expected App data row was right Voice/card/chat was acceptable

Report/grader issue

Report expected the wrong result Evidence was enough to judge Failure reason was not valid

Other thing actually right (describe below)

Pick every reason you think applies. Multiple boxes are allowed because one utterance can be wrong in more than one way. Use the note below for "Other" or extra detail.

Timing 2.3s

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:

Seed food: beer

{
  "type": "food_item",
  "foodItem": {
    "id": "seed-c-del-3-beer",
    "name": "beer",
    "brand": null,
    "source": "manual",
    "servingLabel": "serving",
    "servingQuantity": 1,
    "servingUnit": "serving",
    "macrosPerServing": {
      "calories": 200,
      "proteinGrams": 5,
      "fatGrams": 10,
      "carbsGrams": 20
    },
    "aliases": [],
    "timesLogged": 0,
    "createdAt": "2026-07-16T12:00:00.000Z"
  }
}

Seed food history: 1 for seed-c-del-3-beer at 2026-07-17T20:00:00.000Z

{
  "type": "food_history",
  "foodItemId": "seed-c-del-3-beer",
  "quantity": 1,
  "loggedAt": "2026-07-17T20:00:00.000Z"
}

snapshot captured 2026-08-02T21:56:29.070Z

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)

FAILshould delete the entry"Remove the cookie log from earlier this week." (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:

Seed food: cookie

{
  "type": "food_item",
  "foodItem": {
    "id": "seed-c-del-4-cookie",
    "name": "cookie",
    "brand": null,
    "source": "manual",
    "servingLabel": "serving",
    "servingQuantity": 1,
    "servingUnit": "serving",
    "macrosPerServing": {
      "calories": 200,
      "proteinGrams": 5,
      "fatGrams": 10,
      "carbsGrams": 20
    },
    "aliases": [],
    "timesLogged": 0,
    "createdAt": "2026-07-16T12:00:00.000Z"
  }
}

Seed food history: 1 for seed-c-del-4-cookie at 2026-07-17T20:00:00.000Z

{
  "type": "food_history",
  "foodItemId": "seed-c-del-4-cookie",
  "quantity": 1,
  "loggedAt": "2026-07-17T20:00:00.000Z"
}

snapshot captured 2026-08-02T21:56:43.208Z

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 delete the entry"Delete the fries I shouldn't have logged." (difficulty —)0.3s

Verdict Expected DELETE — should delete the entry. PASS: Deleted/removed the requested food with database removal proof.

Why verdict Deleted/removed the requested food with database removal proof.

My override

Things I think are wrong

Use this when the report passed something that should have failed.

Comprehension

Picked wrong food Wrong quantity Should have asked (over-logged) Shouldn't have asked (over-asked) Wrong action entirely

Execution

Didn't save to DB Wrong data saved No voice/TTS Card missing/wrong No chat

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

Use this when the report failed something that should have passed.

Actually right

Food/action was right Quantity/serving was right Asking was right Not asking was right Answer was right No app data row was expected App data row was right Voice/card/chat was acceptable

Report/grader issue

Report expected the wrong result Evidence was enough to judge Failure reason was not valid

Other thing actually right (describe below)

Pick every reason you think applies. Multiple boxes 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 fries.

2 · Card shown Deleted fries.

3 · App data rows written deleted food_log_entry:

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seed food: fries

{
  "type": "food_item",
  "foodItem": {
    "id": "seed-c-del-5-fries",
    "name": "fries",
    "brand": null,
    "source": "manual",
    "servingLabel": "serving",
    "servingQuantity": 1,
    "servingUnit": "serving",
    "macrosPerServing": {
      "calories": 200,
      "proteinGrams": 5,
      "fatGrams": 10,
      "carbsGrams": 20
    },
    "aliases": [],
    "timesLogged": 0,
    "createdAt": "2026-07-16T12:00:00.000Z"
  }
}

Seed food history: 1 for seed-c-del-5-fries at 2026-07-17T20:00:00.000Z

{
  "type": "food_history",
  "foodItemId": "seed-c-del-5-fries",
  "quantity": 1,
  "loggedAt": "2026-07-17T20:00:00.000Z"
}

snapshot captured 2026-08-02T21:57:01.316Z

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)

FAILshould update the entry"Change the sequence banana quantity to two." (difficulty —)0.1s

Verdict Expected UPDATE — should update the entry. FAIL: Reported could-not-confirm (write-confirmation false negative).

Why verdict Reported could-not-confirm (write-confirmation false negative).

My override

Things I think are wrong

Use this when the report passed something that should have failed.

Comprehension

Picked wrong food Wrong quantity Should have asked (over-logged) Shouldn't have asked (over-asked) Wrong action entirely

Execution

Didn't save to DB Wrong data saved No voice/TTS Card missing/wrong No chat

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

Use this when the report failed something that should have passed.

Actually right

Food/action was right Quantity/serving was right Asking was right Not asking was right Answer was right No app data row was expected App data row was right Voice/card/chat was acceptable

Report/grader issue

Report expected the wrong result Evidence was enough to judge Failure reason was not valid

Other thing actually right (describe below)

Pick every reason you think applies. Multiple boxes are allowed because one utterance can be wrong in more than one way. Use the note below for "Other" or extra detail.

Timing 0.1s

1 · TTS said 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: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T21:57:05.805Z

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 "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.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 update the entry"Actually make the Quest bar two bars." (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 Quest Chocolate Brownie Protein Bar to 2 bars.

2 · Card shown Updated Quest Chocolate Brownie Protein Bar to 2 bars.

3 · App data rows written updated food_log_entry: Quest Chocolate Brownie Protein Bar ×2 (bar) 380 cal · 40g P · 42g C · 14g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T21:57:17.408Z

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 Brownie 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)

FAILshould update the entry"Update the oatmeal to one and a half cups." (difficulty —)0.1s

Verdict Expected UPDATE — should update the entry. FAIL: Reported could-not-confirm (write-confirmation false negative).

Why verdict Reported could-not-confirm (write-confirmation false negative).

My override

Things I think are wrong

Use this when the report passed something that should have failed.

Comprehension

Picked wrong food Wrong quantity Should have asked (over-logged) Shouldn't have asked (over-asked) Wrong action entirely

Execution

Didn't save to DB Wrong data saved No voice/TTS Card missing/wrong No chat

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

Use this when the report failed something that should have passed.

Actually right

Food/action was right Quantity/serving was right Asking was right Not asking was right Answer was right No app data row was expected App data row was right Voice/card/chat was acceptable

Report/grader issue

Report expected the wrong result Evidence was enough to judge Failure reason was not valid

Other thing actually right (describe below)

Pick every reason you think applies. Multiple boxes are allowed because one utterance can be wrong in more than one way. Use the note below for "Other" or extra detail.

Timing 0.1s

1 · TTS said 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: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T21:57:28.713Z

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 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)

FAILshould update the entry"Change the eggs to three." (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: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T21:57:39.936Z

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 "egg" at 90% confidence.
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.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"Make the blueberries a half cup." (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: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T21:57:51.227Z

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 "blueberries" at 90% 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.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 update the entry"Update the chicken to six ounces." (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 Chicken breast to 6 oz.

2 · Card shown Updated Chicken breast to 6 oz.

3 · App data rows written updated food_log_entry: Chicken breast ×1.7009699999999999 (100 g) 281 cal · 52.7g P · 0g C · 6.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-02T21:58:02.811Z

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 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)

FAILshould update the entry"Change peanut butter to two tablespoons." (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: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T21:58:14.044Z

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 "peanut butter" at 90% confidence.
Matched the common-food list to "Peanut butter" 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 update the entry"Actually the milk was skim, not two percent." (difficulty —)3.2s

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.2s

1 · TTS said Updated to skim milk.

2 · Card shown Updated the food entry from "2 Percent Milk" to "skim milk".

3 · App data rows written updated food_log_entry: 2% milk ×1 (100 g) 50 cal · 3.3g P · 4.8g C · 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-02T21:58:28.364Z

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"Actually that was vanilla, not chocolate." (difficulty —)1.1s

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 1.1s

1 · TTS said Updated to vanilla.

2 · Card shown Updated the food entry from "Plain Greek yogurt" to "vanilla".

3 · App data rows written updated food_log_entry: TWO GOOD Vanilla Lowfat Greek Yogurt, Vanilla ×1 (one) 90 cal · 13g P · 4g C · 2g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seed food: chocolate item

{
  "type": "food_item",
  "foodItem": {
    "id": "seed-c-edit-0-chocolate-item",
    "name": "chocolate item",
    "brand": null,
    "source": "manual",
    "servingLabel": "serving",
    "servingQuantity": 1,
    "servingUnit": "serving",
    "macrosPerServing": {
      "calories": 180,
      "proteinGrams": 8,
      "fatGrams": 6,
      "carbsGrams": 18
    },
    "aliases": [],
    "timesLogged": 0,
    "createdAt": "2026-07-16T12:00:00.000Z"
  }
}

Seed food history: 1 for seed-c-edit-0-chocolate-item at 2026-07-18T10:00:00.000Z

{
  "type": "food_history",
  "foodItemId": "seed-c-edit-0-chocolate-item",
  "quantity": 1,
  "loggedAt": "2026-07-18T10:00:00.000Z"
}

snapshot captured 2026-08-02T21:58:40.704Z

6 · Why this food No food-decision explanation was captured for this path.

7 · Lookup method No lookup method was captured for this path.

8 · Candidates → decider no candidate list captured (this path did not run DB resolution — e.g. provisional branded log)

FAILshould update the entry"Change the portion to two cups." (difficulty —)0.1s

Verdict Expected UPDATE — should update the entry. FAIL: Reported could-not-confirm (write-confirmation false negative).

Why verdict Reported could-not-confirm (write-confirmation false negative).

My override

Things I think are wrong

Use this when the report passed something that should have failed.

Comprehension

Picked wrong food Wrong quantity Should have asked (over-logged) Shouldn't have asked (over-asked) Wrong action entirely

Execution

Didn't save to DB Wrong data saved No voice/TTS Card missing/wrong No chat

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

Use this when the report failed something that should have passed.

Actually right

Food/action was right Quantity/serving was right Asking was right Not asking was right Answer was right No app data row was expected App data row was right Voice/card/chat was acceptable

Report/grader issue

Report expected the wrong result Evidence was enough to judge Failure reason was not valid

Other thing actually right (describe below)

Pick every reason you think applies. Multiple boxes are allowed because one utterance can be wrong in more than one way. Use the note below for "Other" or extra detail.

Timing 0.1s

1 · TTS said 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:

Seed food: rice

{
  "type": "food_item",
  "foodItem": {
    "id": "seed-c-edit-1-rice",
    "name": "rice",
    "brand": null,
    "source": "manual",
    "servingLabel": "serving",
    "servingQuantity": 1,
    "servingUnit": "serving",
    "macrosPerServing": {
      "calories": 180,
      "proteinGrams": 8,
      "fatGrams": 6,
      "carbsGrams": 18
    },
    "aliases": [],
    "timesLogged": 0,
    "createdAt": "2026-07-16T12:00:00.000Z"
  }
}

Seed food history: 1 for seed-c-edit-1-rice at 2026-07-18T10:00:00.000Z

{
  "type": "food_history",
  "foodItemId": "seed-c-edit-1-rice",
  "quantity": 1,
  "loggedAt": "2026-07-18T10:00:00.000Z"
}

snapshot captured 2026-08-02T21:58:52.030Z

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)

FAILshould update the entry"Make it half a cup instead." (difficulty —)0.1s

Verdict Expected UPDATE — should update the entry. FAIL: Reported could-not-confirm (write-confirmation false negative).

Why verdict Reported could-not-confirm (write-confirmation false negative).

My override

Things I think are wrong

Use this when the report passed something that should have failed.

Comprehension

Picked wrong food Wrong quantity Should have asked (over-logged) Shouldn't have asked (over-asked) Wrong action entirely

Execution

Didn't save to DB Wrong data saved No voice/TTS Card missing/wrong No chat

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

Use this when the report failed something that should have passed.

Actually right

Food/action was right Quantity/serving was right Asking was right Not asking was right Answer was right No app data row was expected App data row was right Voice/card/chat was acceptable

Report/grader issue

Report expected the wrong result Evidence was enough to judge Failure reason was not valid

Other thing actually right (describe below)

Pick every reason you think applies. Multiple boxes are allowed because one utterance can be wrong in more than one way. Use the note below for "Other" or extra detail.

Timing 0.1s

1 · TTS said 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:

Seed food: oatmeal

{
  "type": "food_item",
  "foodItem": {
    "id": "seed-c-edit-2-oatmeal",
    "name": "oatmeal",
    "brand": null,
    "source": "manual",
    "servingLabel": "serving",
    "servingQuantity": 1,
    "servingUnit": "serving",
    "macrosPerServing": {
      "calories": 180,
      "proteinGrams": 8,
      "fatGrams": 6,
      "carbsGrams": 18
    },
    "aliases": [],
    "timesLogged": 0,
    "createdAt": "2026-07-16T12:00:00.000Z"
  }
}

Seed food history: 1 for seed-c-edit-2-oatmeal at 2026-07-18T10:00:00.000Z

{
  "type": "food_history",
  "foodItemId": "seed-c-edit-2-oatmeal",
  "quantity": 1,
  "loggedAt": "2026-07-18T10:00:00.000Z"
}

snapshot captured 2026-08-02T21:59:03.272Z

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)

FAILshould update the entry"Update that to six ounces." (difficulty —)0.1s

Verdict Expected UPDATE — should update the entry. FAIL: Reported could-not-confirm (write-confirmation false negative).

Why verdict Reported could-not-confirm (write-confirmation false negative).

My override

Things I think are wrong

Use this when the report passed something that should have failed.

Comprehension

Picked wrong food Wrong quantity Should have asked (over-logged) Shouldn't have asked (over-asked) Wrong action entirely

Execution

Didn't save to DB Wrong data saved No voice/TTS Card missing/wrong No chat

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

Use this when the report failed something that should have passed.

Actually right

Food/action was right Quantity/serving was right Asking was right Not asking was right Answer was right No app data row was expected App data row was right Voice/card/chat was acceptable

Report/grader issue

Report expected the wrong result Evidence was enough to judge Failure reason was not valid

Other thing actually right (describe below)

Pick every reason you think applies. Multiple boxes are allowed because one utterance can be wrong in more than one way. Use the note below for "Other" or extra detail.

Timing 0.1s

1 · TTS said 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:

Seed food: chicken

{
  "type": "food_item",
  "foodItem": {
    "id": "seed-c-edit-3-chicken",
    "name": "chicken",
    "brand": null,
    "source": "manual",
    "servingLabel": "serving",
    "servingQuantity": 1,
    "servingUnit": "serving",
    "macrosPerServing": {
      "calories": 180,
      "proteinGrams": 8,
      "fatGrams": 6,
      "carbsGrams": 18
    },
    "aliases": [],
    "timesLogged": 0,
    "createdAt": "2026-07-16T12:00:00.000Z"
  }
}

Seed food history: 1 for seed-c-edit-3-chicken at 2026-07-18T10:00:00.000Z

{
  "type": "food_history",
  "foodItemId": "seed-c-edit-3-chicken",
  "quantity": 1,
  "loggedAt": "2026-07-18T10:00:00.000Z"
}

snapshot captured 2026-08-02T21:59:14.422Z

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 update the entry"Actually it was almond butter, not peanut butter." (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 butter.

2 · Card shown Updated the food entry from "TWO GOOD Vanilla Lowfat Greek Yogurt, Vanilla" to "almond butter".

3 · App data rows written updated food_log_entry: Almond Butter ×1 (1 tablespoon) 103 cal · 3.3g P · 3.4g C · 8.4g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seed food: peanut butter

{
  "type": "food_item",
  "foodItem": {
    "id": "seed-c-edit-4-peanut-butter",
    "name": "peanut butter",
    "brand": null,
    "source": "manual",
    "servingLabel": "serving",
    "servingQuantity": 1,
    "servingUnit": "serving",
    "macrosPerServing": {
      "calories": 180,
      "proteinGrams": 8,
      "fatGrams": 6,
      "carbsGrams": 18
    },
    "aliases": [],
    "timesLogged": 0,
    "createdAt": "2026-07-16T12:00:00.000Z"
  }
}

Seed food history: 1 for seed-c-edit-4-peanut-butter at 2026-07-18T10:00:00.000Z

{
  "type": "food_history",
  "foodItemId": "seed-c-edit-4-peanut-butter",
  "quantity": 1,
  "loggedAt": "2026-07-18T10:00:00.000Z"
}

snapshot captured 2026-08-02T21:59:26.380Z

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 banana to a large." (difficulty —)6.0s

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 6.0s

1 · TTS said Updated Banana to 1 large.

2 · Card shown Updated Banana to 1 large.

3 · App data rows written updated food_log_entry: Banana ×1 (1 large banana) 121 cal · 1.5g P · 31.3g C · 0.4g F

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state:

Seed food: banana

{
  "type": "food_item",
  "foodItem": {
    "id": "seed-c-edit-5-banana",
    "name": "banana",
    "brand": null,
    "source": "manual",
    "servingLabel": "serving",
    "servingQuantity": 1,
    "servingUnit": "serving",
    "macrosPerServing": {
      "calories": 180,
      "proteinGrams": 8,
      "fatGrams": 6,
      "carbsGrams": 18
    },
    "aliases": [],
    "timesLogged": 0,
    "createdAt": "2026-07-16T12:00:00.000Z"
  }
}

Seed food history: 1 for seed-c-edit-5-banana at 2026-07-18T10:00:00.000Z

{
  "type": "food_history",
  "foodItemId": "seed-c-edit-5-banana",
  "quantity": 1,
  "loggedAt": "2026-07-18T10:00:00.000Z"
}

snapshot captured 2026-08-02T21:59:43.360Z

6 · Why this food No food-decision explanation was captured for this path.

7 · Lookup method No lookup method was captured for this path.

8 · Candidates → decider no candidate list captured (this path did not run DB resolution — e.g. provisional branded log)

UNVERIFIEDunclassifiedshould answer the query"How much protein have I had today?" (difficulty —)0.1s

Verdict Expected QUERY — should answer the query. UNVERIFIED: answer key has no expected values

Why verdict answer key has no expected values

My override

Things I think are wrong

Use this when the report passed something that should have failed.

Comprehension

Picked wrong food Wrong quantity Should have asked (over-logged) Shouldn't have asked (over-asked) Wrong action entirely

Execution

Didn't save to DB Wrong data saved No voice/TTS Card missing/wrong No chat

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

Use this when the report failed something that should have passed.

Actually right

Food/action was right Quantity/serving was right Asking was right Not asking was right Answer was right No app data row was expected App data row was right Voice/card/chat was acceptable

Report/grader issue

Report expected the wrong result Evidence was enough to judge Failure reason was not valid

Other thing actually right (describe below)

Pick every reason you think applies. Multiple boxes are allowed because one utterance can be wrong in more than one way. Use the note below for "Other" or extra detail.

Timing 0.1s

1 · TTS said You logged 1113.6 grams of protein today.

2 · Card shown You logged 1113.6 grams of protein today.

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T21:59:54.582Z

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 answer the query"How many calories so far?" (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-02T22:00:17.335Z

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)

UNVERIFIEDunclassifiedshould answer the query"What did I eat yesterday?" (difficulty —)0.0s

Verdict Expected QUERY — should answer the query. UNVERIFIED: answer key has no expected values

Why verdict answer key has no expected values

My override

Things I think are wrong

Use this when the report passed something that should have failed.

Comprehension

Picked wrong food Wrong quantity Should have asked (over-logged) Shouldn't have asked (over-asked) Wrong action entirely

Execution

Didn't save to DB Wrong data saved No voice/TTS Card missing/wrong No chat

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

Use this when the report failed something that should have passed.

Actually right

Food/action was right Quantity/serving was right Asking was right Not asking was right Answer was right No app data row was expected App data row was right Voice/card/chat was acceptable

Report/grader issue

Report expected the wrong result Evidence was enough to judge Failure reason was not valid

Other thing actually right (describe below)

Pick every reason you think applies. Multiple boxes are allowed because one utterance can be wrong in more than one way. Use the note below for "Other" or extra detail.

Timing 0.0s

1 · TTS said I do not see any food logged yesterday.

2 · Card shown I do not see any food logged yesterday.

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T22:00:28.548Z

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)

UNVERIFIEDunclassifiedshould answer the query"How much fat have I logged today?" (difficulty —)0.1s

Verdict Expected QUERY — should answer the query. UNVERIFIED: answer key has no expected values

Why verdict answer key has no expected values

My override

Things I think are wrong

Use this when the report passed something that should have failed.

Comprehension

Picked wrong food Wrong quantity Should have asked (over-logged) Shouldn't have asked (over-asked) Wrong action entirely

Execution

Didn't save to DB Wrong data saved No voice/TTS Card missing/wrong No chat

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

Use this when the report failed something that should have passed.

Actually right

Food/action was right Quantity/serving was right Asking was right Not asking was right Answer was right No app data row was expected App data row was right Voice/card/chat was acceptable

Report/grader issue

Report expected the wrong result Evidence was enough to judge Failure reason was not valid

Other thing actually right (describe below)

Pick every reason you think applies. Multiple boxes are allowed because one utterance can be wrong in more than one way. Use the note below for "Other" or extra detail.

Timing 0.1s

1 · TTS said You logged 518.5 grams of fat today.

2 · Card shown You logged 518.5 grams of fat today.

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T22:00:39.738Z

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 answer the query"What's my remaining calorie budget?" (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 13785 calories over today's 2200 calorie budget (15985 logged).

2 · Card shown You are about 13785 calories over today's 2200 calorie budget (15985 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-02T22:00:50.976Z

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 answer the query"Did I log breakfast yet?" (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 do not see breakfast logged today.

2 · Card shown I do not see breakfast logged today.

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T22:01:05.331Z

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 "breakfast portion" 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)

UNVERIFIEDunclassifiedshould answer the query"How many carbs today?" (difficulty —)0.1s

Verdict Expected QUERY — should answer the query. UNVERIFIED: answer key has no expected values

Why verdict answer key has no expected values

My override

Things I think are wrong

Use this when the report passed something that should have failed.

Comprehension

Picked wrong food Wrong quantity Should have asked (over-logged) Shouldn't have asked (over-asked) Wrong action entirely

Execution

Didn't save to DB Wrong data saved No voice/TTS Card missing/wrong No chat

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

Use this when the report failed something that should have passed.

Actually right

Food/action was right Quantity/serving was right Asking was right Not asking was right Answer was right No app data row was expected App data row was right Voice/card/chat was acceptable

Report/grader issue

Report expected the wrong result Evidence was enough to judge Failure reason was not valid

Other thing actually right (describe below)

Pick every reason you think applies. Multiple boxes are allowed because one utterance can be wrong in more than one way. Use the note below for "Other" or extra detail.

Timing 0.1s

1 · TTS said You logged 1815.4 grams of carbs today.

2 · Card shown You logged 1815.4 grams of carbs today.

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T22:01:18.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.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"What did I eat after my workout?" (difficulty —)2.0s

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 2.0s

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: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T22:01:29.624Z

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)

UNVERIFIEDunclassifiedshould answer the query"Show me today's food log." (difficulty —)0.1s

Verdict Expected QUERY — should answer the query. UNVERIFIED: answer key has no expected values

Why verdict answer key has no expected values

My override

Things I think are wrong

Use this when the report passed something that should have failed.

Comprehension

Picked wrong food Wrong quantity Should have asked (over-logged) Shouldn't have asked (over-asked) Wrong action entirely

Execution

Didn't save to DB Wrong data saved No voice/TTS Card missing/wrong No chat

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

Use this when the report failed something that should have passed.

Actually right

Food/action was right Quantity/serving was right Asking was right Not asking was right Answer was right No app data row was expected App data row was right Voice/card/chat was acceptable

Report/grader issue

Report expected the wrong result Evidence was enough to judge Failure reason was not valid

Other thing actually right (describe below)

Pick every reason you think applies. Multiple boxes are allowed because one utterance can be wrong in more than one way. Use the note below for "Other" or extra detail.

Timing 0.1s

1 · TTS said 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-02T22:01:40.893Z

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)

UNVERIFIEDunclassifiedshould answer the query"Am I over my protein 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 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-02T22:01:52.177Z

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)

UNVERIFIEDunclassifiedshould answer the query"How many calories in the banana I just logged?" (difficulty —)0.1s

Verdict Expected QUERY — should answer the query. UNVERIFIED: answer key has no expected values

Why verdict answer key has no expected values

My override

Things I think are wrong

Use this when the report passed something that should have failed.

Comprehension

Picked wrong food Wrong quantity Should have asked (over-logged) Shouldn't have asked (over-asked) Wrong action entirely

Execution

Didn't save to DB Wrong data saved No voice/TTS Card missing/wrong No chat

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

Use this when the report failed something that should have passed.

Actually right

Food/action was right Quantity/serving was right Asking was right Not asking was right Answer was right No app data row was expected App data row was right Voice/card/chat was acceptable

Report/grader issue

Report expected the wrong result Evidence was enough to judge Failure reason was not valid

Other thing actually right (describe below)

Pick every reason you think applies. Multiple boxes are allowed because one utterance can be wrong in more than one way. Use the note below for "Other" or extra detail.

Timing 0.1s

1 · TTS said Banana has about 105 calories per 118 g.

2 · Card shown Banana has about 105 calories per 118 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-02T22:02:03.445Z

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 "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.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"What was my last meal?" (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 Your last food entry today was 1 1 tablespoon Almond Butter.

2 · Card shown Your last food entry today was 1 1 tablespoon Almond Butter.

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T22:02:14.721Z

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)

UNVERIFIEDunclassifiedshould answer the query"How much water have I logged?" (difficulty —)0.1s

Verdict Expected QUERY — should answer the query. UNVERIFIED: answer key has no expected values

Why verdict answer key has no expected values

My override

Things I think are wrong

Use this when the report passed something that should have failed.

Comprehension

Picked wrong food Wrong quantity Should have asked (over-logged) Shouldn't have asked (over-asked) Wrong action entirely

Execution

Didn't save to DB Wrong data saved No voice/TTS Card missing/wrong No chat

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

Use this when the report failed something that should have passed.

Actually right

Food/action was right Quantity/serving was right Asking was right Not asking was right Answer was right No app data row was expected App data row was right Voice/card/chat was acceptable

Report/grader issue

Report expected the wrong result Evidence was enough to judge Failure reason was not valid

Other thing actually right (describe below)

Pick every reason you think applies. Multiple boxes are allowed because one utterance can be wrong in more than one way. Use the note below for "Other" or extra detail.

Timing 0.1s

1 · TTS said Today you logged 1 240 g Water (0 calories).

2 · Card shown Today you logged 1 240 g Water (0 calories).

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T22:02:26.033Z

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 "water" at 90% confidence.
Matched the common-food list to "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 1.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"Calories left for dinner?" (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 13785 calories over today's 2200 calorie budget (15985 logged).

2 · Card shown You are about 13785 calories over today's 2200 calorie budget (15985 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-02T22:02:37.297Z

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)

UNVERIFIEDunclassifiedshould answer the query"Did I already log my usual yogurt?" (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 Yes. Today you logged 1 200 g Nonfat Greek yogurt, 1 cup Codex Test Dairy Vanilla Greek Yogurt Cup, 1 cup Chobani Zero Sugar Vanilla Yogurt, 1 100 g Plain Greek yogurt, 1 100 g Plain Greek yogurt, 1 serving Yogurt Bowl, 1 100 g Plain Greek yogurt.

2 · Card shown Yes. Today you logged 1 200 g Nonfat Greek yogurt, 1 cup Codex Test Dairy Vanilla Greek Yogurt Cup, 1 cup Chobani Zero Sugar Vanilla Yogurt, 1 100 g Plain Greek yogurt, 1 100 g Plain Greek yogurt, 1 serving Yogurt Bowl, 1 100 g Plain Greek yogurt.

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T22:02:48.628Z

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 yogurt" at 96% confidence.
Matched the common-food list to "Plain Greek yogurt" 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)

UNVERIFIEDunclassifiedshould answer the query"What's my average protein this week?" (difficulty —)0.1s

Verdict Expected QUERY — should answer the query. UNVERIFIED: answer key has no expected values

Why verdict answer key has no expected values

My override

Things I think are wrong

Use this when the report passed something that should have failed.

Comprehension

Picked wrong food Wrong quantity Should have asked (over-logged) Shouldn't have asked (over-asked) Wrong action entirely

Execution

Didn't save to DB Wrong data saved No voice/TTS Card missing/wrong No chat

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

Use this when the report failed something that should have passed.

Actually right

Food/action was right Quantity/serving was right Asking was right Not asking was right Answer was right No app data row was expected App data row was right Voice/card/chat was acceptable

Report/grader issue

Report expected the wrong result Evidence was enough to judge Failure reason was not valid

Other thing actually right (describe below)

Pick every reason you think applies. Multiple boxes are allowed because one utterance can be wrong in more than one way. Use the note below for "Other" or extra detail.

Timing 0.1s

1 · TTS said 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-02T22:02:59.844Z

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 answer the query"How many entries do I have today?" (difficulty —)0.1s

Verdict Expected QUERY — should answer the query. UNVERIFIED: answer key has no expected values

Why verdict answer key has no expected values

My override

Things I think are wrong

Use this when the report passed something that should have failed.

Comprehension

Picked wrong food Wrong quantity Should have asked (over-logged) Shouldn't have asked (over-asked) Wrong action entirely

Execution

Didn't save to DB Wrong data saved No voice/TTS Card missing/wrong No chat

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

Use this when the report failed something that should have passed.

Actually right

Food/action was right Quantity/serving was right Asking was right Not asking was right Answer was right No app data row was expected App data row was right Voice/card/chat was acceptable

Report/grader issue

Report expected the wrong result Evidence was enough to judge Failure reason was not valid

Other thing actually right (describe below)

Pick every reason you think applies. Multiple boxes are allowed because one utterance can be wrong in more than one way. Use the note below for "Other" or extra detail.

Timing 0.1s

1 · TTS said You have 106 food entries logged today.

2 · Card shown You have 106 food entries logged today.

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T22:03:11.144Z

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 answer the query"What did I snack on earlier?" (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 do not see any snacks logged today.

2 · Card shown I do not see any snacks logged today.

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T22:03:22.452Z

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 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-02T22:03:33.680Z

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.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 nutrition 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-02T22:03:45.036Z

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 apply the setting"Set my calorie goal to twenty two hundred." (difficulty —)0.1s

Verdict Expected SETTINGS — should apply the setting. FAIL: Reported could-not-confirm (write-confirmation false negative).

Why verdict Reported could-not-confirm (write-confirmation false negative).

My override

Things I think are wrong

Use this when the report passed something that should have failed.

Comprehension

Picked wrong food Wrong quantity Should have asked (over-logged) Shouldn't have asked (over-asked) Wrong action entirely

Execution

Didn't save to DB Wrong data saved No voice/TTS Card missing/wrong No chat

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

Use this when the report failed something that should have passed.

Actually right

Food/action was right Quantity/serving was right Asking was right Not asking was right Answer was right No app data row was expected App data row was right Voice/card/chat was acceptable

Report/grader issue

Report expected the wrong result Evidence was enough to judge Failure reason was not valid

Other thing actually right (describe below)

Pick every reason you think applies. Multiple boxes are allowed because one utterance can be wrong in more than one way. Use the note below for "Other" or extra detail.

Timing 0.1s

1 · TTS said I'm not sure how to help with that yet. Try asking me to log food, a workout, a note, or a to-do.

2 · Card shown I'm not sure how to help with that yet. Try asking me to log food, a workout, a note, or a to-do.

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

No DB snapshot captured for this utterance; the report cannot prove whether yesterday/personal data existed.

snapshot captured 2026-08-02T22:03:56.424Z

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 log the entry"I had a bowl of plain cooked oatmeal." (difficulty —)8.0s

Verdict Expected LOG — should log the entry. FAIL: WRITE-TRUTH FAIL — WRONG/MISSING item "estimated three-quarters to one cup" — no saved row with matching identity (rows: Cooked oatmeal, Cooked oatmeal)

Why verdict WRITE-TRUTH FAIL — WRONG/MISSING item "estimated three-quarters to one cup" — no saved row with matching identity (rows: Cooked oatmeal, Cooked oatmeal)

My override

Things I think are wrong

Use this when the report passed something that should have failed.

Comprehension

Picked wrong food Wrong quantity Should have asked (over-logged) Shouldn't have asked (over-asked) Wrong action entirely

Execution

Didn't save to DB Wrong data saved No voice/TTS Card missing/wrong No chat

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

Use this when the report failed something that should have passed.

Actually right

Food/action was right Quantity/serving was right Asking was right Not asking was right Answer was right No app data row was expected App data row was right Voice/card/chat was acceptable

Report/grader issue

Report expected the wrong result Evidence was enough to judge Failure reason was not valid

Other thing actually right (describe below)

Pick every reason you think applies. Multiple boxes are allowed because one utterance can be wrong in more than one way. Use the note below for "Other" or extra detail.

Timing 8.0s

1 · TTS said How much oatmeal should I use? I did not log it yet because bowl size can change the nutrition.

2 · Card shown How much oatmeal should I use? I did not log it yet because bowl size 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-02T22:04:27.183Z

6 · Why this food No food-decision explanation was captured for this path.

7 · Lookup method No lookup method was captured for this path.

8 · Candidates → decider no candidate list captured (this path did not run DB resolution — e.g. provisional branded log)

Why the fails happened — comprehension vs execution vs cosmetic

Handled correctly? — by expected action

Accuracy by difficulty

Clarification follow-ups — scored separately

Cosmetic only

System / infra

Latency

Filter — controls the list below

Per-utterance detail