slug: groove
provider: Groove
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: Tickets
  spec_file: groove-tickets-api-openapi.yml
  capability_id: BC-430.10
  capability_id_l1: BC-430
  capability_name: Customer Inquiry Management
  confidence: 0.9
  evidence: POST /tickets createTicket; PUT /tickets/{number}/state updateTicketState; PUT /tickets/{number}/assignee
    updateTicketAssignee
  reason: Help-desk ticket lifecycle with state and assignee routing is squarely inbound customer contact
    capture, routing and resolution.
- tag: Messages
  spec_file: groove-messages-api-openapi.yml
  capability_id: BC-430.10
  capability_id_l1: BC-430
  capability_name: Customer Inquiry Management
  confidence: 0.75
  evidence: GET /messages  listMessages  List messages ... POST /messages  createMessage — within "Groove
    help-desk resources including tickets, messages, customers, agents"
  reason: Messages here are help-desk conversation messages on support tickets — inbound/outbound customer
    contact handling, i.e. customer inquiry management. Slight ambiguity on sub-capability since messages
    are conversation artefacts rather than the inquiry record itself.