Overview

AUTO-TOW-019, Select Nearest Qualified Operator, compares candidate towing operators using proximity, certification match, current job load, safety history, and customer rating.

Decision ID

AUTO-TOW-019

Decision Name

Select Nearest Qualified Operator

Industry Profile

auto-towing-select-nearest-qualified-opera-auto-tow-019 version 1.0.0

Default Profile

balanced

Runnable Scenario

standard

Catalog

DKR-AUTO-RUNTIME-001, version 13.9.3

API Compatibility

7.4.0 or later catalog execution flow

Understanding This Decision

Select Nearest Qualified Operator helps a towing operation compare available candidate operators before dispatching one to an incident. The decision is useful when dispatch teams need a repeatable recommendation that balances proximity, qualification fit, operator workload, safety history, and recent customer service performance.

Architecture

1. Request a token from the Identity service.
2. Use the returned jwtToken as the bearer token.
3. Load the catalog and decision detail from DKS.
4. Build a Prepared Decision Input using canonical criterion IDs.
5. Execute the decision through DDE.
6. Use X-Request-Id and X-Correlation-Id for tracing across DDE and DKS.

Authentication

Request a secure session token from Identity. The current token response field is jwtToken.

POST https://identity.vinquery.com/connect/token
Content-Type: application/json

{
  "clientId": "{clientId}",
  "clientSecret": "{clientSecret}",
  "audience": "vinquery:api:decisioq"
}

Catalog Discovery

Use DKS to discover the catalog and then load complete metadata for AUTO-TOW-019.

GET https://dks.vinquery.com/decisioncatalog
Authorization: Bearer {jwtToken}

GET https://dks.vinquery.com/decisioncatalog/decisions/AUTO-TOW-019
Authorization: Bearer {jwtToken}

Criteria

Criterion IDs are intentionally stable machine identifiers. Display labels are for users; request values should be keyed by canonical criterionId.

Constraint Processing

This decision currently has no catalog-defined hard constraints. All validated candidates proceed to criteria-based ranking.

{
  "constraintSummary": {
    "definedConstraintCount": 0,
    "activeConstraintCount": 0,
    "eligibleOptionCount": 3,
    "excludedOptionCount": 0,
    "eligibleOptions": [
      "OPTION-001",
      "OPTION-002",
      "OPTION-003"
    ],
    "excludedOptions": []
  }
}

const constraints = decisionDetail.constraints || [];
if (constraints.length === 0) {
  // No catalog-defined hard constraints.
  // Submit all validated candidates for criteria-based ranking.
}

const summary = response.constraintSummary;
const excluded = response.decisionResult?.excludedOptions || [];

Excluded candidates do not participate in ranking because hard constraints are evaluated before scoring. For AUTO-TOW-019, no candidates are excluded by catalog-defined constraints because DKS currently defines none for this decision.

Industry Profile

The active industry profile uses $.towRequests as the options path, $.optionId as the option ID, and $.name as the option display name.

{
  "requestContext": {
    "sourceSystem": "auto-towing-demo",
    "correlationId": "auto-tow-019-demo-001"
  },
  "towRequests": [
    {
      "optionId": "OPTION-001",
      "name": "Operator North Zone",
      "assessment": {
        "proximityScore": 88,
        "certificationMatchScore": 88,
        "safetyHistoryScore": 88,
        "customerRatingScore": 88
      },
      "resource": {
        "allocation": {
          "currentJobLoad": 1
        }
      }
    }
  ]
}

{
  "optionId": "OPTION-001",
  "name": "Operator North Zone",
  "values": {
    "proximity_score": 88,
    "certification_match_score": 88,
    "current_job_load": 1,
    "safety_history_score": 88,
    "customer_rating_score": 88
  }
}

Profiles and Scenarios

A profile changes criterion weights. A scenario describes the operating context for the execution. The active DKS catalog exposes these choices with the decision detail response.

Prepared Input

For Prepared Decision Input, send decisionId, selected profile/scenario IDs, and option values keyed by canonical criterion ID.

{
  "decisionId": "AUTO-TOW-019",
  "profileId": "balanced",
  "scenarioId": "standard",
  "algorithm": "TOPSIS",
  "weightStrategy": "Manual",
  "runSensitivity": false,
  "requestContext": {
    "correlationId": "auto-tow-019-demo-001"
  },
  "options": [
    {
      "optionId": "OPTION-001",
      "name": "Operator North Zone",
      "values": {
        "proximity_score": 88,
        "certification_match_score": 88,
        "current_job_load": 1,
        "safety_history_score": 88,
        "customer_rating_score": 88
      }
    },
    {
      "optionId": "OPTION-002",
      "name": "Operator Central Zone",
      "values": {
        "proximity_score": 80,
        "certification_match_score": 80,
        "current_job_load": 3,
        "safety_history_score": 80,
        "customer_rating_score": 80
      }
    },
    {
      "optionId": "OPTION-003",
      "name": "Operator East Zone",
      "values": {
        "proximity_score": 72,
        "certification_match_score": 72,
        "current_job_load": 5,
        "safety_history_score": 72,
        "customer_rating_score": 72
      }
    }
  ]
}

Execute

curl -X POST "https://dde.vinquery.com/api/v1/decide" \
  -H "Authorization: Bearer ${DECISIOQ_TOKEN}" \
  -H "Content-Type: application/json" \
  -H "X-Correlation-Id: auto-tow-019-demo-001" \
  --data @auto-tow-019-execute.json

The Decision Engine validates the request, retrieves authoritative criteria, constraints, profiles, scenarios, and validation metadata from DKS, applies hard constraints, ranks eligible options, and returns the decision result plus execution metadata.

Interpret the Result

The successful response is centered on decisionResult. The winner and ranking are deterministic outputs; optional explanation fields add context but do not change the ranking.

{
  "service": "decisioq",
  "version": "7.6.3",
  "requestId": "0HNE...",
  "operation": "Decide",
  "success": true,
  "decisionType": "AUTO-TOW-019",
  "decisionVersion": "13.9.3",
  "timestampUtc": "2026-07-18T00:00:00Z",
  "decisionResult": {
    "winner": "OPTION-001",
    "confidence": 72.4,
    "ranking": [
      {
        "optionId": "OPTION-001",
        "score": 0.8421,
        "breakdown": {
          "proximity_score": 0.25,
          "certification_match_score": 0.25,
          "current_job_load": 0.20,
          "safety_history_score": 0.15,
          "customer_rating_score": 0.15
        },
        "normalizationBreakdown": {}
      }
    ],
    "excludedOptions": [],
    "explanation": {
      "summary": "Operator North Zone ranked highest based on the submitted towing dispatch criteria.",
      "strengths": [],
      "weaknesses": [],
      "exclusions": []
    }
  },
  "constraintSummary": {
    "definedConstraintCount": 0,
    "activeConstraintCount": 0,
    "eligibleOptionCount": 3,
    "excludedOptionCount": 0,
    "eligibleOptions": [
    "OPTION-001",
    "OPTION-002",
    "OPTION-003"
    ],
    "excludedOptions": []
  },
  "warnings": [],
  "requestContext": {
    "correlationId": "auto-tow-019-demo-001"
  }
}

Sensitivity Analysis

Set runSensitivity to true on catalog execution when the client wants recommendation-stability information in the same response. The sensitivity engine perturbs criterion weights by controlled factors and reports whether the winner remains stable.

{
  "sensitivityResult": {
    "stableWinner": true,
    "winner": "OPTION-001",
    "mostSensitiveCriterion": "proximity_score",
    "confidence": 95,
    "criterionImpacts": {
      "proximity_score": 0.1842
    },
    "winnerChangeCounts": {
      "proximity_score": 0
    }
  }
}

Use sensitivity output to decide whether a recommendation is robust enough for automation or should be reviewed by a person.

Explanation of Decision Result

Every successful response can include deterministic explanation text under decisionResult.explanation and explanation. If the optional AI layer is enabled, the response may also include an ai block with structured business-language explanation fields.

{
  "ai": {
    "enabled": true,
    "generated": true,
    "schemaValidated": true,
    "explanation": {
      "summary": "The selected towing operator provided the strongest overall dispatch fit.",
      "whyRecommended": "It combined strong proximity and certification match with low current job load, strong safety history, and strong customer rating.",
      "keyDrivers": [],
      "tradeoffs": [],
      "competitors": [],
      "sensitivitySummary": "Sensitivity analysis was not included in this response.",
      "scenarioSummary": "The standard dispatch scenario was selected.",
      "risks": [],
      "nextSteps": [],
      "assumptions": []
    }
  }
}

Tracing and Logs

Use request identifiers to connect client, catalog, and execution activity during support or integration testing.

X-Request-Id

Optional client-supplied request ID. If omitted, the server generates one.

X-Correlation-Id

Optional client correlation value propagated from DDE to DKS.

requestContext.correlationId

Optional payload value echoed in the response and used for tracing.

executionTrace

Advanced execution metadata including selected profile, selected scenario, effective weights, and applied constraints.

Code Examples

These examples demonstrate the current DecisioQ flow:

1. Request jwtToken from https://identity.vinquery.com/connect/token.
2. Load AUTO-TOW-019 metadata from https://dks.vinquery.com/decisioncatalog/decisions/AUTO-TOW-019.
3. Execute a Prepared Decision Input at https://dde.vinquery.com/api/v1/decide.

Set these environment variables before running any companion example:

DECISIOQ_CLIENT_ID
DECISIOQ_CLIENT_SECRET

Optional:
DECISIOQ_IDENTITY_URL=https://identity.vinquery.com/connect/token
DECISIOQ_DKS_URL=https://dks.vinquery.com
DECISIOQ_DDE_URL=https://dde.vinquery.com

Download the source files directly:

Troubleshooting

Production Checklist