enjoythai.land

Not every source deserves a traveler widget.

This queue decides which catalog and support sources can move into observations, signals, and public tips. A source only gets promoted when it changes a real traveler subject and can be explained honestly.

Promotion gates

All required gates must pass before a source becomes a traveler-facing widget or changes tips scores.

requiredChanges a traveler subject

Could this source change where someone goes, stays, routes, ferries, eats, shops, or seeks help?

requiredAccess and automation are clear

Is access public or permissioned in a way we can honestly automate and label?

requiredCan produce timestamped observations

Can we store an observed_at or published_at value that is separate from fetch time?

requiredMaps to an existing signal

Does it map to a known signal such as air pollution, ferry fragility. Route friction, stay fit. Food-route confidence, or gold context?

requiredOwned by a subject family

Does a named subject family own the source output?

requiredExplainable in one sentence

Can the page say what this source proves and what it does not prove?

requiredPrivacy and safety boundaries are explicit

Does the source avoid private, dispatch, patient, case-level, or personally sensitive data?

Candidate queue

These are the high-value Thailand source candidates from the source-gap work, with their current runtime role and next action.

Keep Bangkok expressway and airport/coast corridor friction visible before routing travelers out of the city.

Already subject-driving through route and place-fit signals.

Statuspromoted subject driving
Gate score7/7
Runtime rolesubject-driving

Owned by: route-check, today

Next: Keep using as route-friction support; do not label it as guaranteed live traffic unless the connector verifies a current traffic observation.

Let highway traffic, cameras, speed, flow, and road-search context influence overland route caution.

Already subject-driving for route support and transfer burden.

Statuspromoted subject driving
Gate score7/7
Runtime rolesubject-driving

Owned by: route-check, today

Next: Keep automation terms visible and avoid stronger claims than the public surface supports.

Improve Pai, Kanchanaburi, island-access-road, and rural route confidence once road and bridge fields are mapped.

Catalog-only until the schema is normalized into route support observations.

Statuskeep catalog only
Gate score5/7
Runtime rolecatalog-only

Owned by: route-check

Next: Define road/bridge observation fields, then promote to health-checked before letting it feed visitor route recommendations.

Use berth and movement evidence for ferry-risk confidence without pretending it is a ticket, schedule, or seat feed.

Already subject-driving for ferry and Transports.

Statuspromoted subject driving
Gate score7/7
Runtime rolesubject-driving

Owned by: ferry-check, route-check

Next: Keep page copy clear that berth evidence is not operator seat availability.

Separate sea, wave, wind, and shipping risk from generic weather before recommending island transfers.

Already subject-driving for ferry and island route signals.

Statuspromoted subject driving
Gate score7/7
Runtime rolesubject-driving

Owned by: ferry-check, route-check, today

Next: Add more granular Gulf/Andaman labels only if the source exposes stable regional fields.

Let licensed spa and massage evidence support venue and stay-area confidence without making quality claims.

Already subject-driving for wellness/stay support.

Statuspromoted subject driving
Gate score7/7
Runtime rolesubject-driving

Owned by: where-to-stay, today

Next: Keep license confidence separate from reviews, opening hours, and service quality.

Add official food-sanitation confidence to food-route pages where coverage is usable.

Catalog-only until establishment or area coverage can be mapped without overclaiming.

Statuskeep catalog only
Gate score5/7
Runtime rolecatalog-only

Owned by: food-route

Next: Map fields to restaurant-area confidence and keep it separate from taste, popularity, and current opening status.

Represent hospital and clinic fallback depth without implying emergency availability.

Already subject-driving for stay and place confidence.

Statuspromoted subject driving
Gate score7/7
Runtime rolesubject-driving

Owned by: where-to-stay, today

Next: Keep facility presence separate from live capacity, wait times, or emergency dispatch.

Keep national-park, attraction, visitor, and closure context visible on nature-heavy routes.

Already subject-driving for park and route support.

Statuspromoted subject driving
Gate score7/7
Runtime rolesubject-driving

Owned by: route-check, today

Next: Do not imply live park access unless a daily closure or announcement monitor is added.

Use TAT place and event data to improve attraction, food-area, and museum context once auth/access is explicit.

Catalog-only because access/auth and field coverage need explicit connector handling.

Statuskeep catalog only
Gate score4/7
Runtime rolecatalog-only

Owned by: today, food-route

Next: Create a registered connector and map places/events to entity identity before any recommendation changes.

Provide fragmented registered-accommodation evidence without pretending there is one national hotel-license feed.

Catalog-only cluster until province resources can be normalized and coverage gaps displayed.

Statuskeep catalog only
Gate score4/7
Runtime rolecatalog-only

Owned by: where-to-stay

Next: Build province coverage metadata before attaching to stay confidence.

Improve Bangkok district-level air-quality confidence as a local supplement to national and global AQ feeds.

Health-checked only. Not yet subject-driving.

Statushealth checked support
Gate score5/7
Runtime rolehealth-checked

Owned by: today

Next: Map district observations and freshness before letting it rerank Bangkok guidance.

Add regional haze and cross-border hotspot context without replacing station-level Thai PM2.5 readings.

Catalog-only until hotspot fields, cadence, and geography are normalized.

Statuskeep catalog only
Gate score5/7
Runtime rolecatalog-only

Owned by: today

Next: Promote as regional context only; avoid station-level precision claims.

Let Bangkok drainage and flood conditions affect taxi, route, and hotel-area friction.

Already subject-driving for Bangkok condition and route support.

Statuspromoted subject driving
Gate score7/7
Runtime rolesubject-driving

Owned by: route-check, today, where-to-stay

Next: Keep the scope Bangkok-only and do not generalize it to all Thailand flood risk.

Use scheduled outage announcements as utility-risk context only if stable public announcement data can be normalized.

Catalog-only. Useful reference but not live grid status.

Statuskeep catalog only
Gate score4/7
Runtime rolecatalog-only

Owned by: where-to-stay, today

Next: Do not promote until announcement scope, timestamps, and location matching are reliable.

Display national Thai gold reference prices in THB per baht-weight and explain THB exchange-rate context.

Already subject-driving for the gold buying check.

Statuspromoted subject driving
Gate score7/7
Runtime rolesubject-driving

Owned by: gold-buying-check

Next: Keep city cards as buying-friction context, not separate official local prices.

Explain baht-weight, purity, and formula context without turning the site into a trading feed.

Reference context only.

Statusreference only
Gate score6/7
Runtime rolecatalog-only

Owned by: gold-buying-check

Next: Use for unit/formula explanation; do not promote as live retail price truth.