Skip to content
Food Atlas / Location Layer

Where you are should change the answer.

4DK should understand location as kitchen context—not as a cuisine prison. Location affects availability, names, measures, substitutions, seasonality and shopping language. Cuisine interest remains a separate choice.

Core rule

Location = what is realistically around you. Cuisine interest = what you want to eat. They can influence each other without becoming the same thing.

world → country → city.
never a cage.
4DK FOOD ATLAS / LOCATIONCONTEXT, NOT IDENTITY
Active scope
Lagos

City-level context for likely availability, shopping language and substitution realism.

CurrencyNGN
UnitsMetric + market usage
RetailCity-level
ConfidenceEvidence-based, not assumed
Location.
Cuisine.
Availability.
Language.
Substitution.
01 / Separation

Why should location and cuisine stay separate?

Someone in Lagos may want Japanese food tonight, while someone elsewhere may want Nigerian food. Location should adapt availability and shopping advice—not decide what the user is allowed to want.

Where are you?

Lagos.

Used for currency, likely ingredient availability, local naming and shopping phrasing.

What do you want to eat?

Nigerian

Cuisine interest is preference/context. It should not be overwritten by geography.

02 / Availability

How should 4DK decide what is realistically obtainable?

Use evidence and confidence. City context can narrow likely availability, but Pantry, receipts and observed shopping should outrank broad geographic assumptions.

Availability mode

Local-first

Local-first prefers easier-to-obtain substitutes. Open mode allows wider suggestions. Pantry-only uses what is already known.

Confidence model

Observed ≠ assumed.

A food item seen in Pantry or a receipt is stronger evidence than a generic city-level guess.

03 / Location record

What belongs inside a location record?

Names

Canonical + local.

Aliases and market names resolve to one underlying ingredient entity.

Measures

How people buy.

Metric data can coexist with bunches, tins, sachets and other retail units.

Availability

Likely, not guaranteed.

Observed evidence should outrank city-level assumptions.

Substitution

Function first.

Local substitutes still have to do the culinary job.

Culture

Context, not cages.

Location can enrich food context without assuming the user only eats local cuisine.

Language

Say the right thing.

Local names and interface copy can adapt while canonical data stays stable underneath.

Actual 4DK interface
Atlas → recommendation engine

Same craving.
Better local answer.

“Make katsu tonight” can stay Japanese in intent while shopping and substitution advice adapts to the ingredients a user can realistically obtain.

Use location context in 4DK →