slug: stamped provider: Stamped 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: 3 edges: - tag: Customer Actions spec_file: stamped-customer-actions-api-openapi.yml capability_id: BC-420.40 capability_id_l1: BC-420 capability_name: Loyalty & Retention Management confidence: 0.95 evidence: POST .../customers/{customerId}/adjust-points 'Adjust Points'; 'Adjust VIP Tier'; 'Redeem Reward'; 'Void Coupon' reason: Operations directly administer a loyalty programme — point balances, VIP tiers, reward redemption and coupons — which is Loyalty & Retention Management. - tag: Customers spec_file: stamped-customers-api-openapi.yml capability_id: BC-420.10 capability_id_l1: BC-420 capability_name: Customer Data Management confidence: 0.8 evidence: POST /api/v3/merchant/shops/{shopId}/customers createCustomer Create Customer; GET .../customers/lookup lookupCustomer Lookup Customer; schemas CustomerRequest, CustomerResponse, CustomerAddress reason: The operations are straightforward CRUD plus lookup over customer master records held by the merchant (name, address, notification settings), which is customer data management rather than loyalty program mechanics. Mapped to CRM / Customer Data Management; some chance the intended sub-capability is loyalty-oriented since these records feed the loyalty engine, hence 0.8 not 0.95. - tag: Program Reporting spec_file: stamped-program-reporting-api-openapi.yml capability_id: BC-420.40 capability_id_l1: BC-420 capability_name: Loyalty & Retention Management confidence: 0.8 evidence: GET /api/v3/loyalty/shops/{shopId}/activities loyalty-reports-activities Filter Activities; GET /api/v3/loyalty/shops/{shopId}/rewards loyalty-reports-rewards Filter Rewards reason: The operations report on loyalty programme activities and rewards under the vendor's 'Loyalty Operations' domain, which is loyalty programme management. Some ambiguity because the tag is reporting-oriented (could be read as analytics), so 0.8.