slug: emotive
provider: Emotive
generated_by: planning/capability-mapping/scripts/classify_capabilities.py
model: claude-opus-5
frame:
- Telecommunications
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: Single Segment
  spec_file: emotive-single-segment-api-openapi.yml
  capability_id: BC-420.20
  capability_id_l1: BC-420
  capability_name: Customer Segmentation Management
  confidence: 0.78
  evidence: POST /api/v2/segments 'Add a new Segment'; DELETE 'Archive (delete) a segment'; schema SegmentRule
  reason: Full lifecycle CRUD over rule-based marketing segments on an SMS marketing platform maps to
    customer segmentation management.
- tag: Tickets
  spec_file: emotive-tickets-api-openapi.yml
  capability_id: BC-430.10
  capability_id_l1: BC-430
  capability_name: Customer Inquiry Management
  confidence: 0.78
  evidence: GET /tickets controllers.tickets.search; POST /tickets/internal; schemas ticket, ticketEvent,
    status (Helpdesk Tickets API)
  reason: Creation, retrieval, update and event handling of helpdesk tickets is inbound customer contact/inquiry
    handling and resolution.
- tag: Segment Filter
  spec_file: emotive-segment-filter-api-openapi.yml
  capability_id: BC-420.20
  capability_id_l1: BC-420
  capability_name: Customer Segmentation Management
  confidence: 0.75
  evidence: GET /api/v2/segments — 'Retrieve a list of matching segments'; schemas SegmentRule, PaginatedSegments,
    SegmentObjectWithBroadcastCount
  reason: Segments with rules and broadcast counts on an SMS marketing platform are audience/customer
    segments used for targeting, i.e. customer segmentation management. Only a read/filter operation,
    hence moderate confidence.