slug: vividcortex
provider: VividCortex
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: 2
edges:
- tag: Metrics
  spec_file: vividcortex-metrics-api-openapi.yml
  capability_id: BC-4220.20
  capability_id_l1: BC-4220
  capability_name: Observability Management
  confidence: 0.8
  evidence: GET /metrics  listMetrics  List active metrics; GET /metrics/series  Fetch metric time-series
    data
  reason: Listing active metrics and retrieving time-series data is squarely metrics-based observability
    of running systems, matching 'Logs, metrics, traces, and synthetic monitoring that make the running
    service understandable in production'.
- tag: Alerts
  spec_file: vividcortex-alerts-api-openapi.yml
  capability_id: BC-4220.20
  capability_id_l1: BC-4220
  capability_name: Observability Management
  confidence: 0.7
  evidence: GET /config/alerts  List alerts; GET /config/destinations  List alert destinations; GET /config/alert-opts/policy  List
    alert policies
  reason: These are monitoring alert definitions, policies and notification destinations for a database
    performance monitoring service — observability configuration, not financial-crime or business alerting.
    Some ambiguity between observability and incident response/IT operations monitoring keeps confidence
    moderate.