Build structured data from a current restaurant menu

Why use this

1. A diner or researcher may need menu details in a reusable format but find several versions with different prices and categories. A structured table can look current even when it was extracted from an old image or a third-party copy.

2. This job could organize menu information while keeping source identity and freshness evidence visible. Explicitly unresolved prices are more useful than a falsely precise comparison when the restaurant's published materials disagree.

Why an agent / simpler alternative

Useful judgment

Identify the restaurant's own menu, interpret categories and qualifiers, and distinguish current evidence from assumptions.

Simpler alternative

Copy a small clearly dated menu manually when no comparison or restructuring is needed.

Unsuitable when

The result would be treated as guaranteed pricing, availability or allergy-safe ordering advice.

Proposed inputs

1. Name

   Restaurant identity

   Owner

   Requester

   Minimum scope

   Name, branch and official website if known

   Quality check

   Resolve similarly named businesses and locations

2. Name

   Menu materials

   Owner

   Restaurant's published source

   Minimum scope

   Permitted text/images with URL and collection date

   Quality check

   Check menu date, currency and branch relevance

Access and setup — proposed or unknown

Proposed minimum

1. Read public menu materials and create a draft structured table; no order, reservation or account access.

Compatibility unknowns

1. Website accessibility, menu date reliability, extraction quality and runtime compatibility are unknown.

External actions requiring approval

1. Contacting the restaurant, uploading private material or placing orders needs separate authorization.

Expected deliverable and review checks

Proposed artifact

Menu dataset with item, category, description, stated price, qualifiers, source and freshness caveat.

Critical checks

1. Preserve size/variant prices; distinguish add-ons and ranges; leave missing prices unresolved; verify category alignment.

Missing output evidence

This overlay adds no new output inspection, execution or validation; consult the referenced canonical source outcome limits.

Failure signals and proposed responses

1. Signal

   A price belongs to an adjacent item

   Why it matters

   Layout extraction creates a misleading value

   Proposed response

   Compare against the original visual and flag ambiguity.

2. Signal

   Official pages show conflicting menus

   Why it matters

   Official ownership alone does not establish currency

   Proposed response

   Retain both dates and avoid choosing a current price without evidence.

Effort and cost — unknown

Setup work

1. Confirm branch identity and output fields.

Ongoing review

1. Recheck stale or ambiguous entries before practical use.

Unknowns

1. Menu update cadence, OCR effort, regional taxes and service costs are unknown.

First check — proposed, unexecuted

Status

proposed_unexecuted

Synthetic fixture

Invent a two-column menu with one size-dependent price, one add-on and a conflicting older version; propose structured rows.

Acceptance checks

1. Keep variants separate; label the add-on; preserve the conflict and source dates.

Stop conditions

1. Stop if branch identity or price association cannot be resolved without guessing.

Limits

1. Published menus do not guarantee availability, final charges or suitability for dietary and medical needs.