Skip to content

AI-334: rename alert_confidence / triage_confidence → incident_likelihood#90

Merged
gbrewermc merged 2 commits into
mainfrom
gbrewer/ai-334-toolkit-incident-likelihood
May 22, 2026
Merged

AI-334: rename alert_confidence / triage_confidence → incident_likelihood#90
gbrewermc merged 2 commits into
mainfrom
gbrewer/ai-334-toolkit-incident-likelihood

Conversation

@gbrewermc
Copy link
Copy Markdown
Contributor

Summary

Toolkit-side docs rename matching the upstream ai-agent + mcp-server PR (monte-carlo-data/ai-agent#1115). The MCP alert_assessment tool now returns incident_likelihood instead of alert_confidence, and the remediation skill's stale triage_confidence typo is corrected at the same time. Linear ticket: AI-334.

Files touched

  • skills/automated-triage/SKILL.md — tool description + workflow steps
  • skills/automated-triage/references/triage-stages.md — output schema + troubleshooting-filter prose
  • skills/automated-triage/references/triage-example.md — fixture prose + summary-table header
  • skills/remediation/SKILL.md — tool-output description + urgency rules

Key decisions

  • HIGH/MEDIUM/LOW casing intentionally unchanged. ai-agent attempted title-casing the Literals mid-implementation and reverted: criticality and other axes the LLM sees in the same context are ALL-CAPS, so forcing one axis to title case creates a chronic "don't ALL-CAPS this one specific term" prompt-discipline burden. Toolkit docs follow the same convention — the field name changes, the value casing doesn't. See ai-agent PR #1115's "Key Decisions" section for the full reasoning.
  • triage_confidence typo fix in remediation/SKILL.md was scoped into this PR since it's the same concept the rename addresses (and a third-spelling drift that should be cleaned up at the same time).
  • No HIGH/MEDIUM filter sentences flipped. The "BOTH incident_likelihood AND alert_impact are MEDIUM or HIGH" phrasing keeps ALL-CAPS — values are unchanged.

Cutover

Toolkit PR is independent of monolith/FE timing. The MCP server side (ai-agent PR #1115) holds merge until the monolith team signals ready; once that ships, this toolkit PR can merge any time. Users on the released mc-agent-toolkit won't see field-name mismatches because the toolkit MCP tool description and the prose docs both flip together.

Verification

  • git grep -in "alert_confidence\|triage_confidence" returns zero hits across the repo.
  • Bare "confidence" references in the 4 triage-context files now consistently say "incident likelihood" where they describe the score axis.
  • No code or test changes; pure docs rename.

🤖 Generated with Claude Code

…hood

Toolkit-side docs rename matching the upstream ai-agent + mcp-server PR
(monte-carlo-data/ai-agent#1115). The MCP `alert_assessment` tool now
returns `incident_likelihood` instead of `alert_confidence`, and the
remediation skill's stale `triage_confidence` typo is corrected at the
same time.

Files touched:
- skills/automated-triage/SKILL.md — tool description + workflow steps
- skills/automated-triage/references/triage-stages.md — output schema +
  troubleshooting-filter prose
- skills/automated-triage/references/triage-example.md — fixture prose +
  summary-table header
- skills/remediation/SKILL.md — tool-output description + urgency rules

HIGH/MEDIUM/LOW casing intentionally unchanged — see the ai-agent PR's
Key Decisions section for the why (criticality and other axes stay
ALL-CAPS across the LLM context).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@linear
Copy link
Copy Markdown

linear Bot commented May 21, 2026

AI-334

…context

In the automated-triage docs, the score axis is consistently described
as "incident likelihood and potential impact" in agent prose now. This
pass updates the toolkit copy to match so the LLM sees the same noun
pair everywhere — workflow steps, schema bullets, filter sentences, and
the summary-table header column.

`alert_impact` field-name references in backticks stay unchanged
(that's the code identifier). HIGH/MEDIUM/LOW casing also unchanged.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@gbrewermc gbrewermc requested a review from santiagoaguiar May 22, 2026 10:00
@gbrewermc gbrewermc merged commit b523c5e into main May 22, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants