# Wetech Cloud SKA org context

<!-- auto-oncall-optimization-record
{
  "schemaVersion": "auto-oncall-optimization-record-v1",
  "optimizationId": "wetech-cloud-ska-org-context-2026-08-21",
  "problems": [
    {
      "problemId": "wetech-cloud-org-context-not-recalled",
      "summary": "A Wetech Cloud direct-answer ticket can omit the customer name and therefore receive a generic Starter-first answer even though the typed org identifies an SKA environment that is primarily Dedicated.",
      "status": "optimized_verified",
      "applicability": "Tickets whose typed orgId is exactly 1372813089209061633.",
      "issueKeys": ["ST-2904"],
      "sourceRefs": ["https://tidb.atlassian.net/browse/ST-2904#problem:wetech-cloud-org-context-not-recalled"],
      "signalTextIncludesAny": ["1372813089209061633", "Wetech Cloud", "Starter-first answer", "primarily Dedicated"],
      "observedThrough": "2026-08-21",
      "effectiveAt": "2026-08-21T08:26:18Z",
      "verifiedAt": "2026-08-21T08:36:52Z",
      "attemptedAction": "Recall exact-org customer knowledge for Wetech Cloud, keep the non-empty-orgId Cloud boundary, lead capability answers with the Dedicated path, and keep SKA and org identity internal-only.",
      "evidenceUrl": "https://tidb.atlassian.net/browse/ST-2904?focusedCommentId=23654378"
    }
  ]
}
-->

- Owner: repository product knowledge selected by Primary Analysis
- Source: ST-2904 and the exact typed Jira org mapping
- Implementation status: deployed to staging and verified by historical replay
- Effective status: `optimized_verified`

## Bounded problem

ST-2904 has a non-empty typed `orgId` but no Account Alias or Wetech name in its
question. Searching product knowledge only with visible semantic terms cannot
recall customer-specific environment context, so a generic Cloud answer can
make Starter the main path.

## Implemented change

Primary Analysis now performs one exact-literal `orgId` lookup in the bounded
product-knowledge index. The exact mapping identifies Wetech Cloud as an
internal SKA context whose environment is primarily Dedicated. Applicable
capability and integration answers lead with Dedicated and use one focused tier
confirmation only when the exact tier materially changes the conclusion.

The mapping does not reclassify Cloud as Wetech OP, does not select a Provider,
and does not expose the org ID, SKA status, or internal importance to customers.
Direct product Q&A does not query Clinic to infer the tier.

## Replay evidence

Staging read replay `b73e7d3c-9984-4844-835c-1b4b6f3cc599` on image
`dce3ea31c56ab2469cff61f3a0d0c1ec02f75cf6` recalled and read the exact-org
topic and did not query a Provider. However, its first path still described AWS
Starter before Dedicated, so the answer-default criterion did not pass and no
write replay was issued. The topic now makes the first path, heading, and
recommendation explicitly Dedicated-applicable; the problem remains
`candidate`.

The later read replay `01b22769-620d-4cd4-92ff-44ea5d05f9d6` on image
`2dbd19b8e843af1fc05db891f1dc967d40220409` correctly led with the Dedicated
TiDB Vector path and kept `evidenceProvider=none`, but it expressed the v8.4+
and TiFlash requirements only as conditions. It did not end with the requested
customer confirmation. The topic now states that a conditional sentence is not
a substitute for the explicit closing confirmation; no write replay was
issued and the problem remains `candidate`.

Final staging read replay `e8ea96f8-6af6-4313-9ab6-e58322a9b3d1` on image
`55db24f4f654a8eaacd3a2588772a91dc7df6e8e` selected both exact-org and Dify
topics, led with the Dedicated-applicable path, kept the internal org ID and SKA
context out of the customer reply, requested the precise tier/version/TiFlash
confirmation, and did not query Clinic or Wetech OP. It used
`evidenceProvider=none`; the Judge classified the answer as `ai_better` with no
AI gap.

Write replay `f5073bc8-d9d9-4934-a75c-33d40dc94c35` created internal Jira
comment `23654378`. Because that run's stochastic final wording omitted the
closing confirmation, the verified read draft was restored to that exact
comment in place. Readback confirmed Dedicated-first guidance, the focused
customer confirmation, `public=false`, and the internal-comment property. The
database run and Judge history were not rewritten and retain the original
write-run wording gap.

## Next validation action

Monitor later tickets for this exact org mapping and keep the customer-specific
metadata internal while preserving the non-empty-`orgId` Cloud boundary.