Market edition · zh-TW · Asia/Taipei
A convenience-store logistics market with a strong messaging-app layer. The hardest step is usually the last one, not the first.
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 Taiwan edition. The pattern here is that the last step, not the first, decides the outcome. 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.
Fulfilment routing
The order carries a chosen convenience-store branch. A branch near the wrong one of the persona's addresses is an accuracy failure that reads as a success unless the stored selection is checked.
Local services without an API
Restaurant and local-service booking often happens in a chat channel, so there is no structured response to parse and a supervised handoff is the only honest completion.
Receipts and tax artifacts
Checkout expects an invoice carrier identifier. Omitting it completes the purchase but misses the declared final state, and inventing one is never acceptable, so it is confirmed with the account holder.
Local text and search
A semantically correct answer in the wrong character set is a localization failure, and the same applies to the confirmation text a run leaves behind.
Out-of-band fulfilment
Payment on collection finishes the order off the agent's surface and under a deadline, so a confirmation number is a pending state and a retry can create a second order.
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 TW-02, coordinating with a Taipei supplier.
Confirm next week's site visit with the supplier and put it in my calendar.
Final stateA calendar event plus a drafted confirmation in traditional characters at the correct register.
Confirmation boundaryThe message is drafted, not sent.
Shopping & Delivery
Synthetic persona TW-02, who holds two saved addresses.
Order this and send it to the store near my apartment, not my office.
Final stateA prepared order with the correct pickup branch for the home address and the persona's digital invoice carrier attached.
Confirmation boundaryPayment happens at the store counter.
Travel Planning & Accommodation
Synthetic persona TW-05, travelling with family.
Three of us to Hualien over the long weekend, one room, under NT$18,000 total.
Final stateBookable transport and one room for three over the correct lunar-calendar dates, with a stated total.
Confirmation boundaryNothing is reserved.
Dining & Reservations
Synthetic persona TW-05, booking a local service.
Get me a quote for a deep clean of a two-bedroom apartment.
Final stateA drafted enquiry in traditional characters, or an explicit stop stating the provider only accepts messaging-app bookings.
Confirmation boundaryNo message is sent from the persona's account.