# Query evidence causal admission

<!-- auto-oncall-optimization-record
{
  "schemaVersion": "auto-oncall-optimization-record-v1",
  "optimizationId": "query-evidence-causal-admission-2026-08-06",
  "problems": [
    {
      "problemId": "topsql-or-plan-evidence-promoted-without-causal-linkage",
      "summary": "A scenario paragraph requiring SQL dominance, entity and time alignment, and workload magnitude was tested on partial-attribution and confirmed-cause cases. The baseline already made the same distinctions, so the paragraph produced no material target improvement and was reverted.",
      "status": "ineffective",
      "issueKeys": ["TCID-13001", "TCID-12986", "APID-29251", "TCID-12987"],
      "sourceRefs": [
        "https://tidb.atlassian.net/browse/TCID-13001#problem:query-candidate-not-linked-to-ddl",
        "https://tidb.atlassian.net/browse/TCID-12986#problem:query-explains-only-part-of-node-cpu"
      ],
      "signalTextIncludesAny": [
        "top sql promoted without entity and time linkage",
        "query explains only part of the resource differential",
        "execution count used without rows or workload magnitude"
      ],
      "observedThrough": "2026-08-06",
      "effectiveAt": null,
      "verifiedAt": "2026-08-06T13:52:00+08:00",
      "attemptedAction": "Add a query-execution scenario paragraph that promotes TopSQL, Slow Query, or a plan only when it is dominant, entity and time aligned, and explains the resource or latency path.",
      "evidenceUrl": null
    }
  ]
}
-->

- Owner: auto-oncall-services
- Implementation status: evaluated locally and reverted; not deployed
- Effective status: `ineffective`

## Verification

Single-variable A/B on two targets and two controls changed no causal status,
primary mechanism, uncertainty boundary, or action. See
[`../2026-08-06-investibook-scenario-rule-isolated-evaluation.md`](../2026-08-06-investibook-scenario-rule-isolated-evaluation.md).

## Next action

Do not repeat this paragraph-only action unless a new case shows that valid,
aligned SQL evidence reached the existing scenario synthesis and was still
misclassified.