query-frozen-A-14385762-c56-20260802

Supposed to	N	Correct	Wrong	Unverified
▸ QUERY — answer the query	72	68 (94%)	4 (6%)	0 (0%)
4 handled wrong — click one to jump to its full detail below "What did I eat yesterday?" answer did not state expected numeric value(s): mealCount "How many breakfast entries did I log today?" answer did not state expected numeric value(s): entryCount "How many snack entries did I log today?" answer did not state expected numeric value(s): entryCount "What was my average dinner calorie total for the six completed days?" answer did not state expected numeric value(s): averageCalories
▸ NAVIGATE — navigate	3	2 (67%)	1 (33%)	0 (0%)
1 handled wrong — click one to jump to its full detail below "Go back to today in my food diary." Did not navigate — misrouted into a food/workout clarification or dead-ended.
▸ OTHER — handle appropriately	3	2 (67%)	1 (33%)	0 (0%)
1 handled wrong — click one to jump to its full detail below "Good to know." OTHER conversation_acknowledgement — response was not an acknowledgement or was too long
Total	78	72 (92%)	6	0

PASSshould answer the query"How many calories have I logged today?" (difficulty —)0.0s

Verdict Expected QUERY — should answer the query. PASS: Query answered within tolerance.

Why verdict Query answered within tolerance.

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.0s

1 · TTS said You logged 1425 calories today.

2 · Card shown You logged 1425 calories today.

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:

Seeded value

{
  "table": "user_food_items",
  "record": {
    "id": "seed-fab70-qf-A-food-oatmeal",
    "shared_food_id": null,
    "display_name": "Codex Test Oatmeal",
    "brand": "Codex Test Fixture",
    "serving_label": "1 fixture serving",
    "serving_quantity": 1,
    "serving_unit": "serving",
    "macros_per_serving": {
      "calories": 300,
      "proteinGrams": 10,
      "fatGrams": 6,
      "carbsGrams": 54
    },
    "macros_per_100g": null,
    "times_logged": 3,
    "last_logged_at": "2026-07-18T08:00:00-04:00",
    "created_at": "2026-07-01T09:00:00-04:00"
  }
}

Seeded value

{
  "table": "user_food_items",
  "record": {
    "id": "seed-fab70-qf-A-food-blueberries",
    "shared_food_id": null,
    "display_name": "Codex Test Blueberries",
    "brand": "Codex Test Fixture",
    "serving_label": "1 fixture serving",
    "serving_quantity": 1,
    "serving_unit": "serving",
    "macros_per_serving": {
      "calories": 80,
      "proteinGrams": 1,
      "fatGrams": 0,
      "carbsGrams": 20
    },
    "macros_per_100g": null,
    "times_logged": 3,
    "last_logged_at": "2026-07-18T08:05:00-04:00",
    "created_at": "2026-07-01T09:00:00-04:00"
  }
}

Seeded value

{
  "table": "user_food_items",
  "record": {
    "id": "seed-fab70-qf-A-food-chicken",
    "shared_food_id": null,
    "display_name": "Codex Test Chicken Breast",
    "brand": "Codex Test Fixture",
    "serving_label": "1 fixture serving",
    "serving_quantity": 1,
    "serving_unit": "serving",
    "macros_per_serving": {
      "calories": 250,
      "proteinGrams": 45,
      "fatGrams": 5,
      "carbsGrams": 0
    },
    "macros_per_100g": null,
    "times_logged": 5,
    "last_logged_at": "2026-07-19T12:30:00-04:00",
    "created_at": "2026-07-01T09:00:00-04:00"
  }
}

Seeded value

{
  "table": "user_food_items",
  "record": {
    "id": "seed-fab70-qf-A-food-rice",
    "shared_food_id": null,
    "display_name": "Codex Test Brown Rice",
    "brand": "Codex Test Fixture",
    "serving_label": "1 fixture serving",
    "serving_quantity": 1,
    "serving_unit": "serving",
    "macros_per_serving": {
      "calories": 220,
      "proteinGrams": 5,
      "fatGrams": 2,
      "carbsGrams": 45
    },
    "macros_per_100g": null,
    "times_logged": 3,
    "last_logged_at": "2026-07-17T12:35:00-04:00",
    "created_at": "2026-07-01T09:00:00-04:00"
  }
}

Seeded value

{
  "table": "user_food_items",
  "record": {
    "id": "seed-fab70-qf-A-food-broccoli",
    "shared_food_id": null,
    "display_name": "Codex Test Broccoli",
    "brand": "Codex Test Fixture",
    "serving_label": "1 fixture serving",
    "serving_quantity": 1,
    "serving_unit": "serving",
    "macros_per_serving": {
      "calories": 60,
      "proteinGrams": 4,
      "fatGrams": 1,
      "carbsGrams": 10
    },
    "macros_per_100g": null,
    "times_logged": 7,
    "last_logged_at": "2026-07-19T12:40:00-04:00",
    "created_at": "2026-07-01T09:00:00-04:00"
  }
}

Seeded value

{
  "table": "user_food_items",
  "record": {
    "id": "seed-fab70-qf-A-food-yogurt",
    "shared_food_id": null,
    "display_name": "Codex Test Greek Yogurt",
    "brand": "Codex Test Fixture",
    "serving_label": "1 fixture serving",
    "serving_quantity": 1,
    "serving_unit": "serving",
    "macros_per_serving": {
      "calories": 140,
      "proteinGrams": 20,
      "fatGrams": 0,
      "carbsGrams": 15
    },
    "macros_per_100g": null,
    "times_logged": 3,
    "last_logged_at": "2026-07-18T15:30:00-04:00",
    "created_at": "2026-07-01T09:00:00-04:00"
  }
}

Seeded value

{
  "table": "user_food_items",
  "record": {
    "id": "seed-fab70-qf-A-food-banana",
    "shared_food_id": null,
    "display_name": "Codex Test Banana",
    "brand": "Codex Test Fixture",
    "serving_label": "1 fixture serving",
    "serving_quantity": 1,
    "serving_unit": "serving",
    "macros_per_serving": {
      "calories": 105,
      "proteinGrams": 1,
      "fatGrams": 0,
      "carbsGrams": 27
    },
    "macros_per_100g": null,
    "times_logged": 4,
    "last_logged_at": "2026-07-19T15:30:00-04:00",
    "created_at": "2026-07-01T09:00:00-04:00"
  }
}

Seeded value

{
  "table": "user_food_items",
  "record": {
    "id": "seed-fab70-qf-A-food-eggs",
    "shared_food_id": null,
    "display_name": "Codex Test Eggs",
    "brand": "Codex Test Fixture",
    "serving_label": "1 fixture serving",
    "serving_quantity": 1,
    "serving_unit": "serving",
    "macros_per_serving": {
      "calories": 210,
      "proteinGrams": 18,
      "fatGrams": 15,
      "carbsGrams": 2
    },
    "macros_per_100g": null,
    "times_logged": 3,
    "last_logged_at": "2026-07-19T08:00:00-04:00",
    "created_at": "2026-07-01T09:00:00-04:00"
  }
}

Seeded value

{
  "table": "user_food_items",
  "record": {
    "id": "seed-fab70-qf-A-food-toast",
    "shared_food_id": null,
    "display_name": "Codex Test Whole Grain Toast",
    "brand": "Codex Test Fixture",
    "serving_label": "1 fixture serving",
    "serving_quantity": 1,
    "serving_unit": "serving",
    "macros_per_serving": {
      "calories": 180,
      "proteinGrams": 8,
      "fatGrams": 3,
      "carbsGrams": 32
    },
    "macros_per_100g": null,
    "times_logged": 3,
    "last_logged_at": "2026-07-19T08:05:00-04:00",
    "created_at": "2026-07-01T09:00:00-04:00"
  }
}

Seeded value

{
  "table": "user_food_items",
  "record": {
    "id": "seed-fab70-qf-A-food-salmon",
    "shared_food_id": null,
    "display_name": "Codex Test Salmon",
    "brand": "Codex Test Fixture",
    "serving_label": "1 fixture serving",
    "serving_quantity": 1,
    "serving_unit": "serving",
    "macros_per_serving": {
      "calories": 360,
      "proteinGrams": 40,
      "fatGrams": 20,
      "carbsGrams": 0
    },
    "macros_per_100g": null,
    "times_logged": 3,
    "last_logged_at": "2026-07-18T19:00:00-04:00",
    "created_at": "2026-07-01T09:00:00-04:00"
  }
}

Seeded value

{
  "table": "user_food_items",
  "record": {
    "id": "seed-fab70-qf-A-food-sweet-potato",
    "shared_food_id": null,
    "display_name": "Codex Test Sweet Potato",
    "brand": "Codex Test Fixture",
    "serving_label": "1 fixture serving",
    "serving_quantity": 1,
    "serving_unit": "serving",
    "macros_per_serving": {
      "calories": 180,
      "proteinGrams": 4,
      "fatGrams": 0,
      "carbsGrams": 41
    },
    "macros_per_100g": null,
    "times_logged": 3,
    "last_logged_at": "2026-07-18T19:05:00-04:00",
    "created_at": "2026-07-01T09:00:00-04:00"
  }
}

Seeded value

{
  "table": "user_food_items",
  "record": {
    "id": "seed-fab70-qf-A-food-almonds",
    "shared_food_id": null,
    "display_name": "Codex Test Almonds",
    "brand": "Codex Test Fixture",
    "serving_label": "1 fixture serving",
    "serving_quantity": 1,
    "serving_unit": "serving",
    "macros_per_serving": {
      "calories": 170,
      "proteinGrams": 6,
      "fatGrams": 15,
      "carbsGrams": 6
    },
    "macros_per_100g": null,
    "times_logged": 3,
    "last_logged_at": "2026-07-17T15:35:00-04:00",
    "created_at": "2026-07-01T09:00:00-04:00"
  }
}

Seeded value

{
  "table": "user_food_items",
  "record": {
    "id": "seed-fab70-qf-A-food-turkey-sandwich",
    "shared_food_id": null,
    "display_name": "Codex Test Turkey Sandwich",
    "brand": "Codex Test Fixture",
    "serving_label": "1 fixture serving",
    "serving_quantity": 1,
    "serving_unit": "serving",
    "macros_per_serving": {
      "calories": 450,
      "proteinGrams": 32,
      "fatGrams": 14,
      "carbsGrams": 50
    },
    "macros_per_100g": null,
    "times_logged": 3,
    "last_logged_at": "2026-07-18T12:30:00-04:00",
    "created_at": "2026-07-01T09:00:00-04:00"
  }
}

Seeded value

{
  "table": "user_food_items",
  "record": {
    "id": "seed-fab70-qf-A-food-quinoa",
    "shared_food_id": null,
    "display_name": "Codex Test Quinoa",
    "brand": "Codex Test Fixture",
    "serving_label": "1 fixture serving",
    "serving_quantity": 1,
    "serving_unit": "serving",
    "macros_per_serving": {
      "calories": 220,
      "proteinGrams": 8,
      "fatGrams": 4,
      "carbsGrams": 39
    },
    "macros_per_100g": null,
    "times_logged": 3,
    "last_logged_at": "2026-07-19T12:35:00-04:00",
    "created_at": "2026-07-01T09:00:00-04:00"
  }
}

Seeded value

{
  "table": "user_food_items",
  "record": {
    "id": "seed-fab70-qf-A-food-avocado",
    "shared_food_id": null,
    "display_name": "Codex Test Avocado",
    "brand": "Codex Test Fixture",
    "serving_label": "1 fixture serving",
    "serving_quantity": 1,
    "serving_unit": "serving",
    "macros_per_serving": {
      "calories": 160,
      "proteinGrams": 2,
      "fatGrams": 15,
      "carbsGrams": 9
    },
    "macros_per_100g": null,
    "times_logged": 2,
    "last_logged_at": "2026-07-19T08:10:00-04:00",
    "created_at": "2026-07-01T09:00:00-04:00"
  }
}

Seeded value

{
  "table": "user_food_items",
  "record": {
    "id": "seed-fab70-qf-A-food-protein-shake",
    "shared_food_id": null,
    "display_name": "Codex Test Protein Shake",
    "brand": "Codex Test Fixture",
    "serving_label": "1 fixture serving",
    "serving_quantity": 1,
    "serving_unit": "serving",
    "macros_per_serving": {
      "calories": 240,
      "proteinGrams": 30,
      "fatGrams": 4,
      "carbsGrams": 22
    },
    "macros_per_100g": null,
    "times_logged": 2,
    "last_logged_at": "2026-07-19T15:35:00-04:00",
    "created_at": "2026-07-01T09:00:00-04:00"
  }
}

Seeded value

{
  "table": "user_food_items",
  "record": {
    "id": "seed-fab70-qf-A-food-lean-beef",
    "shared_food_id": null,
    "display_name": "Codex Test Lean Beef",
    "brand": "Codex Test Fixture",
    "serving_label": "1 fixture serving",
    "serving_quantity": 1,
    "serving_unit": "serving",
    "macros_per_serving": {
      "calories": 320,
      "proteinGrams": 38,
      "fatGrams": 16,
      "carbsGrams": 0
    },
    "macros_per_100g": null,
    "times_logged": 2,
    "last_logged_at": "2026-07-17T19:10:00-04:00",
    "created_at": "2026-07-01T09:00:00-04:00"
  }
}

Seeded value

{
  "table": "user_food_items",
  "record": {
    "id": "seed-fab70-qf-A-food-apple",
    "shared_food_id": null,
    "display_name": "Codex Test Apple",
    "brand": "Codex Test Fixture",
    "serving_label": "1 fixture serving",
    "serving_quantity": 1,
    "serving_unit": "serving",
    "macros_per_serving": {
      "calories": 95,
      "proteinGrams": 0,
      "fatGrams": 0,
      "carbsGrams": 25
    },
    "macros_per_100g": null,
    "times_logged": 2,
    "last_logged_at": "2026-07-18T15:35:00-04:00",
    "created_at": "2026-07-01T09:00:00-04:00"
  }
}

Seeded value

{
  "table": "user_food_items",
  "record": {
    "id": "seed-fab70-qf-A-food-pasta",
    "shared_food_id": null,
    "display_name": "Codex Test Pasta",
    "brand": "Codex Test Fixture",
    "serving_label": "1 fixture serving",
    "serving_quantity": 1,
    "serving_unit": "serving",
    "macros_per_serving": {
      "calories": 400,
      "proteinGrams": 14,
      "fatGrams": 6,
      "carbsGrams": 72
    },
    "macros_per_100g": null,
    "times_logged": 1,
    "last_logged_at": "2026-07-17T19:00:00-04:00",
    "created_at": "2026-07-01T09:00:00-04:00"
  }
}

Seeded value

{
  "table": "user_food_items",
  "record": {
    "id": "seed-fab70-qf-A-food-tomato-sauce",
    "shared_food_id": null,
    "display_name": "Codex Test Tomato Sauce",
    "brand": "Codex Test Fixture",
    "serving_label": "1 fixture serving",
    "serving_quantity": 1,
    "serving_unit": "serving",
    "macros_per_serving": {
      "calories": 100,
      "proteinGrams": 3,
      "fatGrams": 2,
      "carbsGrams": 18
    },
    "macros_per_100g": null,
    "times_logged": 1,
    "last_logged_at": "2026-07-17T19:05:00-04:00",
    "created_at": "2026-07-01T09:00:00-04:00"
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-fab70-qf-A-log-001",
    "user_food_id": "seed-fab70-qf-A-food-oatmeal",
    "food_name": "Codex Test Oatmeal",
    "brand": "Codex Test Fixture",
    "quantity": 1,
    "serving_label": "1 fixture serving",
    "macros": {
      "calories": 300,
      "proteinGrams": 10,
      "fatGrams": 6,
      "carbsGrams": 54
    },
    "meal": "breakfast",
    "notes": "query-frozen-A fixed Monday fixture",
    "logged_at": "2026-07-13T08:00:00-04:00",
    "deleted_by_request_id": null
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-fab70-qf-A-log-002",
    "user_food_id": "seed-fab70-qf-A-food-blueberries",
    "food_name": "Codex Test Blueberries",
    "brand": "Codex Test Fixture",
    "quantity": 1,
    "serving_label": "1 fixture serving",
    "macros": {
      "calories": 80,
      "proteinGrams": 1,
      "fatGrams": 0,
      "carbsGrams": 20
    },
    "meal": "breakfast",
    "notes": "query-frozen-A fixed Monday fixture",
    "logged_at": "2026-07-13T08:05:00-04:00",
    "deleted_by_request_id": null
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-fab70-qf-A-log-003",
    "user_food_id": "seed-fab70-qf-A-food-chicken",
    "food_name": "Codex Test Chicken Breast",
    "brand": "Codex Test Fixture",
    "quantity": 1,
    "serving_label": "1 fixture serving",
    "macros": {
      "calories": 250,
      "proteinGrams": 45,
      "fatGrams": 5,
      "carbsGrams": 0
    },
    "meal": "lunch",
    "notes": "query-frozen-A fixed Monday fixture",
    "logged_at": "2026-07-13T12:30:00-04:00",
    "deleted_by_request_id": null
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-fab70-qf-A-log-004",
    "user_food_id": "seed-fab70-qf-A-food-rice",
    "food_name": "Codex Test Brown Rice",
    "brand": "Codex Test Fixture",
    "quantity": 1,
    "serving_label": "1 fixture serving",
    "macros": {
      "calories": 220,
      "proteinGrams": 5,
      "fatGrams": 2,
      "carbsGrams": 45
    },
    "meal": "lunch",
    "notes": "query-frozen-A fixed Monday fixture",
    "logged_at": "2026-07-13T12:35:00-04:00",
    "deleted_by_request_id": null
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-fab70-qf-A-log-005",
    "user_food_id": "seed-fab70-qf-A-food-broccoli",
    "food_name": "Codex Test Broccoli",
    "brand": "Codex Test Fixture",
    "quantity": 1,
    "serving_label": "1 fixture serving",
    "macros": {
      "calories": 60,
      "proteinGrams": 4,
      "fatGrams": 1,
      "carbsGrams": 10
    },
    "meal": "lunch",
    "notes": "query-frozen-A fixed Monday fixture",
    "logged_at": "2026-07-13T12:40:00-04:00",
    "deleted_by_request_id": null
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-fab70-qf-A-log-006",
    "user_food_id": "seed-fab70-qf-A-food-yogurt",
    "food_name": "Codex Test Greek Yogurt",
    "brand": "Codex Test Fixture",
    "quantity": 1,
    "serving_label": "1 fixture serving",
    "macros": {
      "calories": 140,
      "proteinGrams": 20,
      "fatGrams": 0,
      "carbsGrams": 15
    },
    "meal": "snack",
    "notes": "query-frozen-A fixed Monday fixture",
    "logged_at": "2026-07-13T15:30:00-04:00",
    "deleted_by_request_id": null
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-fab70-qf-A-log-007",
    "user_food_id": "seed-fab70-qf-A-food-salmon",
    "food_name": "Codex Test Salmon",
    "brand": "Codex Test Fixture",
    "quantity": 1,
    "serving_label": "1 fixture serving",
    "macros": {
      "calories": 360,
      "proteinGrams": 40,
      "fatGrams": 20,
      "carbsGrams": 0
    },
    "meal": "dinner",
    "notes": "query-frozen-A fixed Monday fixture",
    "logged_at": "2026-07-13T19:00:00-04:00",
    "deleted_by_request_id": null
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-fab70-qf-A-log-008",
    "user_food_id": "seed-fab70-qf-A-food-sweet-potato",
    "food_name": "Codex Test Sweet Potato",
    "brand": "Codex Test Fixture",
    "quantity": 1,
    "serving_label": "1 fixture serving",
    "macros": {
      "calories": 180,
      "proteinGrams": 4,
      "fatGrams": 0,
      "carbsGrams": 41
    },
    "meal": "dinner",
    "notes": "query-frozen-A fixed Monday fixture",
    "logged_at": "2026-07-13T19:05:00-04:00",
    "deleted_by_request_id": null
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-fab70-qf-A-log-009",
    "user_food_id": "seed-fab70-qf-A-food-eggs",
    "food_name": "Codex Test Eggs",
    "brand": "Codex Test Fixture",
    "quantity": 1,
    "serving_label": "1 fixture serving",
    "macros": {
      "calories": 210,
      "proteinGrams": 18,
      "fatGrams": 15,
      "carbsGrams": 2
    },
    "meal": "breakfast",
    "notes": "query-frozen-A fixed Tuesday fixture",
    "logged_at": "2026-07-14T08:00:00-04:00",
    "deleted_by_request_id": null
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-fab70-qf-A-log-010",
    "user_food_id": "seed-fab70-qf-A-food-toast",
    "food_name": "Codex Test Whole Grain Toast",
    "brand": "Codex Test Fixture",
    "quantity": 1,
    "serving_label": "1 fixture serving",
    "macros": {
      "calories": 180,
      "proteinGrams": 8,
      "fatGrams": 3,
      "carbsGrams": 32
    },
    "meal": "breakfast",
    "notes": "query-frozen-A fixed Tuesday fixture",
    "logged_at": "2026-07-14T08:05:00-04:00",
    "deleted_by_request_id": null
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-fab70-qf-A-log-011",
    "user_food_id": "seed-fab70-qf-A-food-banana",
    "food_name": "Codex Test Banana",
    "brand": "Codex Test Fixture",
    "quantity": 1,
    "serving_label": "1 fixture serving",
    "macros": {
      "calories": 105,
      "proteinGrams": 1,
      "fatGrams": 0,
      "carbsGrams": 27
    },
    "meal": "snack",
    "notes": "query-frozen-A fixed Tuesday fixture",
    "logged_at": "2026-07-14T15:30:00-04:00",
    "deleted_by_request_id": null
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-fab70-qf-A-log-012",
    "user_food_id": "seed-fab70-qf-A-food-almonds",
    "food_name": "Codex Test Almonds",
    "brand": "Codex Test Fixture",
    "quantity": 1,
    "serving_label": "1 fixture serving",
    "macros": {
      "calories": 170,
      "proteinGrams": 6,
      "fatGrams": 15,
      "carbsGrams": 6
    },
    "meal": "snack",
    "notes": "query-frozen-A fixed Tuesday fixture",
    "logged_at": "2026-07-14T15:35:00-04:00",
    "deleted_by_request_id": null
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-fab70-qf-A-log-013",
    "user_food_id": "seed-fab70-qf-A-food-turkey-sandwich",
    "food_name": "Codex Test Turkey Sandwich",
    "brand": "Codex Test Fixture",
    "quantity": 1,
    "serving_label": "1 fixture serving",
    "macros": {
      "calories": 450,
      "proteinGrams": 32,
      "fatGrams": 14,
      "carbsGrams": 50
    },
    "meal": "lunch",
    "notes": "query-frozen-A fixed Tuesday fixture",
    "logged_at": "2026-07-14T12:30:00-04:00",
    "deleted_by_request_id": null
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-fab70-qf-A-log-014",
    "user_food_id": "seed-fab70-qf-A-food-chicken",
    "food_name": "Codex Test Chicken Breast",
    "brand": "Codex Test Fixture",
    "quantity": 1,
    "serving_label": "1 fixture serving",
    "macros": {
      "calories": 250,
      "proteinGrams": 45,
      "fatGrams": 5,
      "carbsGrams": 0
    },
    "meal": "dinner",
    "notes": "query-frozen-A fixed Tuesday fixture",
    "logged_at": "2026-07-14T19:00:00-04:00",
    "deleted_by_request_id": null
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-fab70-qf-A-log-015",
    "user_food_id": "seed-fab70-qf-A-food-quinoa",
    "food_name": "Codex Test Quinoa",
    "brand": "Codex Test Fixture",
    "quantity": 1,
    "serving_label": "1 fixture serving",
    "macros": {
      "calories": 220,
      "proteinGrams": 8,
      "fatGrams": 4,
      "carbsGrams": 39
    },
    "meal": "dinner",
    "notes": "query-frozen-A fixed Tuesday fixture",
    "logged_at": "2026-07-14T19:05:00-04:00",
    "deleted_by_request_id": null
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-fab70-qf-A-log-016",
    "user_food_id": "seed-fab70-qf-A-food-broccoli",
    "food_name": "Codex Test Broccoli",
    "brand": "Codex Test Fixture",
    "quantity": 1,
    "serving_label": "1 fixture serving",
    "macros": {
      "calories": 60,
      "proteinGrams": 4,
      "fatGrams": 1,
      "carbsGrams": 10
    },
    "meal": "dinner",
    "notes": "query-frozen-A fixed Tuesday fixture",
    "logged_at": "2026-07-14T19:10:00-04:00",
    "deleted_by_request_id": null
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-fab70-qf-A-log-017",
    "user_food_id": "seed-fab70-qf-A-food-oatmeal",
    "food_name": "Codex Test Oatmeal",
    "brand": "Codex Test Fixture",
    "quantity": 1,
    "serving_label": "1 fixture serving",
    "macros": {
      "calories": 300,
      "proteinGrams": 10,
      "fatGrams": 6,
      "carbsGrams": 54
    },
    "meal": "breakfast",
    "notes": "query-frozen-A fixed Wednesday fixture",
    "logged_at": "2026-07-15T08:00:00-04:00",
    "deleted_by_request_id": null
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-fab70-qf-A-log-018",
    "user_food_id": "seed-fab70-qf-A-food-banana",
    "food_name": "Codex Test Banana",
    "brand": "Codex Test Fixture",
    "quantity": 1,
    "serving_label": "1 fixture serving",
    "macros": {
      "calories": 105,
      "proteinGrams": 1,
      "fatGrams": 0,
      "carbsGrams": 27
    },
    "meal": "breakfast",
    "notes": "query-frozen-A fixed Wednesday fixture",
    "logged_at": "2026-07-15T08:05:00-04:00",
    "deleted_by_request_id": null
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-fab70-qf-A-log-019",
    "user_food_id": "seed-fab70-qf-A-food-chicken",
    "food_name": "Codex Test Chicken Breast",
    "brand": "Codex Test Fixture",
    "quantity": 1,
    "serving_label": "1 fixture serving",
    "macros": {
      "calories": 250,
      "proteinGrams": 45,
      "fatGrams": 5,
      "carbsGrams": 0
    },
    "meal": "lunch",
    "notes": "query-frozen-A fixed Wednesday fixture",
    "logged_at": "2026-07-15T12:30:00-04:00",
    "deleted_by_request_id": null
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-fab70-qf-A-log-020",
    "user_food_id": "seed-fab70-qf-A-food-rice",
    "food_name": "Codex Test Brown Rice",
    "brand": "Codex Test Fixture",
    "quantity": 1,
    "serving_label": "1 fixture serving",
    "macros": {
      "calories": 220,
      "proteinGrams": 5,
      "fatGrams": 2,
      "carbsGrams": 45
    },
    "meal": "lunch",
    "notes": "query-frozen-A fixed Wednesday fixture",
    "logged_at": "2026-07-15T12:35:00-04:00",
    "deleted_by_request_id": null
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-fab70-qf-A-log-021",
    "user_food_id": "seed-fab70-qf-A-food-avocado",
    "food_name": "Codex Test Avocado",
    "brand": "Codex Test Fixture",
    "quantity": 1,
    "serving_label": "1 fixture serving",
    "macros": {
      "calories": 160,
      "proteinGrams": 2,
      "fatGrams": 15,
      "carbsGrams": 9
    },
    "meal": "lunch",
    "notes": "query-frozen-A fixed Wednesday fixture",
    "logged_at": "2026-07-15T12:40:00-04:00",
    "deleted_by_request_id": null
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-fab70-qf-A-log-022",
    "user_food_id": "seed-fab70-qf-A-food-protein-shake",
    "food_name": "Codex Test Protein Shake",
    "brand": "Codex Test Fixture",
    "quantity": 1,
    "serving_label": "1 fixture serving",
    "macros": {
      "calories": 240,
      "proteinGrams": 30,
      "fatGrams": 4,
      "carbsGrams": 22
    },
    "meal": "snack",
    "notes": "query-frozen-A fixed Wednesday fixture",
    "logged_at": "2026-07-15T15:30:00-04:00",
    "deleted_by_request_id": null
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-fab70-qf-A-log-023",
    "user_food_id": "seed-fab70-qf-A-food-lean-beef",
    "food_name": "Codex Test Lean Beef",
    "brand": "Codex Test Fixture",
    "quantity": 1,
    "serving_label": "1 fixture serving",
    "macros": {
      "calories": 320,
      "proteinGrams": 38,
      "fatGrams": 16,
      "carbsGrams": 0
    },
    "meal": "dinner",
    "notes": "query-frozen-A fixed Wednesday fixture",
    "logged_at": "2026-07-15T19:00:00-04:00",
    "deleted_by_request_id": null
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-fab70-qf-A-log-024",
    "user_food_id": "seed-fab70-qf-A-food-sweet-potato",
    "food_name": "Codex Test Sweet Potato",
    "brand": "Codex Test Fixture",
    "quantity": 1,
    "serving_label": "1 fixture serving",
    "macros": {
      "calories": 180,
      "proteinGrams": 4,
      "fatGrams": 0,
      "carbsGrams": 41
    },
    "meal": "dinner",
    "notes": "query-frozen-A fixed Wednesday fixture",
    "logged_at": "2026-07-15T19:05:00-04:00",
    "deleted_by_request_id": null
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-fab70-qf-A-log-025",
    "user_food_id": "seed-fab70-qf-A-food-broccoli",
    "food_name": "Codex Test Broccoli",
    "brand": "Codex Test Fixture",
    "quantity": 1,
    "serving_label": "1 fixture serving",
    "macros": {
      "calories": 60,
      "proteinGrams": 4,
      "fatGrams": 1,
      "carbsGrams": 10
    },
    "meal": "dinner",
    "notes": "query-frozen-A fixed Wednesday fixture",
    "logged_at": "2026-07-15T19:10:00-04:00",
    "deleted_by_request_id": null
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-fab70-qf-A-log-026",
    "user_food_id": "seed-fab70-qf-A-food-yogurt",
    "food_name": "Codex Test Greek Yogurt",
    "brand": "Codex Test Fixture",
    "quantity": 1,
    "serving_label": "1 fixture serving",
    "macros": {
      "calories": 140,
      "proteinGrams": 20,
      "fatGrams": 0,
      "carbsGrams": 15
    },
    "meal": "breakfast",
    "notes": "query-frozen-A fixed Thursday fixture",
    "logged_at": "2026-07-16T08:00:00-04:00",
    "deleted_by_request_id": null
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-fab70-qf-A-log-027",
    "user_food_id": "seed-fab70-qf-A-food-blueberries",
    "food_name": "Codex Test Blueberries",
    "brand": "Codex Test Fixture",
    "quantity": 1,
    "serving_label": "1 fixture serving",
    "macros": {
      "calories": 80,
      "proteinGrams": 1,
      "fatGrams": 0,
      "carbsGrams": 20
    },
    "meal": "breakfast",
    "notes": "query-frozen-A fixed Thursday fixture",
    "logged_at": "2026-07-16T08:05:00-04:00",
    "deleted_by_request_id": null
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-fab70-qf-A-log-028",
    "user_food_id": "seed-fab70-qf-A-food-almonds",
    "food_name": "Codex Test Almonds",
    "brand": "Codex Test Fixture",
    "quantity": 1,
    "serving_label": "1 fixture serving",
    "macros": {
      "calories": 170,
      "proteinGrams": 6,
      "fatGrams": 15,
      "carbsGrams": 6
    },
    "meal": "breakfast",
    "notes": "query-frozen-A fixed Thursday fixture",
    "logged_at": "2026-07-16T08:10:00-04:00",
    "deleted_by_request_id": null
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-fab70-qf-A-log-029",
    "user_food_id": "seed-fab70-qf-A-food-turkey-sandwich",
    "food_name": "Codex Test Turkey Sandwich",
    "brand": "Codex Test Fixture",
    "quantity": 1,
    "serving_label": "1 fixture serving",
    "macros": {
      "calories": 450,
      "proteinGrams": 32,
      "fatGrams": 14,
      "carbsGrams": 50
    },
    "meal": "lunch",
    "notes": "query-frozen-A fixed Thursday fixture",
    "logged_at": "2026-07-16T12:30:00-04:00",
    "deleted_by_request_id": null
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-fab70-qf-A-log-030",
    "user_food_id": "seed-fab70-qf-A-food-apple",
    "food_name": "Codex Test Apple",
    "brand": "Codex Test Fixture",
    "quantity": 1,
    "serving_label": "1 fixture serving",
    "macros": {
      "calories": 95,
      "proteinGrams": 0,
      "fatGrams": 0,
      "carbsGrams": 25
    },
    "meal": "snack",
    "notes": "query-frozen-A fixed Thursday fixture",
    "logged_at": "2026-07-16T15:30:00-04:00",
    "deleted_by_request_id": null
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-fab70-qf-A-log-031",
    "user_food_id": "seed-fab70-qf-A-food-salmon",
    "food_name": "Codex Test Salmon",
    "brand": "Codex Test Fixture",
    "quantity": 1,
    "serving_label": "1 fixture serving",
    "macros": {
      "calories": 360,
      "proteinGrams": 40,
      "fatGrams": 20,
      "carbsGrams": 0
    },
    "meal": "dinner",
    "notes": "query-frozen-A fixed Thursday fixture",
    "logged_at": "2026-07-16T19:00:00-04:00",
    "deleted_by_request_id": null
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-fab70-qf-A-log-032",
    "user_food_id": "seed-fab70-qf-A-food-quinoa",
    "food_name": "Codex Test Quinoa",
    "brand": "Codex Test Fixture",
    "quantity": 1,
    "serving_label": "1 fixture serving",
    "macros": {
      "calories": 220,
      "proteinGrams": 8,
      "fatGrams": 4,
      "carbsGrams": 39
    },
    "meal": "dinner",
    "notes": "query-frozen-A fixed Thursday fixture",
    "logged_at": "2026-07-16T19:05:00-04:00",
    "deleted_by_request_id": null
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-fab70-qf-A-log-033",
    "user_food_id": "seed-fab70-qf-A-food-broccoli",
    "food_name": "Codex Test Broccoli",
    "brand": "Codex Test Fixture",
    "quantity": 1,
    "serving_label": "1 fixture serving",
    "macros": {
      "calories": 60,
      "proteinGrams": 4,
      "fatGrams": 1,
      "carbsGrams": 10
    },
    "meal": "dinner",
    "notes": "query-frozen-A fixed Thursday fixture",
    "logged_at": "2026-07-16T19:10:00-04:00",
    "deleted_by_request_id": null
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-fab70-qf-A-log-034",
    "user_food_id": "seed-fab70-qf-A-food-eggs",
    "food_name": "Codex Test Eggs",
    "brand": "Codex Test Fixture",
    "quantity": 1,
    "serving_label": "1 fixture serving",
    "macros": {
      "calories": 210,
      "proteinGrams": 18,
      "fatGrams": 15,
      "carbsGrams": 2
    },
    "meal": "breakfast",
    "notes": "query-frozen-A fixed Friday fixture",
    "logged_at": "2026-07-17T08:00:00-04:00",
    "deleted_by_request_id": null
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-fab70-qf-A-log-035",
    "user_food_id": "seed-fab70-qf-A-food-toast",
    "food_name": "Codex Test Whole Grain Toast",
    "brand": "Codex Test Fixture",
    "quantity": 1,
    "serving_label": "1 fixture serving",
    "macros": {
      "calories": 180,
      "proteinGrams": 8,
      "fatGrams": 3,
      "carbsGrams": 32
    },
    "meal": "breakfast",
    "notes": "query-frozen-A fixed Friday fixture",
    "logged_at": "2026-07-17T08:05:00-04:00",
    "deleted_by_request_id": null
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-fab70-qf-A-log-036",
    "user_food_id": "seed-fab70-qf-A-food-chicken",
    "food_name": "Codex Test Chicken Breast",
    "brand": "Codex Test Fixture",
    "quantity": 1,
    "serving_label": "1 fixture serving",
    "macros": {
      "calories": 250,
      "proteinGrams": 45,
      "fatGrams": 5,
      "carbsGrams": 0
    },
    "meal": "lunch",
    "notes": "query-frozen-A fixed Friday fixture",
    "logged_at": "2026-07-17T12:30:00-04:00",
    "deleted_by_request_id": null
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-fab70-qf-A-log-037",
    "user_food_id": "seed-fab70-qf-A-food-rice",
    "food_name": "Codex Test Brown Rice",
    "brand": "Codex Test Fixture",
    "quantity": 1,
    "serving_label": "1 fixture serving",
    "macros": {
      "calories": 220,
      "proteinGrams": 5,
      "fatGrams": 2,
      "carbsGrams": 45
    },
    "meal": "lunch",
    "notes": "query-frozen-A fixed Friday fixture",
    "logged_at": "2026-07-17T12:35:00-04:00",
    "deleted_by_request_id": null
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-fab70-qf-A-log-038",
    "user_food_id": "seed-fab70-qf-A-food-broccoli",
    "food_name": "Codex Test Broccoli",
    "brand": "Codex Test Fixture",
    "quantity": 1,
    "serving_label": "1 fixture serving",
    "macros": {
      "calories": 60,
      "proteinGrams": 4,
      "fatGrams": 1,
      "carbsGrams": 10
    },
    "meal": "lunch",
    "notes": "query-frozen-A fixed Friday fixture",
    "logged_at": "2026-07-17T12:40:00-04:00",
    "deleted_by_request_id": null
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-fab70-qf-A-log-039",
    "user_food_id": "seed-fab70-qf-A-food-banana",
    "food_name": "Codex Test Banana",
    "brand": "Codex Test Fixture",
    "quantity": 1,
    "serving_label": "1 fixture serving",
    "macros": {
      "calories": 105,
      "proteinGrams": 1,
      "fatGrams": 0,
      "carbsGrams": 27
    },
    "meal": "snack",
    "notes": "query-frozen-A fixed Friday fixture",
    "logged_at": "2026-07-17T15:30:00-04:00",
    "deleted_by_request_id": null
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-fab70-qf-A-log-040",
    "user_food_id": "seed-fab70-qf-A-food-almonds",
    "food_name": "Codex Test Almonds",
    "brand": "Codex Test Fixture",
    "quantity": 1,
    "serving_label": "1 fixture serving",
    "macros": {
      "calories": 170,
      "proteinGrams": 6,
      "fatGrams": 15,
      "carbsGrams": 6
    },
    "meal": "snack",
    "notes": "query-frozen-A fixed Friday fixture",
    "logged_at": "2026-07-17T15:35:00-04:00",
    "deleted_by_request_id": null
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-fab70-qf-A-log-041",
    "user_food_id": "seed-fab70-qf-A-food-pasta",
    "food_name": "Codex Test Pasta",
    "brand": "Codex Test Fixture",
    "quantity": 1,
    "serving_label": "1 fixture serving",
    "macros": {
      "calories": 400,
      "proteinGrams": 14,
      "fatGrams": 6,
      "carbsGrams": 72
    },
    "meal": "dinner",
    "notes": "query-frozen-A fixed Friday fixture",
    "logged_at": "2026-07-17T19:00:00-04:00",
    "deleted_by_request_id": null
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-fab70-qf-A-log-042",
    "user_food_id": "seed-fab70-qf-A-food-tomato-sauce",
    "food_name": "Codex Test Tomato Sauce",
    "brand": "Codex Test Fixture",
    "quantity": 1,
    "serving_label": "1 fixture serving",
    "macros": {
      "calories": 100,
      "proteinGrams": 3,
      "fatGrams": 2,
      "carbsGrams": 18
    },
    "meal": "dinner",
    "notes": "query-frozen-A fixed Friday fixture",
    "logged_at": "2026-07-17T19:05:00-04:00",
    "deleted_by_request_id": null
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-fab70-qf-A-log-043",
    "user_food_id": "seed-fab70-qf-A-food-lean-beef",
    "food_name": "Codex Test Lean Beef",
    "brand": "Codex Test Fixture",
    "quantity": 1,
    "serving_label": "1 fixture serving",
    "macros": {
      "calories": 320,
      "proteinGrams": 38,
      "fatGrams": 16,
      "carbsGrams": 0
    },
    "meal": "dinner",
    "notes": "query-frozen-A fixed Friday fixture",
    "logged_at": "2026-07-17T19:10:00-04:00",
    "deleted_by_request_id": null
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-fab70-qf-A-log-044",
    "user_food_id": "seed-fab70-qf-A-food-oatmeal",
    "food_name": "Codex Test Oatmeal",
    "brand": "Codex Test Fixture",
    "quantity": 1,
    "serving_label": "1 fixture serving",
    "macros": {
      "calories": 300,
      "proteinGrams": 10,
      "fatGrams": 6,
      "carbsGrams": 54
    },
    "meal": "breakfast",
    "notes": "query-frozen-A fixed Saturday fixture",
    "logged_at": "2026-07-18T08:00:00-04:00",
    "deleted_by_request_id": null
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-fab70-qf-A-log-045",
    "user_food_id": "seed-fab70-qf-A-food-blueberries",
    "food_name": "Codex Test Blueberries",
    "brand": "Codex Test Fixture",
    "quantity": 1,
    "serving_label": "1 fixture serving",
    "macros": {
      "calories": 80,
      "proteinGrams": 1,
      "fatGrams": 0,
      "carbsGrams": 20
    },
    "meal": "breakfast",
    "notes": "query-frozen-A fixed Saturday fixture",
    "logged_at": "2026-07-18T08:05:00-04:00",
    "deleted_by_request_id": null
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-fab70-qf-A-log-046",
    "user_food_id": "seed-fab70-qf-A-food-turkey-sandwich",
    "food_name": "Codex Test Turkey Sandwich",
    "brand": "Codex Test Fixture",
    "quantity": 1,
    "serving_label": "1 fixture serving",
    "macros": {
      "calories": 450,
      "proteinGrams": 32,
      "fatGrams": 14,
      "carbsGrams": 50
    },
    "meal": "lunch",
    "notes": "query-frozen-A fixed Saturday fixture",
    "logged_at": "2026-07-18T12:30:00-04:00",
    "deleted_by_request_id": null
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-fab70-qf-A-log-047",
    "user_food_id": "seed-fab70-qf-A-food-yogurt",
    "food_name": "Codex Test Greek Yogurt",
    "brand": "Codex Test Fixture",
    "quantity": 1,
    "serving_label": "1 fixture serving",
    "macros": {
      "calories": 140,
      "proteinGrams": 20,
      "fatGrams": 0,
      "carbsGrams": 15
    },
    "meal": "snack",
    "notes": "query-frozen-A fixed Saturday fixture",
    "logged_at": "2026-07-18T15:30:00-04:00",
    "deleted_by_request_id": null
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-fab70-qf-A-log-048",
    "user_food_id": "seed-fab70-qf-A-food-apple",
    "food_name": "Codex Test Apple",
    "brand": "Codex Test Fixture",
    "quantity": 1,
    "serving_label": "1 fixture serving",
    "macros": {
      "calories": 95,
      "proteinGrams": 0,
      "fatGrams": 0,
      "carbsGrams": 25
    },
    "meal": "snack",
    "notes": "query-frozen-A fixed Saturday fixture",
    "logged_at": "2026-07-18T15:35:00-04:00",
    "deleted_by_request_id": null
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-fab70-qf-A-log-049",
    "user_food_id": "seed-fab70-qf-A-food-salmon",
    "food_name": "Codex Test Salmon",
    "brand": "Codex Test Fixture",
    "quantity": 1,
    "serving_label": "1 fixture serving",
    "macros": {
      "calories": 360,
      "proteinGrams": 40,
      "fatGrams": 20,
      "carbsGrams": 0
    },
    "meal": "dinner",
    "notes": "query-frozen-A fixed Saturday fixture",
    "logged_at": "2026-07-18T19:00:00-04:00",
    "deleted_by_request_id": null
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-fab70-qf-A-log-050",
    "user_food_id": "seed-fab70-qf-A-food-sweet-potato",
    "food_name": "Codex Test Sweet Potato",
    "brand": "Codex Test Fixture",
    "quantity": 1,
    "serving_label": "1 fixture serving",
    "macros": {
      "calories": 180,
      "proteinGrams": 4,
      "fatGrams": 0,
      "carbsGrams": 41
    },
    "meal": "dinner",
    "notes": "query-frozen-A fixed Saturday fixture",
    "logged_at": "2026-07-18T19:05:00-04:00",
    "deleted_by_request_id": null
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-fab70-qf-A-log-051",
    "user_food_id": "seed-fab70-qf-A-food-broccoli",
    "food_name": "Codex Test Broccoli",
    "brand": "Codex Test Fixture",
    "quantity": 1,
    "serving_label": "1 fixture serving",
    "macros": {
      "calories": 60,
      "proteinGrams": 4,
      "fatGrams": 1,
      "carbsGrams": 10
    },
    "meal": "dinner",
    "notes": "query-frozen-A fixed Saturday fixture",
    "logged_at": "2026-07-18T19:10:00-04:00",
    "deleted_by_request_id": null
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-fab70-qf-A-log-052",
    "user_food_id": "seed-fab70-qf-A-food-eggs",
    "food_name": "Codex Test Eggs",
    "brand": "Codex Test Fixture",
    "quantity": 1,
    "serving_label": "1 fixture serving",
    "macros": {
      "calories": 210,
      "proteinGrams": 18,
      "fatGrams": 15,
      "carbsGrams": 2
    },
    "meal": "breakfast",
    "notes": "query-frozen-A fixed Sunday fixture",
    "logged_at": "2026-07-19T08:00:00-04:00",
    "deleted_by_request_id": null
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-fab70-qf-A-log-053",
    "user_food_id": "seed-fab70-qf-A-food-toast",
    "food_name": "Codex Test Whole Grain Toast",
    "brand": "Codex Test Fixture",
    "quantity": 1,
    "serving_label": "1 fixture serving",
    "macros": {
      "calories": 180,
      "proteinGrams": 8,
      "fatGrams": 3,
      "carbsGrams": 32
    },
    "meal": "breakfast",
    "notes": "query-frozen-A fixed Sunday fixture",
    "logged_at": "2026-07-19T08:05:00-04:00",
    "deleted_by_request_id": null
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-fab70-qf-A-log-054",
    "user_food_id": "seed-fab70-qf-A-food-avocado",
    "food_name": "Codex Test Avocado",
    "brand": "Codex Test Fixture",
    "quantity": 1,
    "serving_label": "1 fixture serving",
    "macros": {
      "calories": 160,
      "proteinGrams": 2,
      "fatGrams": 15,
      "carbsGrams": 9
    },
    "meal": "breakfast",
    "notes": "query-frozen-A fixed Sunday fixture",
    "logged_at": "2026-07-19T08:10:00-04:00",
    "deleted_by_request_id": null
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-fab70-qf-A-log-055",
    "user_food_id": "seed-fab70-qf-A-food-banana",
    "food_name": "Codex Test Banana",
    "brand": "Codex Test Fixture",
    "quantity": 1,
    "serving_label": "1 fixture serving",
    "macros": {
      "calories": 105,
      "proteinGrams": 1,
      "fatGrams": 0,
      "carbsGrams": 27
    },
    "meal": "snack",
    "notes": "query-frozen-A fixed Sunday fixture",
    "logged_at": "2026-07-19T15:30:00-04:00",
    "deleted_by_request_id": null
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-fab70-qf-A-log-056",
    "user_food_id": "seed-fab70-qf-A-food-protein-shake",
    "food_name": "Codex Test Protein Shake",
    "brand": "Codex Test Fixture",
    "quantity": 1,
    "serving_label": "1 fixture serving",
    "macros": {
      "calories": 240,
      "proteinGrams": 30,
      "fatGrams": 4,
      "carbsGrams": 22
    },
    "meal": "snack",
    "notes": "query-frozen-A fixed Sunday fixture",
    "logged_at": "2026-07-19T15:35:00-04:00",
    "deleted_by_request_id": null
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-fab70-qf-A-log-057",
    "user_food_id": "seed-fab70-qf-A-food-chicken",
    "food_name": "Codex Test Chicken Breast",
    "brand": "Codex Test Fixture",
    "quantity": 1,
    "serving_label": "1 fixture serving",
    "macros": {
      "calories": 250,
      "proteinGrams": 45,
      "fatGrams": 5,
      "carbsGrams": 0
    },
    "meal": "lunch",
    "notes": "query-frozen-A fixed Sunday fixture",
    "logged_at": "2026-07-19T12:30:00-04:00",
    "deleted_by_request_id": null
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-fab70-qf-A-log-058",
    "user_food_id": "seed-fab70-qf-A-food-quinoa",
    "food_name": "Codex Test Quinoa",
    "brand": "Codex Test Fixture",
    "quantity": 1,
    "serving_label": "1 fixture serving",
    "macros": {
      "calories": 220,
      "proteinGrams": 8,
      "fatGrams": 4,
      "carbsGrams": 39
    },
    "meal": "lunch",
    "notes": "query-frozen-A fixed Sunday fixture",
    "logged_at": "2026-07-19T12:35:00-04:00",
    "deleted_by_request_id": null
  }
}

Seeded value

{
  "table": "food_log_entries",
  "record": {
    "id": "seed-fab70-qf-A-log-059",
    "user_food_id": "seed-fab70-qf-A-food-broccoli",
    "food_name": "Codex Test Broccoli",
    "brand": "Codex Test Fixture",
    "quantity": 1,
    "serving_label": "1 fixture serving",
    "macros": {
      "calories": 60,
      "proteinGrams": 4,
      "fatGrams": 1,
      "carbsGrams": 10
    },
    "meal": "lunch",
    "notes": "query-frozen-A fixed Sunday fixture",
    "logged_at": "2026-07-19T12:40:00-04:00",
    "deleted_by_request_id": null
  }
}

Seeded value

{
  "table": "user_module_preferences",
  "record": {
    "id": "seed-fab70-qf-A-nutrition-goals",
    "module_key": "nutrition",
    "preferences": {
      "responseSummary": {
        "calories": true,
        "protein": true,
        "fat": true,
        "carbs": true,
        "water": false
      },
      "dailyTargets": {
        "calories": 2200,
        "proteinGrams": 150,
        "fatGrams": 70,
        "carbsGrams": 250
      }
    },
    "updated_at": "2026-07-19T06:00:00-04:00",
    "deleted_by_request_id": null
  }
}

snapshot captured 2026-08-02T10:32:58.022Z

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.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 answer the query"What is my calorie total so far today?" (difficulty —)0.1s

Verdict Expected QUERY — should answer the query. PASS: Query answered within tolerance.

Why verdict Query answered within tolerance.

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.1s

1 · TTS said You logged 1425 calories today.

2 · Card shown You logged 1425 calories 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-02T10:33:09.185Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, 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 answer the query"How much protein have I had today?" (difficulty —)0.0s

Verdict Expected QUERY — should answer the query. PASS: Query answered within tolerance.

Why verdict Query answered within tolerance.

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.0s

1 · TTS said You logged 116 grams of protein today.

2 · Card shown You logged 116 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-02T10:33:20.347Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, 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 answer the query"How much fat have I logged today?" (difficulty —)0.1s

Verdict Expected QUERY — should answer the query. PASS: Query answered within tolerance.

Why verdict Query answered within tolerance.

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.1s

1 · TTS said You logged 47 grams of fat today.

2 · Card shown You logged 47 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-02T10:33:31.522Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, 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 answer the query"How many carbs have I had today?" (difficulty —)0.0s

Verdict Expected QUERY — should answer the query. PASS: Query answered within tolerance.

Why verdict Query answered within tolerance.

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.0s

1 · TTS said You logged 141 grams of carbs today.

2 · Card shown You logged 141 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-02T10:33:42.689Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, 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 answer the query"Give me all my macros for today so far." (difficulty —)0.1s

Verdict Expected QUERY — should answer the query. PASS: Query answered within tolerance.

Why verdict Query answered within tolerance.

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.1s

1 · TTS said Today. Items: 1 1 fixture serving Codex Test Fixture Codex Test Eggs; 1 1 fixture serving Codex Test Fixture Codex Test Whole Grain Toast; 1 1 fixture serving Codex Test Fixture Codex Test Avocado; 1 1 fixture serving Codex Test Fixture Codex Test Chicken Breast; 1 1 fixture serving Codex Test Fixture Codex Test Quinoa; 1 1 fixture serving Codex Test Fixture Codex Test Broccoli; 1 1 fixture serving Codex Test Fixture Codex Test Banana; 1 1 fixture serving Codex Test Fixture Codex Test Protein Shake. Calories: 1425. Protein: 116 grams. Fat: 47 grams. Carbs: 141 grams. Entry count: 8.

2 · Card shown Today. Items: 1 1 fixture serving Codex Test Fixture Codex Test Eggs; 1 1 fixture serving Codex Test Fixture Codex Test Whole Grain Toast; 1 1 fixture serving Codex Test Fixture Codex Test Avocado; 1 1 fixture serving Codex Test Fixture Codex Test Chicken Breast; 1 1 fixture serving Codex Test Fixture Codex Test Quinoa; 1 1 fixture serving Codex Test Fixture Codex Test Broccoli; 1 1 fixture serving Codex Test Fixture Codex Test Banana; 1 1 fixture serving Codex Test Fixture Codex Test Protein Shake. Calories: 1425. Protein: 116 grams. Fat: 47 grams. Carbs: 141 grams. Entry count: 8.

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

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

snapshot captured 2026-08-02T10:33:53.873Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, 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 answer the query"How many calories did I have yesterday?" (difficulty —)0.0s

Verdict Expected QUERY — should answer the query. PASS: Query answered within tolerance.

Why verdict Query answered within tolerance.

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.0s

1 · TTS said You logged 1665 calories yesterday.

2 · Card shown You logged 1665 calories 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-02T10:34:05.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.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 answer the query"How much protein did I eat yesterday?" (difficulty —)0.0s

Verdict Expected QUERY — should answer the query. PASS: Query answered within tolerance.

Why verdict Query answered within tolerance.

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.0s

1 · TTS said You logged 111 grams of protein yesterday.

2 · Card shown You logged 111 grams of protein 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-02T10:34:16.402Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, 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 answer the query"How much fat did I have yesterday?" (difficulty —)0.0s

Verdict Expected QUERY — should answer the query. PASS: Query answered within tolerance.

Why verdict Query answered within tolerance.

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.0s

1 · TTS said You logged 41 grams of fat yesterday.

2 · Card shown You logged 41 grams of fat 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-02T10:34:27.570Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, 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 answer the query"How many carbs did I eat yesterday?" (difficulty —)0.0s

Verdict Expected QUERY — should answer the query. PASS: Query answered within tolerance.

Why verdict Query answered within tolerance.

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.0s

1 · TTS said You logged 215 grams of carbs yesterday.

2 · Card shown You logged 215 grams of carbs 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-02T10:34:38.742Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, 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 answer the query"What were my total calories and macros yesterday?" (difficulty —)0.0s

Verdict Expected QUERY — should answer the query. PASS: Query answered within tolerance.

Why verdict Query answered within tolerance.

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.0s

1 · TTS said Yesterday. Items: 1 1 fixture serving Codex Test Fixture Codex Test Oatmeal; 1 1 fixture serving Codex Test Fixture Codex Test Blueberries; 1 1 fixture serving Codex Test Fixture Codex Test Turkey Sandwich; 1 1 fixture serving Codex Test Fixture Codex Test Greek Yogurt; 1 1 fixture serving Codex Test Fixture Codex Test Apple; 1 1 fixture serving Codex Test Fixture Codex Test Salmon; 1 1 fixture serving Codex Test Fixture Codex Test Sweet Potato; 1 1 fixture serving Codex Test Fixture Codex Test Broccoli. Calories: 1665. Protein: 111 grams. Fat: 41 grams. Carbs: 215 grams. Entry count: 8.

2 · Card shown Yesterday. Items: 1 1 fixture serving Codex Test Fixture Codex Test Oatmeal; 1 1 fixture serving Codex Test Fixture Codex Test Blueberries; 1 1 fixture serving Codex Test Fixture Codex Test Turkey Sandwich; 1 1 fixture serving Codex Test Fixture Codex Test Greek Yogurt; 1 1 fixture serving Codex Test Fixture Codex Test Apple; 1 1 fixture serving Codex Test Fixture Codex Test Salmon; 1 1 fixture serving Codex Test Fixture Codex Test Sweet Potato; 1 1 fixture serving Codex Test Fixture Codex Test Broccoli. Calories: 1665. Protein: 111 grams. Fat: 41 grams. Carbs: 215 grams. Entry count: 8.

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

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

snapshot captured 2026-08-02T10:34:49.920Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, 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 answer the query"What did I eat yesterday?" (difficulty —)0.0s

Verdict Expected QUERY — should answer the query. FAIL: answer did not state expected numeric value(s): mealCount

Why verdict answer did not state expected numeric value(s): mealCount

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

Pick every reason you think applies. Multiple boxes 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

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

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

snapshot captured 2026-08-02T10:35:01.068Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 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 answer the query"What did I have for breakfast yesterday?" (difficulty —)0.0s

Verdict Expected QUERY — should answer the query. PASS: Query answered within tolerance.

Why verdict Query answered within tolerance.

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.0s

1 · TTS said Breakfast yesterday. Items: 1 1 fixture serving Codex Test Fixture Codex Test Oatmeal; 1 1 fixture serving Codex Test Fixture Codex Test Blueberries. Calories: 380. Protein: 11 grams. Fat: 6 grams. Carbs: 74 grams. Entry count: 2.

2 · Card shown Breakfast yesterday. Items: 1 1 fixture serving Codex Test Fixture Codex Test Oatmeal; 1 1 fixture serving Codex Test Fixture Codex Test Blueberries. Calories: 380. Protein: 11 grams. Fat: 6 grams. Carbs: 74 grams. Entry count: 2.

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

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

snapshot captured 2026-08-02T10:35:12.249Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, 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 answer the query"What was lunch yesterday?" (difficulty —)0.0s

Verdict Expected QUERY — should answer the query. PASS: Query answered within tolerance.

Why verdict Query answered within tolerance.

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.0s

1 · TTS said Lunch yesterday. Items: 1 1 fixture serving Codex Test Fixture Codex Test Turkey Sandwich. Calories: 450. Protein: 32 grams. Fat: 14 grams. Carbs: 50 grams. Entry count: 1.

2 · Card shown Lunch yesterday. Items: 1 1 fixture serving Codex Test Fixture Codex Test Turkey Sandwich. Calories: 450. Protein: 32 grams. Fat: 14 grams. Carbs: 50 grams. Entry count: 1.

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

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

snapshot captured 2026-08-02T10:35:23.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 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 answer the query"What snacks did I log yesterday?" (difficulty —)0.0s

Verdict Expected QUERY — should answer the query. PASS: Query answered within tolerance.

Why verdict Query answered within tolerance.

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.0s

1 · TTS said Snack yesterday. Items: 1 1 fixture serving Codex Test Fixture Codex Test Greek Yogurt; 1 1 fixture serving Codex Test Fixture Codex Test Apple. Calories: 235. Protein: 20 grams. Fat: 0 grams. Carbs: 40 grams. Entry count: 2.

2 · Card shown Snack yesterday. Items: 1 1 fixture serving Codex Test Fixture Codex Test Greek Yogurt; 1 1 fixture serving Codex Test Fixture Codex Test Apple. Calories: 235. Protein: 20 grams. Fat: 0 grams. Carbs: 40 grams. Entry count: 2.

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

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

snapshot captured 2026-08-02T10:35:34.682Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, 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 answer the query"What did I have for dinner yesterday?" (difficulty —)0.0s

Verdict Expected QUERY — should answer the query. PASS: Query answered within tolerance.

Why verdict Query answered within tolerance.

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.0s

1 · TTS said Dinner yesterday. Items: 1 1 fixture serving Codex Test Fixture Codex Test Salmon; 1 1 fixture serving Codex Test Fixture Codex Test Sweet Potato; 1 1 fixture serving Codex Test Fixture Codex Test Broccoli. Calories: 600. Protein: 48 grams. Fat: 21 grams. Carbs: 51 grams. Entry count: 3.

2 · Card shown Dinner yesterday. Items: 1 1 fixture serving Codex Test Fixture Codex Test Salmon; 1 1 fixture serving Codex Test Fixture Codex Test Sweet Potato; 1 1 fixture serving Codex Test Fixture Codex Test Broccoli. Calories: 600. Protein: 48 grams. Fat: 21 grams. Carbs: 51 grams. Entry count: 3.

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

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

snapshot captured 2026-08-02T10:35:45.852Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, 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 answer the query"How many calories were in the banana I logged today?" (difficulty —)0.1s

Verdict Expected QUERY — should answer the query. PASS: Query answered within tolerance.

Why verdict Query answered within tolerance.

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.1s

1 · TTS said Codex Test Banana today. Calories: 105.

2 · Card shown Codex Test Banana today. Calories: 105.

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

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

snapshot captured 2026-08-02T10:35:57.039Z

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.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 answer the query"How much protein was in today's banana?" (difficulty —)0.1s

Verdict Expected QUERY — should answer the query. PASS: Query answered within tolerance.

Why verdict Query answered within tolerance.

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.1s

1 · TTS said Codex Test Banana today. Protein: 1 grams.

2 · Card shown Codex Test Banana today. Protein: 1 grams.

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

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

snapshot captured 2026-08-02T10:36:08.225Z

6 · Why this food

The lookup compared against planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
Matched the common-food list to "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.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 answer the query"How many calories were in the protein shake I logged?" (difficulty —)0.1s

Verdict Expected QUERY — should answer the query. PASS: Query answered within tolerance.

Why verdict Query answered within tolerance.

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.1s

1 · TTS said Codex Test Protein Shake today. Calories: 240.

2 · Card shown Codex Test Protein Shake today. Calories: 240.

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

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

snapshot captured 2026-08-02T10:36:19.395Z

6 · Why this food

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

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 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 answer the query"How many calories were in the chicken at lunch today?" (difficulty —)0.0s

Verdict Expected QUERY — should answer the query. PASS: Query answered within tolerance.

Why verdict Query answered within tolerance.

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.0s

1 · TTS said Codex Test Chicken Breast at lunch today. Calories: 250.

2 · Card shown Codex Test Chicken Breast at lunch today. Calories: 250.

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

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

snapshot captured 2026-08-02T10:36:30.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 "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.9 seconds to collect.
This lookup is supporting evidence in the report; by itself it does not prove that food was saved.

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

PASSshould answer the query"How many times did I have chicken this week?" (difficulty —)0.1s

Verdict Expected QUERY — should answer the query. PASS: Query answered within tolerance.

Why verdict Query answered within tolerance.

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.1s

1 · TTS said You logged Codex Test Chicken Breast 5 times this week.

2 · Card shown You logged Codex Test Chicken Breast 5 times this week.

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

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

snapshot captured 2026-08-02T10:36:53.355Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, 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 answer the query"How many bananas did I log this week?" (difficulty —)0.1s

Verdict Expected QUERY — should answer the query. PASS: Query answered within tolerance.

Why verdict Query answered within tolerance.

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.1s

1 · TTS said You logged Codex Test Banana 4 times this week.

2 · Card shown You logged Codex Test Banana 4 times this week.

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

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

snapshot captured 2026-08-02T10:37:04.536Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, 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 answer the query"How many times did I eat salmon this week?" (difficulty —)0.0s

Verdict Expected QUERY — should answer the query. PASS: Query answered within tolerance.

Why verdict Query answered within tolerance.

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.0s

1 · TTS said You logged Codex Test Salmon 3 times this week.

2 · Card shown You logged Codex Test Salmon 3 times this week.

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

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

snapshot captured 2026-08-02T10:37:15.714Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 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 answer the query"How many turkey sandwiches did I have this week?" (difficulty —)0.1s

Verdict Expected QUERY — should answer the query. PASS: Query answered within tolerance.

Why verdict Query answered within tolerance.

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.1s

1 · TTS said You logged Codex Test Turkey Sandwich 3 times this week.

2 · Card shown You logged Codex Test Turkey Sandwich 3 times this week.

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

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

snapshot captured 2026-08-02T10:37:26.888Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, 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 answer the query"How many food entries have I logged this week?" (difficulty —)0.0s

Verdict Expected QUERY — should answer the query. PASS: Query answered within tolerance.

Why verdict Query answered within tolerance.

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.0s

1 · TTS said You have 59 food entries logged this week.

2 · Card shown You have 59 food entries logged this week.

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

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

snapshot captured 2026-08-02T10:37:38.053Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 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 answer the query"How many food entries did I log today?" (difficulty —)0.0s

Verdict Expected QUERY — should answer the query. PASS: Query answered within tolerance.

Why verdict Query answered within tolerance.

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.0s

1 · TTS said You have 8 food entries logged today.

2 · Card shown You have 8 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-02T10:37:49.219Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, 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 answer the query"How many breakfast entries did I log today?" (difficulty —)0.1s

Verdict Expected QUERY — should answer the query. FAIL: answer did not state expected numeric value(s): entryCount

Why verdict answer did not state expected numeric value(s): entryCount

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

Pick every reason you think applies. Multiple boxes 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 3 breakfast food entries logged today.

2 · Card shown You have 3 breakfast 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-02T10:38:00.415Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, 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 answer the query"How many snack entries did I log today?" (difficulty —)0.1s

Verdict Expected QUERY — should answer the query. FAIL: answer did not state expected numeric value(s): entryCount

Why verdict answer did not state expected numeric value(s): entryCount

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

Pick every reason you think applies. Multiple boxes 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 2 snack food entries logged today.

2 · Card shown You have 2 snack 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-02T10:38:11.618Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, 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 answer the query"How many calories did I log Monday?" (difficulty —)0.1s

Verdict Expected QUERY — should answer the query. PASS: Query answered within tolerance.

Why verdict Query answered within tolerance.

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.1s

1 · TTS said You logged 1590 calories on Monday.

2 · Card shown You logged 1590 calories on Monday.

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

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

snapshot captured 2026-08-02T10:38:22.901Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, 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 answer the query"How much protein did I have Monday?" (difficulty —)0.0s

Verdict Expected QUERY — should answer the query. PASS: Query answered within tolerance.

Why verdict Query answered within tolerance.

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.0s

1 · TTS said You logged 129 grams of protein on Monday.

2 · Card shown You logged 129 grams of protein on Monday.

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

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

snapshot captured 2026-08-02T10:38:34.091Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, 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 answer the query"How many carbs did I eat Monday?" (difficulty —)0.0s

Verdict Expected QUERY — should answer the query. PASS: Query answered within tolerance.

Why verdict Query answered within tolerance.

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.0s

1 · TTS said You logged 185 grams of carbs on Monday.

2 · Card shown You logged 185 grams of carbs on Monday.

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

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

snapshot captured 2026-08-02T10:38:45.281Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, 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 answer the query"What did I have for breakfast Monday?" (difficulty —)0.1s

Verdict Expected QUERY — should answer the query. PASS: Query answered within tolerance.

Why verdict Query answered within tolerance.

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.1s

1 · TTS said Breakfast on Monday. Items: 1 1 fixture serving Codex Test Fixture Codex Test Oatmeal; 1 1 fixture serving Codex Test Fixture Codex Test Blueberries. Calories: 380. Protein: 11 grams. Fat: 6 grams. Carbs: 74 grams. Entry count: 2.

2 · Card shown Breakfast on Monday. Items: 1 1 fixture serving Codex Test Fixture Codex Test Oatmeal; 1 1 fixture serving Codex Test Fixture Codex Test Blueberries. Calories: 380. Protein: 11 grams. Fat: 6 grams. Carbs: 74 grams. Entry count: 2.

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

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

snapshot captured 2026-08-02T10:38:56.403Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, 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 answer the query"How much fat did I have Tuesday?" (difficulty —)0.0s

Verdict Expected QUERY — should answer the query. PASS: Query answered within tolerance.

Why verdict Query answered within tolerance.

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.0s

1 · TTS said You logged 57 grams of fat on Tuesday.

2 · Card shown You logged 57 grams of fat on Tuesday.

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

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

snapshot captured 2026-08-02T10:39:07.597Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, 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 answer the query"What was my calorie total Tuesday?" (difficulty —)0.0s

Verdict Expected QUERY — should answer the query. PASS: Query answered within tolerance.

Why verdict Query answered within tolerance.

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.0s

1 · TTS said You logged 1645 calories on Tuesday.

2 · Card shown You logged 1645 calories on Tuesday.

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

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

snapshot captured 2026-08-02T10:39:18.770Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, 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 answer the query"How much protein did I eat Wednesday?" (difficulty —)0.0s

Verdict Expected QUERY — should answer the query. PASS: Query answered within tolerance.

Why verdict Query answered within tolerance.

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.0s

1 · TTS said You logged 139 grams of protein on Wednesday.

2 · Card shown You logged 139 grams of protein on Wednesday.

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

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

snapshot captured 2026-08-02T10:39:29.936Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, 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 answer the query"How many calories were in Wednesday dinner?" (difficulty —)0.0s

Verdict Expected QUERY — should answer the query. PASS: Query answered within tolerance.

Why verdict Query answered within tolerance.

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.0s

1 · TTS said Dinner on Wednesday: 560 calories.

2 · Card shown Dinner on Wednesday: 560 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-02T10:39:41.102Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, 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 answer the query"How many carbs did I have Thursday?" (difficulty —)0.0s

Verdict Expected QUERY — should answer the query. PASS: Query answered within tolerance.

Why verdict Query answered within tolerance.

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.0s

1 · TTS said You logged 165 grams of carbs on Thursday.

2 · Card shown You logged 165 grams of carbs on Thursday.

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

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

snapshot captured 2026-08-02T10:39:52.307Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, 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 answer the query"How much protein was in Thursday breakfast?" (difficulty —)0.1s

Verdict Expected QUERY — should answer the query. PASS: Query answered within tolerance.

Why verdict Query answered within tolerance.

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.1s

1 · TTS said Breakfast on Thursday: 27 grams of protein.

2 · Card shown Breakfast on Thursday: 27 grams of protein.

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

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

snapshot captured 2026-08-02T10:40:03.517Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, 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 answer the query"How many calories did I eat Friday?" (difficulty —)0.0s

Verdict Expected QUERY — should answer the query. PASS: Query answered within tolerance.

Why verdict Query answered within tolerance.

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.0s

1 · TTS said You logged 2015 calories on Friday.

2 · Card shown You logged 2015 calories on Friday.

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

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

snapshot captured 2026-08-02T10:40:14.695Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, 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 answer the query"How many calories were in Friday dinner?" (difficulty —)0.0s

Verdict Expected QUERY — should answer the query. PASS: Query answered within tolerance.

Why verdict Query answered within tolerance.

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.0s

1 · TTS said Dinner on Friday: 820 calories.

2 · Card shown Dinner on Friday: 820 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-02T10:40:25.890Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, 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 answer the query"What was my protein total yesterday?" (difficulty —)0.0s

Verdict Expected QUERY — should answer the query. PASS: Query answered within tolerance.

Why verdict Query answered within tolerance.

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.0s

1 · TTS said You logged 111 grams of protein yesterday.

2 · Card shown You logged 111 grams of protein 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-02T10:40:48.589Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, 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 answer the query"How many calories have I logged this week?" (difficulty —)0.1s

Verdict Expected QUERY — should answer the query. PASS: Query answered within tolerance.

Why verdict Query answered within tolerance.

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.1s

1 · TTS said You logged 11750 calories this week.

2 · Card shown You logged 11750 calories this week.

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

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

snapshot captured 2026-08-02T10:40:59.765Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, 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 answer the query"How much protein have I logged this week?" (difficulty —)0.1s

Verdict Expected QUERY — should answer the query. PASS: Query answered within tolerance.

Why verdict Query answered within tolerance.

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.1s

1 · TTS said You logged 870 grams of protein this week.

2 · Card shown You logged 870 grams of protein this week.

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

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

snapshot captured 2026-08-02T10:41:10.932Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, 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 answer the query"How much fat have I logged this week?" (difficulty —)0.0s

Verdict Expected QUERY — should answer the query. PASS: Query answered within tolerance.

Why verdict Query answered within tolerance.

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.0s

1 · TTS said You logged 347 grams of fat this week.

2 · Card shown You logged 347 grams of fat this week.

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

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

snapshot captured 2026-08-02T10:41:22.101Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, 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 answer the query"How many carbs have I logged this week?" (difficulty —)0.1s

Verdict Expected QUERY — should answer the query. PASS: Query answered within tolerance.

Why verdict Query answered within tolerance.

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.1s

1 · TTS said You logged 1292 grams of carbs this week.

2 · Card shown You logged 1292 grams of carbs this week.

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

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

snapshot captured 2026-08-02T10:41:33.283Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, 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 answer the query"What is my average daily calorie total this week?" (difficulty —)0.1s

Verdict Expected QUERY — should answer the query. PASS: Query answered within tolerance.

Why verdict Query answered within tolerance.

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.1s

1 · TTS said Average daily calories: 1678.5714 calories.

2 · Card shown Average daily calories: 1678.5714 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-02T10:41:44.471Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, 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 answer the query"What is my average protein per day this week?" (difficulty —)0.1s

Verdict Expected QUERY — should answer the query. PASS: Query answered within tolerance.

Why verdict Query answered within tolerance.

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.1s

1 · TTS said Average daily protein: 124.2857 g protein.

2 · Card shown Average daily protein: 124.2857 g protein.

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

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

snapshot captured 2026-08-02T10:41:55.665Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, 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 answer the query"Which day had the most calories this week?" (difficulty —)0.1s

Verdict Expected QUERY — should answer the query. PASS: Query answered within tolerance.

Why verdict Query answered within tolerance.

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.1s

1 · TTS said Friday had the most calories this week. Calories: 2015.

2 · Card shown Friday had the most calories this week. Calories: 2015.

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

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

snapshot captured 2026-08-02T10:42:06.847Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 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 answer the query"Based on what is logged, which day had the fewest calories this week?" (difficulty —)0.1s

Verdict Expected QUERY — should answer the query. PASS: Query answered within tolerance.

Why verdict Query answered within tolerance.

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.1s

1 · TTS said Sunday had the fewest calories this week. Calories: 1425.

2 · Card shown Sunday had the fewest calories this week. Calories: 1425.

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

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

snapshot captured 2026-08-02T10:42:18.049Z

7 · Lookup method

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

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

PASSshould answer the query"How many calories do I have left today?" (difficulty —)0.1s

Verdict Expected QUERY — should answer the query. PASS: Query answered within tolerance.

Why verdict Query answered within tolerance.

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.1s

1 · TTS said You have about 775 calories left in today's budget (1425 of 2200 logged).

2 · Card shown You have about 775 calories left in today's budget (1425 of 2200 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-02T10:42:29.251Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, 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 answer the query"How many calories are left for dinner?" (difficulty —)0.0s

Verdict Expected QUERY — should answer the query. PASS: Query answered within tolerance.

Why verdict Query answered within tolerance.

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.0s

1 · TTS said You have about 775 calories left in today's budget (1425 of 2200 logged).

2 · Card shown You have about 775 calories left in today's budget (1425 of 2200 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-02T10:42:40.480Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, 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 answer the query"How much protein do I have left today?" (difficulty —)0.1s

Verdict Expected QUERY — should answer the query. PASS: Query answered within tolerance.

Why verdict Query answered within tolerance.

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.1s

1 · TTS said You have about 34 grams of protein left today (116 of 150 grams logged).

2 · Card shown You have about 34 grams of protein left today (116 of 150 grams 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-02T10:42:51.634Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 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 answer the query"How much fat is left in my budget today?" (difficulty —)0.1s

Verdict Expected QUERY — should answer the query. PASS: Query answered within tolerance.

Why verdict Query answered within tolerance.

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.1s

1 · TTS said You have about 23 grams of fat left today (47 of 70 grams logged).

2 · Card shown You have about 23 grams of fat left today (47 of 70 grams 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-02T10:43:02.851Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, 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 answer the query"How many carbs do I have left today?" (difficulty —)0.1s

Verdict Expected QUERY — should answer the query. PASS: Query answered within tolerance.

Why verdict Query answered within tolerance.

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.1s

1 · TTS said You have about 109 grams of carbs left today (141 of 250 grams logged).

2 · Card shown You have about 109 grams of carbs left today (141 of 250 grams 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-02T10:43:13.997Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, 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 answer the query"What percent of my calorie goal have I used today?" (difficulty —)0.1s

Verdict Expected QUERY — should answer the query. PASS: Query answered within tolerance.

Why verdict Query answered within tolerance.

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.1s

1 · TTS said Calorie goal used: 64.7727%. Calories logged: 1425. Calorie goal: 2200.

2 · Card shown Calorie goal used: 64.7727%. Calories logged: 1425. Calorie goal: 2200.

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

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

snapshot captured 2026-08-02T10:43:25.186Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, 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 answer the query"Am I over my calorie goal today?" (difficulty —)0.1s

Verdict Expected QUERY — should answer the query. PASS: Query answered within tolerance.

Why verdict Query answered within tolerance.

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.1s

1 · TTS said Over calorie goal: No. Calories over: 0. Calories remaining: 775.

2 · Card shown Over calorie goal: No. Calories over: 0. Calories remaining: 775.

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

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

snapshot captured 2026-08-02T10:43:36.354Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, 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 answer the query"Did I get more protein today or yesterday?" (difficulty —)0.0s

Verdict Expected QUERY — should answer the query. PASS: Query answered within tolerance.

Why verdict Query answered within tolerance.

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.0s

1 · TTS said Today: 116 g protein. Yesterday: 111 g protein. Difference: 5 g protein.

2 · Card shown Today: 116 g protein. Yesterday: 111 g protein. Difference: 5 g protein.

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

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

snapshot captured 2026-08-02T10:43:47.520Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, 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 answer the query"Did I eat more calories today or yesterday?" (difficulty —)0.0s

Verdict Expected QUERY — should answer the query. PASS: Query answered within tolerance.

Why verdict Query answered within tolerance.

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.0s

1 · TTS said Today: 1425 calories. Yesterday: 1665 calories. Difference: 240 calories.

2 · Card shown Today: 1425 calories. Yesterday: 1665 calories. Difference: 240 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-02T10:43:58.657Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, 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 answer the query"Was my fat higher today or yesterday?" (difficulty —)0.0s

Verdict Expected QUERY — should answer the query. PASS: Query answered within tolerance.

Why verdict Query answered within tolerance.

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.0s

1 · TTS said Today: 47 g fat. Yesterday: 41 g fat. Difference: 6 g fat.

2 · Card shown Today: 47 g fat. Yesterday: 41 g fat. Difference: 6 g fat.

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

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

snapshot captured 2026-08-02T10:44:09.825Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, 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 answer the query"Did I have more carbs today or yesterday?" (difficulty —)0.0s

Verdict Expected QUERY — should answer the query. PASS: Query answered within tolerance.

Why verdict Query answered within tolerance.

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.0s

1 · TTS said Today: 141 g carbs. Yesterday: 215 g carbs. Difference: 74 g carbs.

2 · Card shown Today: 141 g carbs. Yesterday: 215 g carbs. Difference: 74 g carbs.

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

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

snapshot captured 2026-08-02T10:44:21.031Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, 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 answer the query"Which had more protein, Monday or Friday?" (difficulty —)0.1s

Verdict Expected QUERY — should answer the query. PASS: Query answered within tolerance.

Why verdict Query answered within tolerance.

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.1s

1 · TTS said Monday: 129 g protein. Friday: 142 g protein. Difference: 13 g protein.

2 · Card shown Monday: 129 g protein. Friday: 142 g protein. Difference: 13 g protein.

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

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

snapshot captured 2026-08-02T10:44:43.731Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, 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 answer the query"Which had more calories, Tuesday or Thursday?" (difficulty —)0.1s

Verdict Expected QUERY — should answer the query. PASS: Query answered within tolerance.

Why verdict Query answered within tolerance.

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.1s

1 · TTS said Tuesday: 1645 calories. Thursday: 1575 calories. Difference: 70 calories.

2 · Card shown Tuesday: 1645 calories. Thursday: 1575 calories. Difference: 70 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-02T10:44:54.899Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, 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 answer the query"How many calories were in breakfast today?" (difficulty —)0.1s

Verdict Expected QUERY — should answer the query. PASS: Query answered within tolerance.

Why verdict Query answered within tolerance.

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.1s

1 · TTS said Breakfast today: 550 calories.

2 · Card shown Breakfast today: 550 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-02T10:45:06.103Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, 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 answer the query"How many calories were in lunch today?" (difficulty —)0.0s

Verdict Expected QUERY — should answer the query. PASS: Query answered within tolerance.

Why verdict Query answered within tolerance.

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.0s

1 · TTS said Lunch today: 530 calories.

2 · Card shown Lunch today: 530 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-02T10:45:17.312Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, 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 answer the query"How many calories were in my snacks today?" (difficulty —)0.1s

Verdict Expected QUERY — should answer the query. PASS: Query answered within tolerance.

Why verdict Query answered within tolerance.

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.1s

1 · TTS said Snack today: 345 calories.

2 · Card shown Snack today: 345 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-02T10:45:28.464Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, your past food logs, the shared nutrition database, the common-food list, the exercise list, and the workout equipment list.
The lookup evidence took 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 answer the query"What was my largest meal today?" (difficulty —)0.1s

Verdict Expected QUERY — should answer the query. PASS: Query answered within tolerance.

Why verdict Query answered within tolerance.

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.1s

1 · TTS said Breakfast was your largest meal today. Calories: 550.

2 · Card shown Breakfast was your largest meal today. Calories: 550.

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

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

snapshot captured 2026-08-02T10:45:39.678Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, 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 answer the query"How many calories came from chicken this week?" (difficulty —)0.1s

Verdict Expected QUERY — should answer the query. PASS: Query answered within tolerance.

Why verdict Query answered within tolerance.

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.1s

1 · TTS said Codex Test Chicken Breast this week. Calories: 1250.

2 · Card shown Codex Test Chicken Breast this week. Calories: 1250.

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

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

snapshot captured 2026-08-02T10:45:50.852Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, 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 answer the query"How many calories came from bananas this week?" (difficulty —)0.1s

Verdict Expected QUERY — should answer the query. PASS: Query answered within tolerance.

Why verdict Query answered within tolerance.

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.1s

1 · TTS said Codex Test Banana this week. Calories: 420.

2 · Card shown Codex Test Banana this week. Calories: 420.

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

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

snapshot captured 2026-08-02T10:46:02.054Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, 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 answer the query"How much protein came from salmon this week?" (difficulty —)0.1s

Verdict Expected QUERY — should answer the query. PASS: Query answered within tolerance.

Why verdict Query answered within tolerance.

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.1s

1 · TTS said Codex Test Salmon this week. Protein: 120 grams.

2 · Card shown Codex Test Salmon this week. Protein: 120 grams.

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

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

snapshot captured 2026-08-02T10:46:13.286Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, 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 answer the query"How many breakfast calories did I log this week?" (difficulty —)0.1s

Verdict Expected QUERY — should answer the query. PASS: Query answered within tolerance.

Why verdict Query answered within tolerance.

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.1s

1 · TTS said Breakfast this week: 2885 calories.

2 · Card shown Breakfast this week: 2885 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-02T10:46:24.465Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, 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)

FAILshould answer the query"What was my average dinner calorie total for the six completed days?" (difficulty —)0.0s

Verdict Expected QUERY — should answer the query. FAIL: answer did not state expected numeric value(s): averageCalories

Why verdict answer did not state expected numeric value(s): averageCalories

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

Pick every reason you think applies. Multiple boxes 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 could not find a to-do matching days.

2 · Card shown I could not find a to-do matching days.

4 · UI did navigated to "todos" screen

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

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

snapshot captured 2026-08-02T10:46:35.635Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, 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 answer the query"On how many days did I reach at least 120 grams of protein?" (difficulty —)0.1s

Verdict Expected QUERY — should answer the query. PASS: Query answered within tolerance.

Why verdict Query answered within tolerance.

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 0.1s

1 · TTS said Days at or above 120 g protein: 4.

2 · Card shown Days at or above 120 g protein: 4.

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

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

snapshot captured 2026-08-02T10:46:47.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 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 navigate"Open my food history." (difficulty —)0.0s

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

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-02T10:46:58.213Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, 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 handle appropriately"Thanks, that is helpful." (difficulty —)1.8s

Verdict Expected OTHER — should handle appropriately. PASS: OTHER conversation_acknowledgement — brief acknowledgement with no write on the general route.

Why verdict OTHER conversation_acknowledgement — brief acknowledgement with no write on the general route.

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 1.8s

1 · TTS said You're welcome. Ready for your next log or question.

2 · Card shown You're welcome. Ready for your next log or question.

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

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

snapshot captured 2026-08-02T10:47:11.211Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, 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 navigate"Show me the nutrition dashboard." (difficulty —)0.0s

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

1 · TTS said Opening Food Today.

2 · Card shown Opening Food Today.

4 · UI did navigated to "food" screen

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

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

snapshot captured 2026-08-02T10:47:22.355Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, 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 handle appropriately"Okay, let us keep going." (difficulty —)1.0s

Verdict Expected OTHER — should handle appropriately. PASS: OTHER conversation_acknowledgement — brief acknowledgement with no write on the general route.

Why verdict OTHER conversation_acknowledgement — brief acknowledgement with no write on the general route.

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

Pick every reason you think applies. Multiple 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 Of course. Ready when you are. Are you looking to log something new, or do you have a question about your current data?

2 · Card shown Of course. Ready when you are. Are you looking to log something new, or do you have a question about your current data?

4 · UI did no screen events captured

5 · Seed/context data

Seeded starting state: none listed in the corpus row.

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

snapshot captured 2026-08-02T10:47:34.539Z

7 · Lookup method

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

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

FAILshould navigate"Go back to today in my food diary." (difficulty —)1.6s

Verdict Expected NAVIGATE — should navigate. FAIL: Did not navigate — misrouted into a food/workout clarification or dead-ended.

Why verdict Did not navigate — misrouted into a food/workout clarification or dead-ended.

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

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

Timing 1.6s

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: none listed in the corpus row.

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

snapshot captured 2026-08-02T10:47:47.293Z

7 · Lookup method

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

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

FAILshould handle appropriately"Good to know." (difficulty —)0.0s

Verdict Expected OTHER — should handle appropriately. FAIL: OTHER conversation_acknowledgement — response was not an acknowledgement or was too long

Why verdict OTHER conversation_acknowledgement — response was not an acknowledgement or was too long

My override

Things I think are wrong

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

Comprehension

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

Execution

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

Cosmetic

Wording weird

Other thing wrong (describe below)

Things the report marked wrong but I think are right

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

Actually right

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

Report/grader issue

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

Other thing actually right (describe below)

Pick every reason you think applies. Multiple boxes 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: none listed in the corpus row.

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

snapshot captured 2026-08-02T10:47:58.435Z

7 · Lookup method

The report captured the app food lookup that ran before or alongside the final decision.
It searched planned foods, your saved foods and aliases, 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)

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