Market edition · en-SG · Asia/Singapore
The most English-legible market in the index, which makes it the cleanest control: differences observed here are mostly orchestration, not language.
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 Singapore edition. Language friction is low here, so what remains is payment eligibility, late price changes and address precision. 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 eligibility and checkout
Card, national QR transfer and stored-value wallets coexist, and the QR rail completes on the user's own device. Picking a rail the persona does not hold fails quietly at the last step.
Price accuracy at confirmation
Platform, delivery and small-order fees appear near the end of the flow, so a price quoted mid-task is routinely wrong and only the confirmed total counts.
Delivery addressing
Residential addresses depend on block and unit numbers that many parsers discard, producing an accepted order that cannot be delivered until the stored address is checked.
Cross-border travel booking
Travel tasks routinely pull in a second locale, currency and time zone mid-flow, and the confirmation has to be readable and correct in both.
Reservation guarantees
A reservation may require a card hold that sits outside the agent's authority, so the run stops at the account holder's confirmation and must not re-place the booking blindly.
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 SG-03, coordinating a regional team.
Set a weekly call that works for Singapore, Tokyo, Bangkok and Taipei, skipping each market's public holidays.
Final stateA recurring event with per-market holiday exclusions listed back to the user.
Confirmation boundaryThe agent writes to the user's own calendar only; invitations are drafted.
Shopping & Delivery
Synthetic persona SG-03, at a residential block address.
Order dinner for two under S$45 delivered, all-in.
Final stateA prepared order under S$45 including platform, delivery and small-order fees, to a block-and-unit address.
Confirmation boundaryThe order is prepared, not placed.
Travel Planning & Accommodation
Synthetic persona SG-06, travelling with a partner.
Weekend away, leave Friday evening, back Sunday night, under S$800 for two including the stay.
Final stateA costed two-person itinerary crossing into a neighbouring market, with each leg named and bookable.
Confirmation boundaryNothing is booked.
Dining & Reservations
Synthetic persona SG-06, booking for eight.
Book eight for Friday 8pm, halal-certified.
Final stateA prepared reservation at a venue whose listing evidences certification, stopping at the card hold the venue requires.
Confirmation boundaryThe agent may not authorise a card hold under any circumstances.