slug: hyperping
provider: Hyperping
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: 4
edges:
- tag: Monitors
  spec_file: hyperping-monitors-api-openapi.yml
  capability_id: BC-4220.20
  capability_id_l1: BC-4220
  capability_name: Observability Management
  confidence: 0.85
  evidence: POST /monitors createMonitor Create a new monitor; 'manage HTTP, ping, port, keyword, DNS,
    and browser monitors'
  reason: CRUD over uptime monitors (HTTP, ping, DNS, browser) is synthetic monitoring of the running
    service — observability management, not business alerting.
- tag: Health Checks
  spec_file: hyperping-health-checks-api-openapi.yml
  capability_id: BC-4220.20
  capability_id_l1: BC-4220
  capability_name: Observability Management
  confidence: 0.8
  evidence: POST /healthchecks createHealthcheck Create a new healthcheck; 'run scheduled-task healthchecks'
  reason: Configures heartbeat/healthcheck monitors for scheduled tasks on an uptime monitoring platform
    — synthetic monitoring of running services, i.e. observability management.
- tag: Outages
  spec_file: hyperping-outages-api-openapi.yml
  capability_id: BC-4220.30
  capability_id_l1: BC-4220
  capability_name: Incident Response Management
  confidence: 0.8
  evidence: POST /outages/{outage_uuid}/acknowledge  acknowledgeOutage; POST /outages/{outage_uuid}/escalate  escalateOutage  Escalate
    an outage to team members; resolveOutage
  reason: The operations are on-call detection-to-resolution handling of production outages (acknowledge,
    escalate to team, resolve), which is incident response for a running service rather than any business-domain
    'outage' concept.
- tag: Incidents
  spec_file: hyperping-incidents-api-openapi.yml
  capability_id: BC-4220.30
  capability_id_l1: BC-4220
  capability_name: Incident Response Management
  confidence: 0.75
  evidence: POST /incidents createIncident Create an incident; POST /incidents/{incident_uuid}/updates
    addIncidentUpdate Add an update to an incident
  reason: Creation and progressive updating of service incidents published on status pages matches incident
    detection, coordination and customer communication. Some overlap with public trust/status disclosure,
    so not maximal confidence.