slug: rootly
provider: Rootly
generated_by: planning/capability-mapping/scripts/classify_capabilities.py
model: claude-opus-5
frame:
- Software & Technology
min_confidence: 0.7
capability_model:
  source: https://github.com/vincentmakes/turbo-ea-capabilities
  license: CC-BY-4.0
  attribution: Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities,
    CC BY 4.0
  notice: NOTICE
edge_count: 3
edges:
- tag: Incidents
  spec_file: rootly-incidents-api-openapi.yml
  capability_id: BC-4220.30
  capability_id_l1: BC-4220
  capability_name: Incident Response Management
  confidence: 0.85
  evidence: POST /incidents/{id}/mitigate 'Mitigate incident'; POST /incidents/{id}/resolve 'Resolve incident'
  reason: Full lifecycle of production incidents including mitigation and resolution on an incident response
    platform — Incident Response Management.
- tag: Alerts
  spec_file: rootly-alerts-api-openapi.yml
  capability_id: BC-4220.30
  capability_id_l1: BC-4220
  capability_name: Incident Response Management
  confidence: 0.8
  evidence: POST /alerts/{id}/acknowledge 'Acknowledge alert'; POST /alerts/{id}/resolve 'Resolve alert'
    on the 'Rootly incident management REST API'
  reason: Alerts here are production monitoring alerts in an incident management platform, acknowledged
    and resolved by on-call responders — Incident Response Management, not financial-crime or marketing
    alerting.
- tag: Escalation Policies
  spec_file: rootly-escalation-policies-api-openapi.yml
  capability_id: BC-4220.30
  capability_id_l1: BC-4220
  capability_name: Incident Response Management
  confidence: 0.8
  evidence: GET /escalation-policies 'List escalation policies' in the 'Rootly incident management REST
    API'
  reason: Escalation policies define on-call routing and escalation for production incidents, a core element
    of Incident Response Management.