Source: https://guthlabs.ai/docs/instruments/leftover-freshness-countdown-tracker/

instrument / verified-clean

# Leftover/Freshness Countdown Tracker

The current ledger marks this instrument verified clean within the source-bound verification corpus.

Status: **VERIFIED_CLEAN**Lifecycle: **verified-clean**

## Inspectable records

[01**Overview**Purpose and lifecycle](<https://guthlabs.ai/docs/instruments/leftover-freshness-countdown-tracker/>)[02**Mechanism**Method and assumptions](<https://guthlabs.ai/docs/instruments/leftover-freshness-countdown-tracker/mechanism/>)[03**Implementation**Binding and validation](<https://guthlabs.ai/docs/instruments/leftover-freshness-countdown-tracker/implementation/>)[04**Qualification**Evidence and errata](<https://guthlabs.ai/docs/instruments/leftover-freshness-countdown-tracker/qualification/>)

## Ledger state

The current ledger marks this instrument verified clean within the source-bound verification corpus.

**Area**: Everyday & Life

**Tranche**: tranche-7

**Evidence ID**: t7-074

**Ledger rows**: 1

No ledger note is attached.

## Review findings

The core subtraction is standard date arithmetic, but the instrument is not formula-complete because the table contains ranges and mixed units and the specification does not define a selection or conversion policy. The honest-label warning is appropriate and should be prominent: estimates only, not a substitute for USDA food-safety guidance or sensory and handling judgment.

### Formula and scope findings

- The date arithmetic is valid only after a single shelf-life value is selected, but USDA FoodKeeper commonly provides ranges such as 3–4 days or 1–2 days; the specification does not define whether to use the minimum, maximum, or another value.

- FoodKeeper shelf-life guidance is an estimated quality/safety window, not a calculated spoilage date. The output should be labeled an estimated discard/use-by date rather than an expiry or spoilage date.

- Freezer guidance is often expressed in months and for quality rather than safety; converting months to shelf_life_days requires an explicit calendar-month versus fixed-day policy.

- The formula omits storage temperature, refrigerator/freezer operating condition, packaging, whether the food was opened, and time spent in the temperature danger zone. Food type plus broad storage method is insufficient for a reliable safety estimate.

- The subtraction convention is unspecified: it must define whether days_left is a calendar-day difference, whether the storage date counts as day zero, and whether negative values are permitted after the estimated date.

### Unit assumptions

- Dates are interpreted as ISO calendar dates in the proleptic Gregorian calendar.

- expiry_date = date_stored plus the selected shelf-life duration; the storage date is day zero.

- days_left = expiry_date minus today, measured as whole calendar days. A result of zero means the estimated date is today; a negative result means the estimate has passed.

- For the refrigerated vectors, the implementation policy used here selects the conservative maximum table endpoint: 4 days for cooked leftovers, 7 days for hard-cooked eggs, and 2 days for raw chicken. This policy is not stated in the instrument specification.

- The frozen-leftovers table value is expressed as 2–6 months. The test vector explicitly uses a 180-day approximation for the 6-month upper endpoint; this is not equivalent to six calendar months in every date interval.

## Boundary hardening

**BREAK_CLAIMED** · SELF_FLAGGED

The instrument cannot produce a deterministic numeric result from the supplied specification because the required FoodSafety.gov/USDA shelf-life lookup table is absent and the table may contain ranges rather than one shelf-life value. It also lacks an explicit date-range and overflow policy; a positive shelf life added to 9999-12-31 produces an out-of-range date.

## Errata and corrections

No applied erratum is attached to this unique-name record.

## Inspectable example

4 review vectors are recorded. One source-bound sample is shown below.

````
{
  "inputs": {
    "food_item": "cooked meat or poultry leftovers",
    "date_stored": "2025-03-01",
    "storage_method": "fridge",
    "today": "2025-03-05"
  },
  "expected_outputs": {
    "estimated_use_by_date": "2025-03-05",
    "days_remaining": 0
  },
  "reference_data": {
    "foodkeeper_table_row": {
      "food_item": "cooked meat or poultry leftovers",
      "storage_method": "refrigerator",
      "shelf_life": "3–4 days"
    },
    "selected_shelf_life_days": 4,
    "selection_policy": "maximum endpoint of the USDA range",
    "source_convention": "USDA FoodKeeper / FoodSafety.gov standard consumer food-storage table value"
  },
  "working": "1. Select 4 days from the table's 3–4 day refrigerator range using the stated maximum-endpoint policy. 2. 2025-03-01 + 4 calendar days = 2025-03-05. 3. days_left = 2025-03-05 − 2025-03-05 = 0 days."
}
````

## Related workflows

No source-defined multi-instrument workflow membership is recorded.

## Sources and evidence

These pointers bind the page to evidence. They do not grant authority or collapse verification into deployment.

- `VERIFIED_LEDGER.json · VERIFIED_CLEAN`

- `evidence-tranche7/tranche7-results.json`

- `BOUNDARY_HAZARD_CATALOG.json`