slug: autonomous-solutions
provider: VenHub
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: loyalty-points
  spec_file: autonomous-solutions-loyalty-points-api-openapi.yml
  capability_id: BC-420.40
  capability_id_l1: BC-420
  capability_name: Loyalty & Retention Management
  confidence: 0.88
  evidence: GET /users/loyalty/balance  Get Loyalty Balance; POST /users/loyalty/calculate-earnings  Calculate
    Potential Earnings
  reason: Explicit loyalty point balance and earnings calculation with LoyaltyPointsBalanceSchema — a
    consumer loyalty programme, i.e. Loyalty & Retention Management.
- tag: Deals
  spec_file: autonomous-solutions-deals-api-openapi.yml
  capability_id: BC-440.30
  capability_id_l1: BC-440
  capability_name: Discount & Promotion Management
  confidence: 0.85
  evidence: '"Check Deal Eligibility", "Apply Deal Reward", "Get Deal Redemption Status", "Get Promo Product
    Ids"; schemas DealRewardRetrieveSchema, DealTriggerRetrieveSchema'
  reason: Full lifecycle of promotional offers — creation, eligibility rules/triggers/constraints, reward
    application to a cart, and redemption tracking. That is Discount & Promotion Management; loyalty programme
    framing is possible but promotions is the better fit.
- tag: user profile
  spec_file: autonomous-solutions-user-profile-api-openapi.yml
  capability_id: BC-420.10
  capability_id_l1: BC-420
  capability_name: Customer Data Management
  confidence: 0.72
  evidence: GET /users/user/profile  Get User Profile; PATCH /users/user/profile  Update User Profile;
    UserProfileRetrieve
  reason: CRUD over the shopper's own profile record and profile image — management of customer master
    data for the consumer. Not identity/authentication (no credential or token operations), so Customer
    Data Management is the better fit than IAM.
- tag: Orders
  spec_file: autonomous-solutions-orders-api-openapi.yml
  capability_id: BC-520.40
  capability_id_l1: BC-520
  capability_name: Order Fulfilment Management
  confidence: 0.7
  evidence: POST /users/{user_id}/orders Create User Order; GET .../checkout-available Check User Order
    Available To Checkout; GET .../queue-position Get Order Queue Position View
  reason: Customer order capture, item amendment, checkout eligibility, delivery-bin dispensing and queue
    position — order capture through fulfilment orchestration in the smart store.