slug: spike-sh
provider: Spike.sh
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: 7
edges:
- tag: Incident Actions
  spec_file: spike-sh-incident-actions-api-openapi.yml
  capability_id: BC-4220.30
  capability_id_l1: BC-4220
  capability_name: Incident Response Management
  confidence: 0.9
  evidence: POST /incidents/acknowledge  acknowledgeIncidents  Acknowledge incident
  reason: Acknowledge, resolve, escalate, assign responders on production incidents — plainly incident
    response management.
- tag: Incidents
  spec_file: spike-sh-incidents-api-openapi.yml
  capability_id: BC-4220.30
  capability_id_l1: BC-4220
  capability_name: Incident Response Management
  confidence: 0.9
  evidence: GET /incidents/triggered  getTriggeredIncidents  Fetch triggered incidents
  reason: Lifecycle of production incidents for engineering on-call teams; incident detection, coordination
    and tracking.
- tag: Escalations
  spec_file: spike-sh-escalations-api-openapi.yml
  capability_id: BC-4220.30
  capability_id_l1: BC-4220
  capability_name: Incident Response Management
  confidence: 0.85
  evidence: POST /escalations/create  createEscalation  Create an escalation policy
  reason: Escalation policies tied to on-call rotations are core on-call response configuration within
    incident response management.
- tag: On-Call Schedules
  spec_file: spike-sh-on-call-schedules-api-openapi.yml
  capability_id: BC-4220.30
  capability_id_l1: BC-4220
  capability_name: Incident Response Management
  confidence: 0.82
  evidence: POST /on-calls createOnCall 'Create an on-call schedule'; 'Fetch all currently active on-call
    shifts'
  reason: Operations manage on-call rotations, layers and shifts for an incident management platform,
    which is the on-call response element of Incident Response Management.
- tag: Alert Rules
  spec_file: spike-sh-alert-rules-api-openapi.yml
  capability_id: BC-4220.30
  capability_id_l1: BC-4220
  capability_name: Incident Response Management
  confidence: 0.8
  evidence: GET /automation/rules  getAlertRules  Fetch all alert rules
  reason: Alerting rules within an incident management and on-call platform configure how production alerts
    route to responders — part of incident response management.
- tag: On-Call Overrides
  spec_file: spike-sh-on-call-overrides-api-openapi.yml
  capability_id: BC-4220.30
  capability_id_l1: BC-4220
  capability_name: Incident Response Management
  confidence: 0.8
  evidence: POST /on-calls/{oncall_id}/overrides/add  addOnCallOverride  Add an override
  reason: On-call schedule overrides govern who responds to production incidents, part of on-call response
    management.
- tag: Suppressed Incidents
  spec_file: spike-sh-suppressed-incidents-api-openapi.yml
  capability_id: BC-4220.30
  capability_id_l1: BC-4220
  capability_name: Incident Response Management
  confidence: 0.75
  evidence: GET /incidents/{counterId}/suppressed-incidents 'Fetch suppressed incidents'
  reason: Suppressed (deduplicated) production incidents under a parent incident are part of incident
    detection and coordination on this incident management platform.