slug: reputation
provider: Reputation
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: Surveys
  spec_file: reputation-surveys-api-openapi.yml
  capability_id: BC-430.50
  capability_id_l1: BC-430
  capability_name: Customer Feedback Management
  confidence: 0.9
  evidence: GET /v3/survey-results  Get Survey Results; GET /v3/surveys3-templates  Get Survey Templates;
    POST /v3/surveys-link  Get Survey URL
  reason: The surface runs customer surveys end to end — templates, distribution links, and result capture
    — which is squarely Customer Feedback Management (surveys, NPS, voice-of-customer).
- tag: Reviews
  spec_file: reputation-reviews-api-openapi.yml
  capability_id: BC-430.50
  capability_id_l1: BC-430
  capability_name: Customer Feedback Management
  confidence: 0.72
  evidence: GET /v3/reviews  Get Reviews; POST /v3/reviews/{reviewID}/respond  Respond To Review; "REST
    API for aggregating customer feedback, managing reviews"
  reason: Operations aggregate customer reviews and post responses to them — voice-of-customer capture
    and closing the loop with customers, which sits under Customer Feedback Management. Some ambiguity
    with brand/reputation marketing, hence moderate confidence.
- tag: Tenants
  spec_file: reputation-tenants-api-openapi.yml
  capability_id: BC-4230.10
  capability_id_l1: BC-4230
  capability_name: Tenant Provisioning & Lifecycle
  confidence: 0.72
  evidence: POST /v3/tenants  Save Tenant; PUT /v3/tenants/{tenantID}/pause  Pause Tenant; PUT /v3/tenants/{tenantID}/unpause  Unpause
    Tenant
  reason: Create, retrieve, pause and unpause tenants in the multi-tenant platform matches tenant provisioning
    and lifecycle (creation, suspension). Confidence tempered because no schemas are shown and tenant
    could partly mean customer account administration.
- tag: Tickets
  spec_file: reputation-tickets-api-openapi.yml
  capability_id: BC-430
  capability_id_l1: BC-430
  capability_name: Customer Service Management
  confidence: 0.7
  evidence: GET /v3/tickets  Get Tickets; GET /v3/ticket-queues  Get Queues; GET /v3/ticket-stages  Get
    Stages; GET /v3/ticket-types  Get Ticket Definitions
  reason: Ticket, queue, stage and type operations are case management over customer issues raised from
    feedback/reviews, i.e. Customer Service Management. Cannot tell from the evidence whether this is
    inquiry routing or complaint handling, so no L2 is asserted.