slug: turvo
provider: Turvo
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: 3
edges:
- tag: Tracking
  spec_file: turvo-tracking-api-openapi.yml
  capability_id: BC-2510.10
  capability_id_l1: BC-2510
  capability_name: Event Capture and Status Management
  confidence: 0.75
  evidence: GET /shipments/{id}/locationUpdates "List tracking updates for a shipment"; POST "Post a tracking
    update for a shipment"; schema LocationUpdate
  reason: Turvo is a TMS and this tag exposes posting and listing of shipment location/tracking updates
    — i.e. capture of shipment events and status for visibility. L1 shipment visibility is clear; the
    L2 split between event capture (posting updates) and tracking resolution (listing) is somewhat ambiguous,
    hence moderate confidence on the sub-capability.
- tag: Accounts
  spec_file: turvo-accounts-api-openapi.yml
  capability_id: BC-420.10
  capability_id_l1: BC-420
  capability_name: Customer Data Management
  confidence: 0.72
  evidence: GET /accounts/list  listAccounts; POST /accounts  createAccount; "accounts (customers)"; schemas
    Account, Contact, Address
  reason: The vendor explicitly equates accounts with customers, and the operations are CRUD over customer
    records with contacts and addresses — customer master data maintenance inside the TMS, not a transport
    execution capability.
- tag: Shipments
  spec_file: turvo-shipments-api-openapi.yml
  capability_id: BC-2420
  capability_id_l1: BC-2420
  capability_name: Transport Operations Management
  confidence: 0.7
  evidence: POST /shipments  createShipment; DELETE /shipments/{id}  cancelShipment  Cancel a shipment;
    schemas Shipment, Stop, LocationRef
  reason: Shipments with stops, updates and cancellation are the execution objects of a transportation
    management system, placing this in multimodal transport operations. The sub-capability (dispatch vs
    line-haul vs last-mile) is not distinguishable, so L1 only.