slug: phare
provider: Phare
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: phare-monitors-api-openapi.yml
  capability_id: BC-4220.20
  capability_id_l1: BC-4220
  capability_name: Observability Management
  confidence: 0.9
  evidence: 'GET /uptime/monitors; Uptime.Monitor.ProtocolEnum, Uptime.Monitor.RegionEnum; vendor: ''real‑time
    website and server uptime checks'''
  reason: CRUD over uptime checks/synthetic monitors with pause/resume and reports — squarely Observability
    Management (synthetic monitoring).
- tag: Incidents
  spec_file: phare-incidents-api-openapi.yml
  capability_id: BC-4220.30
  capability_id_l1: BC-4220
  capability_name: Incident Response Management
  confidence: 0.85
  evidence: POST /uptime/incidents/{incidentId}/recover  recoverUptimeIncident; 'Create an incident update';
    schema Uptime.Incident.ImpactEnum
  reason: Uptime-monitoring incident lifecycle with status updates and recovery — production incident
    response and customer communication, not ITSM ticketing for internal IT. Maps to SaaS Platform Operations
    / Incident Response Management.
- tag: Alert Rules
  spec_file: phare-alert-rules-api-openapi.yml
  capability_id: BC-4220.20
  capability_id_l1: BC-4220
  capability_name: Observability Management
  confidence: 0.75
  evidence: POST /alert-rules createUptimeAlertRule; schema Platform.Event.UptimeMonitorCertificateExpiring.AlertRuleSettings
  reason: Alert rules configure notifications from uptime monitoring checks — observability/monitoring
    configuration, not financial-crime or any other alerting. Some ambiguity with Incident Response Management
    given the uptime-incident event schema.
- tag: Status Pages
  spec_file: phare-status-pages-api-openapi.yml
  capability_id: BC-4290.30
  capability_id_l1: BC-4290
  capability_name: Trust Portal & Public Disclosure
  confidence: 0.75
  evidence: POST /uptime/status-pages  createUptimeStatusPage; GET .../current-status; Uptime.StatusPage.SubscriptionChannelEnum
  reason: Public status pages with subscriber channels are customer-facing public status disclosure —
    Trust Portal & Public Disclosure; alternative reading is service resilience commitment, hence not
    higher.