Promotion snapshot
Gate catalog and support sources before they become traveler-facing widgets.
Source promotion gate
This queue decides which catalog and support sources can move into observations, signals, and public recommendations. A source only gets promoted when it changes a real traveler decision and can be explained honestly.
Gate catalog and support sources before they become traveler-facing widgets.
All required gates must pass before a source becomes a traveler-facing widget or changes recommendation scores.
Could this source change where someone goes, stays, routes, ferries, eats, shops, or seeks help?
Is access public or permissioned in a way we can honestly automate and label?
Can we store an observed_at or published_at value that is separate from fetch time?
Does it map to a known signal such as AQI, ferry fragility, route friction, stay fit, food-route confidence, or gold context?
Does a named decision family own the source output?
Can the page say what this source proves and what it does not prove?
Does the source avoid private, dispatch, patient, case-level, or personally sensitive data?
These are the high-value Thailand source candidates from the source-gap work, with their current runtime role and next action.
| Candidate | Priority | Status | Decision family | Runtime role | Gates | Sources | Next step |
|---|---|---|---|---|---|---|---|
| exat-bangkok-expressway-friction. | Priority: high | Status: Promoted: decision-driving | Decision families: route-check, today | Current role: decision-driving | Gates: 7/7 | Sources: EXAT Data Catalog EXAT Traffic Surface |
Next step: Keep using as route-friction support; do not label it as guaranteed live traffic unless the connector verifies a current traffic observation. |
| doh-highway-traffic-route-friction. | Priority: high | Status: Promoted: decision-driving | Decision families: route-check, today | Current role: decision-driving | Gates: 7/7 | Sources: DOH Highway Traffic | Next step: Keep automation terms visible and avoid stronger claims than the public surface supports. |
| drr-rural-road-bridge-context. | Priority: high | Status: Keep catalog-only | Decision families: route-check | Current role: catalog-only | Gates: 5/7 | Sources: Department of Rural Roads road and bridge web services | Next step: Define road/bridge observation fields, then promote to health-checked before letting it affect route scores. |
| marine-berth-ferry-evidence. | Priority: high | Status: Promoted: decision-driving | Decision families: ferry-check, route-check | Current role: decision-driving | Gates: 7/7 | Sources: Marine Department Berth Status | Next step: Keep page copy clear that berth evidence is not operator seat availability. |
| tmd-maritime-ferry-risk. | Priority: high | Status: Promoted: decision-driving | Decision families: ferry-check, route-check, today | Current role: decision-driving | Gates: 7/7 | Sources: TMD Shipping Forecast | Next step: Add more granular Gulf/Andaman labels only if the source exposes stable regional fields. |
| hss-spa-license-confidence. | Priority: high | Status: Promoted: decision-driving | Decision families: where-to-stay, today | Current role: decision-driving | Gates: 7/7 | Sources: HSS Health Establishment Directory HSS Spa Premium |
Next step: Keep license confidence separate from reviews, opening hours, and service quality. |
| anamai-food-sanitation. | Priority: high | Status: Keep catalog-only | Decision families: food-route | Current role: catalog-only | Gates: 5/7 | Sources: Department of Health food sanitation and SAN standards | Next step: Map fields to restaurant-area confidence and keep it separate from taste, popularity, and current opening status. |
| moph-health-facility-fallback. | Priority: high | Status: Promoted: decision-driving | Decision families: where-to-stay, today | Current role: decision-driving | Gates: 7/7 | Sources: MOPH Health Facility Datasets | Next step: Keep facility presence separate from live capacity, wait times, or emergency dispatch. |
| dnp-park-tourism-closures. | Priority: high | Status: Promoted: decision-driving | Decision families: route-check, today | Current role: decision-driving | Gates: 7/7 | Sources: DNP Tourism Datasets | Next step: Do not imply live park access unless a daily closure or announcement monitor is added. |
| tat-data-api-v2-update. | Priority: high | Status: Keep catalog-only | Decision families: today, food-route | Current role: catalog-only | Gates: 4/7 | Sources: TAT Data API museum place and event detail | Next step: Create a registered connector and map places/events to entity identity before any recommendation changes. |
| provincial-hotel-registration-cluster. | Priority: medium | Status: Keep catalog-only | Decision families: where-to-stay | Current role: catalog-only | Gates: 4/7 | Sources: Provincial hotel registration GDC cluster | Next step: Build province coverage metadata before attaching to stay confidence. |
| bangkok-airbkk-district-aq. | Priority: medium | Status: Health-checked support | Decision families: today | Current role: health-checked | Gates: 5/7 | Sources: AirBKK | Next step: Map district observations and freshness before letting it rerank Bangkok guidance. |
| asmc-regional-haze-context. | Priority: medium | Status: Keep catalog-only | Decision families: today | Current role: catalog-only | Gates: 5/7 | Sources: ASMC regional haze and hotspot portal | Next step: Promote as regional context only; avoid station-level precision claims. |
| bangkok-flood-monitoring. | Priority: medium | Status: Promoted: decision-driving | Decision families: route-check, today, where-to-stay | Current role: decision-driving | Gates: 7/7 | Sources: Bangkok Flood Monitoring System | Next step: Keep the scope Bangkok-only and do not generalize it to all Thailand flood risk. |
| pea-mea-outage-announcements. | Priority: medium | Status: Keep catalog-only | Decision families: where-to-stay, today | Current role: catalog-only | Gates: 4/7 | Sources: PEA and MEA power outage announcements | Next step: Do not promote until announcement scope, timestamps, and location matching are reliable. |
| thai-gold-national-reference. | Priority: high | Status: Promoted: decision-driving | Decision families: gold-buying-check | Current role: decision-driving | Gates: 7/7 | Sources: Gold Traders Association Thailand gold prices Bank of Thailand API |
Next step: Keep city cards as buying-friction context, not separate official local prices. |
| tfex-gold-unit-reference. | Priority: medium | Status: Reference only | Decision families: gold-buying-check | Current role: catalog-only | Gates: 6/7 | Sources: TFEX Gold Futures contract and market data | Next step: Use for unit/formula explanation; do not promote as live retail price truth. |
high priority
Already decision-driving through route and place-fit signals.
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.
high priority
Already decision-driving for route support and transfer burden.
Owned by: route-check, today
Next: Keep automation terms visible and avoid stronger claims than the public surface supports.
high priority
Catalog-only until the schema is normalized into route support observations.
Owned by: route-check
Next: Define road/bridge observation fields, then promote to health-checked before letting it affect route scores.
high priority
Already decision-driving for ferry and route checks.
Owned by: ferry-check, route-check
Next: Keep page copy clear that berth evidence is not operator seat availability.
high priority
Already decision-driving for ferry and island route signals.
Owned by: ferry-check, route-check, today
Next: Add more granular Gulf/Andaman labels only if the source exposes stable regional fields.
high priority
Already decision-driving for wellness/stay support.
Owned by: where-to-stay, today
Next: Keep license confidence separate from reviews, opening hours, and service quality.
high priority
Catalog-only until establishment or area coverage can be mapped without overclaiming.
Owned by: food-route
Next: Map fields to restaurant-area confidence and keep it separate from taste, popularity, and current opening status.
high priority
Already decision-driving for stay and place confidence.
Owned by: where-to-stay, today
Next: Keep facility presence separate from live capacity, wait times, or emergency dispatch.
high priority
Already decision-driving for park and route support.
Owned by: route-check, today
Next: Do not imply live park access unless a daily closure or announcement monitor is added.
high priority
Catalog-only because access/auth and field coverage need explicit connector handling.
Owned by: today, food-route
Next: Create a registered connector and map places/events to entity identity before any recommendation changes.
medium priority
Catalog-only cluster until province resources can be normalized and coverage gaps displayed.
Owned by: where-to-stay
Next: Build province coverage metadata before attaching to stay confidence.
medium priority
Health-checked only; not yet decision-driving.
Owned by: today
Next: Map district observations and freshness before letting it rerank Bangkok guidance.
medium priority
Catalog-only until hotspot fields, cadence, and geography are normalized.
Owned by: today
Next: Promote as regional context only; avoid station-level precision claims.
medium priority
Already decision-driving for Bangkok condition and route support.
Owned by: route-check, today, where-to-stay
Next: Keep the scope Bangkok-only and do not generalize it to all Thailand flood risk.
medium priority
Catalog-only; useful reference but not live grid status.
Owned by: where-to-stay, today
Next: Do not promote until announcement scope, timestamps, and location matching are reliable.
high priority
Already decision-driving for the gold buying check.
Owned by: gold-buying-check
Next: Keep city cards as buying-friction context, not separate official local prices.
medium priority
Reference context only.
Owned by: gold-buying-check
Next: Use for unit/formula explanation; do not promote as live retail price truth.