slug: ford
provider: Ford
generated_by: planning/capability-mapping/scripts/classify_capabilities.py
model: claude-opus-5
frame:
- Automotive & Mobility
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: 2
edges:
- tag: Commands
  spec_file: ford-commands-api-openapi.yml
  capability_id: BC-3460
  capability_id_l1: BC-3460
  capability_name: Vehicle Connected Services Management
  confidence: 0.78
  evidence: POST .../{vehicleId}/lock "Issue a lock command"; POST .../{vehicleId}/startEngine "Remote
    start engine"; POST .../{vehicleId}/wake "Wake the vehicle from sleep"
  reason: Remote lock/unlock/start/stop/wake commands dispatched to enrolled vehicles and command-status
    polling are operations of an OEM connected-vehicle service platform. Sub-capability left null as remote
    command dispatch spans connectivity platform and customer-facing service operations.
- tag: Charging
  spec_file: ford-charging-api-openapi.yml
  capability_id: BC-3460
  capability_id_l1: BC-3460
  capability_name: Vehicle Connected Services Management
  confidence: 0.75
  evidence: POST /api/fordconnect/vehicles/v1/{vehicleId}/startCharge "Start charging an EV"; GET .../chargeSchedules
    "Get EV charge schedule"
  reason: Remote EV charge commands and charge/departure schedules issued to enrolled vehicles over the
    FordConnect cloud API are connected-vehicle service operations, not charge-point-operator network
    operations. Held at L1 because no sub-capability cleanly covers in-vehicle remote charge control.