# Wetech Asia SaaS shorthand

Source: explicit operator instruction, 2026-09-05.

Apply only to Wetech OP tickets routed to the Wetech Provider with an explicit
`亚太01` / `亚太 01` or `亚太02` / `亚太 02` shorthand. Within that account,
these ordinarily mean Asia SaaS01 and SaaS02 respectively. Default to the exact
inventory candidate `asia-prod / SaaS01` or `asia-prod / SaaS02` and start
bounded read-only diagnosis without waiting for customer confirmation.

This is an authorized interpretation of supplied shorthand, not an arbitrary
regional default. Do not apply it to a Cloud org, another customer, bare
`亚太`, an unlisted number, or another region. An explicit business cluster
such as Order02 or Bet-Wallet02, or a full cluster name, takes precedence.
Conflicting region signals or absence of the mapped candidate from the current
inventory remains unresolved; never invent a target or fall back across regions.

Scenario Router owns both mapping and its confirmation. Preserve the assumption
in the selected scenario's reason; no additional wire field is needed. During
reconciliation, give the useful analysis scoped to the assumed cluster, then
ask the customer to confirm the intended cluster, for example:

> 本次先按亚太 SaaS02 集群分析，也请您确认“亚太02”是否指该集群。

Use SaaS01 for the 01 shorthand. Do not claim the customer already confirmed it.
If a subsequent explicit customer clarification has established the exact
cluster, do not ask the same question again. Do not substitute an internal
Support mapping task for this customer-intent confirmation.

The explicit question follows the existing L1 contract:
`decision=human_required`, `clarificationSimulation.required=true`, and one
focused `requestedContext` asking whether the shorthand means the assumed
cluster. Preserve the acquired facts; this final follow-up must not suppress
the initial diagnostic run or turn it into an evidence-free clarification.
This remains true when a separate internal query gap exists. Final Response
only words the Router-owned confirmation and never chooses the mapping.

The customer may see the safe name `亚太 SaaS01` / `亚太 SaaS02` for this
confirmation, but not the internal region key, datasource, endpoint, credentials,
or machine target reference. The internal queried-cluster line retains its
existing audience boundary. No production operation or customer publication
permission is granted by this default.