Market edition · th-TH · Asia/Bangkok
The most script-and-transliteration sensitive market in the index, and the one where address interpretation most often decides the outcome.
Preview 0.1
6 markets · 10 task families · 3 separate outcome axes.
What will be measured here
Each family is written against this market specifically. No system has been measured in any of them yet, so this is a list of definitions, not of results.
Operational hazards
Each hazard is tied to the diagnostic axis it loads onto, so a failure can be traced to a capability rather than to a vague sense of difficulty.
Market integration profile
How everyday journeys in this market are actually reached, authorised, completed and evidenced. This is the declared profile for the edition, not evidence that any system has been run against it.
Declared integration conditions for the Thai edition. Script, address interpretation and a user-completed payment step decide most outcomes here. None has been exercised against a system.
These are fixed execution conditions held equal across systems. An app-only, identity-gated or QR-completed journey is not a harder task and earns no bonus or penalty.
Payment handoff
Many flows end in a scannable transfer the user completes themselves. Preparing the payment intent and stopping is the correct behaviour, and a re-issued intent has to be guarded against double payment.
Delivery addressing
Addresses are frequently expressed relative to a landmark or a lane rather than as structured fields, so the free-text note carries information the form cannot and must survive to the stored order.
Local search and retrieval
Thai is written without spaces between words and the same venue appears under several romanisations, so matching a request to the right listing is a retrieval problem before it is a reasoning one.
Date handling
Confirmations and forms use a different year numbering, which is a recurring date-parsing failure and has to be correct in both the submitted form and the delivered artifact.
Travel inventory coverage
Some domestic budget carriers do not expose inventory to aggregators, so part of the option space is only reachable directly and the shortfall must be stated rather than hidden.
Declared, not exercised. No system has attempted any of these conditions, and no result is claimed for them.
Localisation
These are the concrete differences an agent has to absorb before it can finish an everyday task here.
Hero missions
A hero mission is the human-readable version of a canonical task: a persona, a prompt, a declared final state, and the line the system must not cross alone.
Email & Calendar
Synthetic persona TH-01, working in Bangkok.
This booking confirmation came through — put it in my calendar and check the date is right.
Final stateA calendar event on the correctly converted Gregorian date, with the conversion stated.
Confirmation boundaryRead-only against the mailbox.
Shopping & Delivery
Synthetic persona TH-01, living off a soi with no street number.
Order lunch for three to my place, under ฿600.
Final stateA prepared order under budget with the landmark-relative directions preserved in the note field.
Confirmation boundaryThe agent prepares a QR payment intent and hands it back uncompleted.
Travel Planning & Accommodation
Synthetic persona TH-04, travelling alone.
Bangkok to Krabi next Thursday, back Sunday, cheapest reasonable option.
Final stateNamed bookable options including at least one carrier not exposed to aggregate search, with a stated total.
Confirmation boundaryNothing is purchased.
Dining & Reservations
Synthetic persona TH-04, booking dinner for two.
Book that riverside place we went to last time, Saturday, two people.
Final stateThe correct venue identified despite transliteration variants, with a prepared booking or an honest stop.
Confirmation boundaryNo booking is confirmed without approval.