# Read-only Configuration Intent Classification

<!-- auto-oncall-optimization-record
{
  "schemaVersion": "auto-oncall-optimization-record-v1",
  "optimizationId": "read-only-future-config-intent-2026-08-27",
  "problems": [
    {
      "problemId": "future-config-change-overrides-current-read-intent",
      "summary": "A request to read four current cluster configuration values was classified as operation_request because the ticket said a production change might be requested later.",
      "status": "optimized_unverified",
      "applicability": "Cloud tickets whose immediate request is a read-only lookup of exact current configuration values and that mention only a possible later mutation after review.",
      "issueKeys": ["TCID-13091"],
      "sourceRefs": [
        "https://tidb.atlassian.net/browse/TCID-13091#problem:future-config-change-overrides-current-read-intent"
      ],
      "signalTextIncludesAny": [
        "scenarioClass=operation_request",
        "possible future configuration change",
        "TCID-13091"
      ],
      "observedThrough": "2026-08-27",
      "effectiveAt": "2026-08-27T10:29:40Z",
      "verifiedAt": null,
      "attemptedAction": "Make the Scenario Classifier preserve the immediate read-only intent and select cluster_runtime_issue, evidence_assisted, and Clinic until Support is actually asked to perform or approve a mutation.",
      "evidenceUrl": "https://tidb.atlassian.net/browse/TCID-13091"
    }
  ]
}
-->

- Optimization ID: `read-only-future-config-intent-2026-08-27`
- Owner: Scenario Classifier
- Source: TCID-13091 read replay
- Implementation status: merged and deployed in live image `bf6b666986fe63d88f4eb8fcbf3a5f926dfa19a1`
- Effective status: `optimized_unverified`

## Bounded problem

TCID-13091 immediately asks Support to read four current PD and TiKV values.
The ticket says a production configuration change may be requested only after
those values are reviewed. A replay nevertheless classified the current request
as `operation_request + human_required`, so it skipped Clinic entirely.

## Candidate change

Make the classifier distinguish a current read from a possible later mutation.
The current lookup remains
`cluster_runtime_issue + evidence_assisted + clinic` with
`requiresPrivilegedAction=false`; a future configuration change becomes an
operation request only when Support is actually asked to perform or approve it.

## Verification evidence

Read replay `299f6cf7-ccfb-49ff-9675-ea8b2a850500` on 2026-08-27 classified
TCID-13091 as `cluster_runtime_issue + evidence_assisted + clinic`, with the
signals `current request is read-only configuration inspection` and `future
production mutation is not requested now`. The replay no longer entered
`operation_request`.

## Unresolved gaps

- No Jira internal comment refresh is authorized by this read-replay task.

## Next validation action

After the separate current-value acquisition problem is corrected, run the
authorized Jira internal-comment refresh and then promote this problem to
`optimized_verified` from the same case-specific evidence.