Internal product map
Evidence before pages
The directory is generated from reviewed graph records. Restaurant brands are not locations, menu items are not canonical dishes, and a food truck is not permanently parked wherever someone last photographed it.
Six layers
Records where information came from, what may be stored, and how recently the source was checked.
src_Government record, official page, menu, publisher, creator, community, or first-party source.
data/catalog/sources.jsoncreator_A public reviewer, creator, critic, or publisher identity connected to attributed sources.
data/catalog/creators.jsonSeparates raw observations from atomic claims so confidence, freshness, and disagreement remain visible.
signal_An observed permit, license, inspection, announcement, menu, review, event, or closure lead.
data/catalog/signals.ndjsonevidence_A source-backed artifact or reference that supports or contradicts a claim.
data/catalog/evidence.ndjsonclaim_An atomic assertion with confidence, validity dates, verification date, and evidence IDs.
data/catalog/claims.ndjsonedge_An evidence-backed relationship between two canonical records.
data/catalog/edges.ndjsonDistinguishes a brand or operator from each physical location and its current lifecycle state.
brand_The canonical concept, brand, or operator identity shared by one or more locations.
data/catalog/restaurants.jsonloc_A physical location with address, coordinates, opening state, and location-specific menu evidence.
data/catalog/locations.jsonhood_A named Houston-area geography used for discovery, routing, and local demand pages.
data/catalog/taxonomies.jsonMakes the thing people actually want to eat a first-class entity instead of hiding it inside a restaurant page.
cuisine_A practical discovery taxonomy that may contain parent-child and cross-tradition relationships.
data/catalog/taxonomies.jsontradition_A cultural or regional lineage kept separate from broad commercial cuisine labels.
data/catalog/taxonomies.jsondish_A canonical food concept with aliases, techniques, cuisines, traditions, and flavor descriptors.
data/catalog/dishes.jsonmenu_A dated snapshot of a location-specific menu from an attributable source.
data/catalog/menus.jsonitem_A named, priced, time-bound restaurant offering that may resolve to a canonical dish.
data/catalog/menus.jsonModels food trucks, pop-ups, markets, events, and temporary appearances without inventing permanent addresses.
vendor_A food truck or mobile operator whose current location is represented by appearances, not a permanent pin.
data/catalog/mobile.jsonpopup_A temporary concept, residency, supper club, or market stall with dated appearances.
data/catalog/mobile.jsonvenue_A market, bar, food hall, park, event space, or host location.
data/catalog/events.jsonevent_A time-bounded market, festival, collaboration, dinner, or public food event.
data/catalog/events.jsonappearance_The dated connection between a vendor or pop-up and a venue, event, or coordinate.
data/catalog/mobile.jsonPublishes only the pages, filters, maps, and feeds supported by approved evidence.
Publication gate
Relationship contract
| Edge | From | To | Meaning |
|---|---|---|---|
HAS_LOCATION | restaurant_brand | restaurant_location | A brand operates or is represented by a location. |
LOCATED_IN | restaurant_location, venue | neighborhood | A physical place belongs to a mapped neighborhood or service area. |
HAS_MENU | restaurant_location | menu_version | A location has a dated, attributable menu snapshot. |
CONTAINS_ITEM | menu_version | menu_item | A menu snapshot contains a location-specific item. |
REPRESENTS_DISH | menu_item | dish | A menu item resolves to a canonical dish when the match is sufficiently supported. |
ASSOCIATED_WITH_CUISINE | restaurant_brand, dish | cuisine | A business or dish is associated with a practical cuisine taxonomy. |
ROOTED_IN_TRADITION | dish, cuisine | tradition | A dish or cuisine is connected to a cultural or regional culinary tradition. |
PUBLISHED_BY | source | creator | A public source is published by an attributable creator, critic, or newsroom identity. |
MENTIONS | source, claim | restaurant_brand, restaurant_location, dish, menu_item, mobile_vendor, popup, event | A source or review claim discusses a canonical entity without implying endorsement. |
ASSERTS | source, signal | claim | A source observation gives rise to an atomic claim. |
SUPPORTS | evidence | claim, edge | Evidence supports, qualifies, or contradicts a claim or relationship. |
HOSTED_AT | event | venue | An event is scheduled at a venue. |
APPEARS_AT | mobile_vendor, popup | appearance | A mobile or temporary concept has a dated appearance record. |
OPERATED_BY | mobile_vendor, popup | restaurant_brand | A mobile or temporary concept is operated by a known canonical brand or operator. |
SUPERSEDES | menu_version, claim | menu_version, claim | A newer record explicitly replaces an older one without erasing history. |
RELATED_TO | dish, cuisine, tradition | dish, cuisine, tradition | A non-hierarchical food relationship used for flavor and discovery navigation. |
Geographic output
restaurant_location
Approved locations with lifecycleState=open and current verification.
restaurant_location
Approved or explicitly quarantined opening states shown with confidence and evidence labels.
restaurant_location
Time-sensitive lifecycle changes with visible verification dates.
mobile_vendor + appearance
Pins come from dated appearances, never from a stale permanent-address assumption.
popup + appearance
Time-bounded appearances connected to a venue, event, or coordinate.
event + venue
Approved upcoming events with explicit start and end dates.
dish + menu_item + restaurant_location
Generated from current menu evidence rather than restaurant category labels alone.
claim + restaurant_location + dish
Shows source diversity, date range, disagreement, confidence, and freshness instead of a magic score.
Decision surfaces
Approved location, current state, visible sources, and location-specific evidence.
Canonical dish plus multiple current menu-item relationships or strong standalone demand.
Coordinates, lifecycle state, confidence, evidence, and last verification date.
Independent source diversity, date range, themes, disagreement, and disclosure visibility.
Approved vendor plus dated appearance records and explicit location timing.
Distinct intent, canonical entities, enough evidence, unique answer, and useful next action.