slug: augment
provider: Augment
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: Load Management
  spec_file: augment-load-management-api-openapi.yml
  capability_id: BC-2420
  capability_id_l1: BC-2420
  capability_name: Transport Operations Management
  confidence: 0.8
  evidence: POST /v2/loads  createOrUpdateLoad  Create or update load; POST /v2/loads/tracking  addTrackingEvent;
    schemas RouteStop, LoadStatus, TrackingEvent
  reason: Creation and lifecycle of freight loads with route stops, statuses and tracking events — core
    transport execution. Spans dispatch/load building and tracking, so L1 only; a shipment-visibility
    reading (BC-2510) also partly applies to the tracking endpoint.
- tag: Webhook Event Subscriptions
  spec_file: augment-webhook-event-subscriptions-api-openapi.yml
  capability_id: BC-4270.80
  capability_id_l1: BC-4270
  capability_name: Webhook & Event Subscription Management
  confidence: 0.8
  evidence: listWebhookEventTypes  List webhook event types; createWebhookSubscription  Create webhook
    subscription; testWebhookSubscription  Test webhook subscription
  reason: Lifecycle of outbound event subscriptions, event type catalogue and delivery testing — exactly
    the webhook & event subscription management capability. No freight-domain semantics in the operations
    themselves.
- tag: Carrier Management
  spec_file: augment-carrier-management-api-openapi.yml
  capability_id: BC-2450.20
  capability_id_l1: BC-2450
  capability_name: Carrier Procurement and Allocation Management
  confidence: 0.75
  evidence: GET /v1/carriers  getCarrierByIdentifier  Get carrier by DOT or MC number; POST /v1/carriers/bulk  bulkUpsertCarriers
  reason: Maintenance of carrier records (DOT/MC identifiers, carrier contacts, brokerage contacts) for
    a freight brokerage platform — carrier network/procurement master data. Could also be read as supplier
    master, but the freight-broker context favours carrier procurement and allocation.
- tag: Webhook Endpoints
  spec_file: augment-webhook-endpoints-api-openapi.yml
  capability_id: BC-4270.80
  capability_id_l1: BC-4270
  capability_name: Webhook & Event Subscription Management
  confidence: 0.75
  evidence: POST /v2/webhook-endpoints  createWebhookEndpoint  Create webhook endpoint; "you can self-manage
    the webhook endpoints that receive event"
  reason: Operations are pure CRUD over outbound webhook endpoint registrations (with auth headers/bearer
    tokens) exposed to API consumers — this is developer-platform webhook subscription lifecycle, not
    any freight capability. Mapped to the explicit webhook/event-subscription candidate rather than a
    logistics capability.