slug: deliverart
provider: Deliverart
generated_by: planning/capability-mapping/scripts/classify_capabilities.py
model: claude-opus-5
frame:
- Transportation & Logistics
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: Deliveries
  spec_file: deliverart-deliveries-api-openapi.yml
  capability_id: BC-2420.40
  capability_id_l1: BC-2420
  capability_name: Last-Mile Delivery Operations Management
  confidence: 0.85
  evidence: POST /delivery/{id}/take deliveriesTakeCharge, POST /delivery/{id}/start, POST /delivery/order/{id}/delivered
    — Order delivered, POST /delivery/{id}/end
  reason: Operations create a delivery, assign it to a rider ('take charge'), start it, mark orders delivered
    and end it — final-leg delivery execution with delivery confirmation, i.e. last-mile delivery operations.
- tag: Customers
  spec_file: deliverart-customers-api-openapi.yml
  capability_id: BC-420.10
  capability_id_l1: BC-420
  capability_name: Customer Data Management
  confidence: 0.78
  evidence: '"Customers — Create", "Customers — Update", "Customers — Delete", "GET /customer/{id}/order/list"'
  reason: Full lifecycle CRUD over customer records within a POS, plus retrieval of that customer's orders
    — a customer master data surface for the restaurant. Order listing is read-only context, not order
    management.
- tag: Orders
  spec_file: deliverart-orders-api-openapi.yml
  capability_id: BC-520.40
  capability_id_l1: BC-520
  capability_name: Order Fulfilment Management
  confidence: 0.75
  evidence: POST /pos/{id}/order/init  ordersInit; GET /order/{id}/delivery/detail  Orders — Detail /
    Delivery; POST /order/{id}/update/menu/items
  reason: Operations create, amend (items, payment, customer address) and abort customer delivery/take-away
    orders — order capture and fulfilment orchestration. Not a food-production capability; the cross-industry
    order fulfilment capability is the honest fit.
  recovered_from: vertical-agriculture-food-production-edges.json
- tag: Customer addresses
  spec_file: deliverart-customer-addresses-api-openapi.yml
  capability_id: BC-420.10
  capability_id_l1: BC-420
  capability_name: Customer Data Management
  confidence: 0.7
  evidence: '"POST /customer/{id}/address/create", "Customer addresses — Set as default"'
  reason: Maintains the customer's address book including default selection — customer master/contact
    data maintenance. Delivery routing is handled elsewhere in this API, so the honest reading is customer
    data management.