slug: vivenu provider: vivenu 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: 14 edges: - tag: supports spec_file: vivenu-supports-api-openapi.yml capability_id: BC-430.10 capability_id_l1: BC-430 capability_name: Customer Inquiry Management confidence: 0.85 evidence: POST /api/support Create a support ticket; PUT /api/support/{id} Send a message; POST_Supports_ChangeSupportTicketPrio; POST_Supports_ChangeSupportTicketAssignee reason: The operations manage end-customer support tickets — creation, messaging, status, priority and assignee changes, plus 'look up the last transaction by email and resend the order confirmation'. This is inbound customer inquiry handling and resolution, not an internal IT service desk. - tag: Invoices spec_file: vivenu-invoices-api-openapi.yml capability_id: BC-200.30 capability_id_l1: BC-200 capability_name: Accounts Receivable Management confidence: 0.8 evidence: POST /api/invoices create_invoice_for_transaction 'Create invoice for transaction'; InvoiceResource, CustomerResource, TransactionResource reason: Generation, retrieval and update of customer invoices against sales transactions is customer invoicing, squarely Accounts Receivable Management. - tag: Users spec_file: vivenu-users-api-openapi.yml capability_id: BC-620.20 capability_id_l1: BC-620 capability_name: Identity & Access Management confidence: 0.8 evidence: POST /api/users/login login_a_user; POST /api/users/invite invite_a_user; PUT /api/users/password-reset/{token} set_password_after_reset; POST /api/users/access-seller change_seller_on_user reason: 'Back-office user account administration: login, token refresh, invitation, password reset, and granting/removing seller scope on a user — joiner-mover-leaver and authentication mechanics, i.e. identity and access management. Some operations (notification subscriptions, devices) sit outside IAM, hence 0.8.' - tag: Webhooks spec_file: vivenu-webhooks-api-openapi.yml capability_id: BC-4270.80 capability_id_l1: BC-4270 capability_name: Webhook & Event Subscription Management confidence: 0.8 evidence: POST /api/webhooks webhooks/create; PUT /api/webhook/{id} webhooks/update; POST_Webhooks_CreateANewWebhook reason: Full CRUD lifecycle over outbound webhook subscriptions, which the vendor describes as 'real-time webhooks' for its platform — this matches the frame's explicit Webhook & Event Subscription Management capability rather than being unmappable plumbing. - tag: API Keys spec_file: vivenu-api-keys-api-openapi.yml capability_id: BC-4270.40 capability_id_l1: BC-4270 capability_name: Developer Identity & Credential Management confidence: 0.78 evidence: POST /api/keys 'Api keys/create', schemas APIKeyResource, RedactedAPIKeyResource reason: Issuance and lifecycle of API credentials for platform consumers matches Developer Identity & Credential Management; could also be read as plain IAM plumbing, hence moderate confidence. - tag: Coupons spec_file: vivenu-coupons-api-openapi.yml capability_id: BC-440.30 capability_id_l1: BC-440 capability_name: Discount & Promotion Management confidence: 0.78 evidence: POST /api/coupon/generate coupons/generate; 'Coupon series/create coupon series'; 'Get coupon or voucher by code' reason: Operations create, generate and redeem coupon/voucher codes and coupon series — discount and promotional offer administration, which is Discount & Promotion Management rather than any technical concern. - tag: Customers spec_file: vivenu-customers-api-openapi.yml capability_id: BC-420.10 capability_id_l1: BC-420 capability_name: Customer Data Management confidence: 0.75 evidence: GET /api/customers/rich customers/list; 'Get all customer tags'; PUT /api/customers/{id} customers/update; CustomerResource reason: CRUD over customer master records plus tagging and customer-owned objects is customer data management; some surface is customer login/password (identity), hence not full confidence. - tag: Marketing spec_file: vivenu-marketing-api-openapi.yml capability_id: BC-400 capability_id_l1: BC-400 capability_name: Marketing Management confidence: 0.75 evidence: GET /api/marketing/campaigns marketing-campaigns/list; POST /api/marketing/campaigns marketing-campaigns/create; CampaignResource reason: Full lifecycle CRUD over marketing campaigns is clearly Marketing Management; the context does not say whether campaigns are demand-generation, digital or operational, so no L2 is asserted. - tag: Subscriptions spec_file: vivenu-subscriptions-api-openapi.yml capability_id: BC-4240 capability_id_l1: BC-4240 capability_name: Subscription Lifecycle Management confidence: 0.75 evidence: GET /api/subscriptions/plans get_all_subscription_plans; PUT /api/subscriptions/{id}/items/{itemId} update_subscription_items; GET /api/subscriptions/{id}/cycles get_all_subscription_cycles reason: Operations manage subscription plans, individual subscriptions, their items and billing cycles, including retrying a cycle transaction and creating a checkout for a draft subscription — i.e. the subscription commercial lifecycle. Evidence spans plan design, modification and provisioning, so only the L1 is asserted. - tag: price-tables spec_file: vivenu-price-tables-api-openapi.yml capability_id: BC-440.20 capability_id_l1: BC-440 capability_name: Price List Management confidence: 0.75 evidence: GET /api/price-tables "Get all price tables"; POST "Create a price table"; schema PriceTableResource reason: Maintenance of reusable price tables is price book / price list maintenance, matching BC-440.20 Price List Management. Slight residual doubt over whether these tables encode dynamic-pricing rules rather than static list prices. - tag: Checkout spec_file: vivenu-checkout-api-openapi.yml capability_id: BC-520.40 capability_id_l1: BC-520 capability_name: Order Fulfilment Management confidence: 0.72 evidence: '''Create a checkout'', ''Update checkout items'', ''Get all tickets for a checkout'', ''Resend confirmation mail'', POST_Checkout_ReserveACheckout' reason: Checkout creates, reserves, confirms and fulfils ticket orders including confirmation delivery — order capture and fulfilment orchestration; sales-order framing is also plausible, hence 0.72. - tag: Auth spec_file: vivenu-auth-api-openapi.yml capability_id: BC-620.20 capability_id_l1: BC-620 capability_name: Identity & Access Management confidence: 0.7 evidence: GET /api/auth/sso/{ssoId}/authorize 'Get redirected to sso provider'; POST /api/auth/token 'Exchange a token' reason: SSO redirect and token exchange is authentication plumbing; the nearest honest mapping is Identity & Access Management (federation), though such plumbing is often best left unmapped. - tag: distributor spec_file: vivenu-distributor-api-openapi.yml capability_id: BC-410.60 capability_id_l1: BC-410 capability_name: Channel Sales Management confidence: 0.7 evidence: GET /api/distributors Get distributor for sales channel; schema DistributorResource reason: Retrieval of distributor entities tied to a sales channel is indirect/channel sales administration. Only read operations and two endpoints, so confidence is tempered. - tag: subscription-plans spec_file: vivenu-subscription-plans-api-openapi.yml capability_id: BC-4240.10 capability_id_l1: BC-4240 capability_name: Plan & Entitlement Design confidence: 0.7 evidence: POST /api/subscriptions/plans Create a subscription plan; schema SubscriptionPlanResource reason: Creating and updating subscription plan definitions is plan design within the subscription commercial lifecycle. Only two operations and no entitlement detail, hence moderate confidence.