# Wetech Regional SaaS Default

<!-- auto-oncall-optimization-record
{
  "schemaVersion": "auto-oncall-optimization-record-v1",
  "optimizationId": "wetech-regional-saas-default-2026-08-18",
  "problems": [
    {
      "problemId": "wetech-regional-label-left-target-unresolved",
      "summary": "APID-29340 identified the Wetech environment as 亚太01 without naming an Order, Wallet, game, or other specific cluster, but the Scenario Router left the target unresolved instead of selecting the normal asia-prod SaaS cluster.",
      "status": "optimized_verified",
      "applicability": "Wetech tickets that identify a region or regional notation but do not name a specific candidate alias, business role, or full cluster name, and whose supplied target inventory contains the configured SaaS default for that region.",
      "issueKeys": ["APID-29340"],
      "sourceRefs": [
        "https://tidb.atlassian.net/browse/APID-29340#problem:wetech-regional-label-left-target-unresolved"
      ],
      "signalTextIncludesAny": [
        "亚太01",
        "diagnostic_wetech_target_missing",
        "regional label without specific cluster",
        "default SaaS cluster"
      ],
      "observedThrough": "2026-08-18",
      "effectiveAt": "2026-08-18T10:52:19Z",
      "verifiedAt": "2026-08-18T12:11:00Z",
      "attemptedAction": "Teach the Scenario Router to apply the supplied regional SaaS default after region selection when no specific candidate is named, while preserving exact unique matching for explicit aliases, business qualifiers, full names, and every cross-region or ambiguous case.",
      "evidenceUrl": "https://tidb.atlassian.net/browse/APID-29340"
    }
  ]
}
-->

- Owner: Scenario Router Wetech target selection
- Source: `APID-29340`
- Implementation status: merged in PR `#970`, deployed, and replay verified
- Effective status: `optimized_verified`

## Bounded problem

The frozen ticket says `亚太01` and describes one slow batched DELETE, but it
does not name Order, Wallet, game, or another specific Wetech cluster. The
Router received the full bounded inventory and still returned no canonical
target because several aliases ended in `01`. For Wetech's operating convention
this regional notation should use the normal Asia SaaS cluster, whose canonical
inventory alias is `SaaS01`.

## Intended change

- Keep region selection semantic and Router-owned.
- After selecting the region, use `SaaS01` for `asia-prod` or `SaaS` for
  `middle-east-prod` only when no specific candidate alias, business role, or
  full name appears and the exact default is present in the supplied inventory.
- Let explicit Order, Wallet, game, canonical alias, or full cluster names
  override the default and retain exact unique validation.
- Do not add a static `亚太01` alias, fuzzy deterministic mapping, or
  cross-region fallback.

## Verification status

Local Router prompt, exact-candidate parser, build, and optimization-record
tests are pending. Case-specific route probe, replay, deployment, and Jira
internal-comment refresh have not started.

## Unresolved gaps

This change only resolves the canonical target. It does not establish why the
DELETE was slow; Wetech evidence and the selected diagnostic scenarios still
own that conclusion.

## Next validation action

Run the local contract tests and a route-only real Router probe using the
frozen APID-29340 text and current candidate list. Then perform one historical
read replay and require `asia-prod/SaaS01` plus actual provider query events.