slug: openstatus
provider: OpenStatus
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: Monitor
  spec_file: openstatus-monitor-api-openapi.yml
  capability_id: BC-4220.20
  capability_id_l1: BC-4220
  capability_name: Observability Management
  confidence: 0.85
  evidence: POST /monitor "Create a monitor"; POST /monitor/{id}/run "Trigger a monitor run"; "Manage
    HTTP, TCP, and DNS uptime monitors across 28 global regions"
  reason: Lifecycle of synthetic uptime monitors and their results — synthetic monitoring/observability
    of a running service.
- tag: Check
  spec_file: openstatus-check-api-openapi.yml
  capability_id: BC-4220.20
  capability_id_l1: BC-4220
  capability_name: Observability Management
  confidence: 0.8
  evidence: POST /check createCheck "Run an on-demand check"; "synthetic monitoring" ... "HTTP, TCP, and
    DNS uptime"
  reason: Executes an ad-hoc synthetic uptime probe; synthetic monitoring sits squarely in observability
    management. Minor ambiguity because the tag also carries a /whoami workspace call.
- tag: Incident
  spec_file: openstatus-incident-api-openapi.yml
  capability_id: BC-4220.30
  capability_id_l1: BC-4220
  capability_name: Incident Response Management
  confidence: 0.8
  evidence: GET /incident "List all incidents"; PUT /incident/{id} "Update an incident"
  reason: Incident records raised from uptime monitoring and worked to resolution — production incident
    response on a monitoring platform, not financial or HSE incidents.