DecisioQ System Architecture Decision Concepts Decision List API Guide Developer Center Decision Studio Quick Start Playground End-to-End Examples

AUTO-INS-036 End-to-End Example

Determine Salvage Recovery Strategy using Identity, the secured Knowledge Catalog, DKS token propagation, catalog constraints, and Prepared Decision Input execution.

Automotive Auto Insurance Salvage & Recovery TOPSIS
IdentityIssue bearer token
CatalogDiscover decision metadata
ProfileSelect weights and scenario
ExecuteApply constraints and rank
ExplainReview result context

Overview

AUTO-INS-036, Determine Salvage Recovery Strategy, selects the best salvage recovery strategy using recovery value, disposal speed, title complexity, storage cost, and compliance.

Decision ID
AUTO-INS-036
Decision Name
Determine Salvage Recovery Strategy
Industry Profile
auto-insurance-determine-salvage-recovery-str-auto-ins-036 version 1.0.0
Default Profile
balanced
Default Scenario
standard
Catalog
DKR-AUTO-RUNTIME-001, version 13.9.3
The deterministic Decision Engine ranks eligible salvage options. AI explanation text, when returned, is explanatory only and must not choose, rerank, or override the deterministic result.

Understanding This Decision

Determine Salvage Recovery Strategy helps Salvage & Recovery teams compare candidate salvage options when expected recovery value must be weighed against storage cost, title complexity, disposal speed, and environmental compliance readiness.

Business question

Which salvage option should be recommended for determine salvage recovery strategy in the selected Auto Insurance context?

Expected outcome

A recommended salvage option or ranked set of salvage options with the criteria and constraints that most influenced the result.

Typical users

Operations managers, salvage recovery teams, claims operations teams, compliance reviewers, and integration teams building insurance recovery workflows.

Decision boundary

Use this decision to compare submitted salvage options. It supports business judgment and does not replace required legal, title, compliance, or management approvals.

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.
Token propagation: when DDE needs authoritative decision metadata during execution, it forwards the caller's bearer token to DKS with the request identifiers. This lets the catalog and execution records share the same security and tracing context.

Authentication

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

Token request
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-INS-036.

Catalog
GET https://dks.vinquery.com/decisioncatalog
Authorization: Bearer {jwtToken}
Decision Detail
GET https://dks.vinquery.com/decisioncatalog/decisions/AUTO-INS-036
Authorization: Bearer {jwtToken}

Criteria

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

Criterion IDNameDirectionWeightValidation
salvage_recovery_valueSalvage Recovery Valuemaximize30non_negative_currency
storage_costStorage Costminimize15non_negative_currency
title_complexity_scoreTitle Complexity Scoreminimize20score_0_to_100
disposal_speed_scoreDisposal Speed Scoremaximize20score_0_to_100
environmental_compliance_scoreEnvironmental Compliance Scoremaximize15score_0_to_100

Constraint Processing

This decision includes one catalog-defined hard constraint. DKS returns the constraint with the decision detail, and DDE evaluates it before criteria-based ranking.

Verified Catalog ConstraintStatusEffect
AUTO-INS-036-ENVIRONMENTAL-COMPLIANCE-MIN-70Hard, enabled, mandatoryRequires environmental_compliance_score >= 70 before a candidate can participate in ranking.
Eligible and Excluded Candidates
{
  "constraintSummary": {
    "definedConstraintCount": 1,
    "activeConstraintCount": 1,
    "eligibleOptionCount": 2,
    "excludedOptionCount": 1,
    "eligibleOptions": [
      "option-1",
      "option-2"
    ],
    "excludedOptions": [
      {
        "optionId": "option-3",
        "reasons": [
          "Environmental compliance score is below the minimum threshold of 70."
        ]
      }
    ]
  }
}
Constraint Handling Pattern
const constraints = decisionDetail.constraints || [];
if (constraints.length > 0) {
  // DDE applies catalog constraints before ranking.
  // Excluded candidates appear in response.constraintSummary.excludedOptions.
}

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-INS-036, option-3 is excluded from the showcase sample because its environmental compliance score is below the catalog threshold.

Industry Profile

The generated integration asset uses $.claims as the business options path, $.optionId as the option ID, and $.name as the option display name.

Business Data PathCriterion ID
option.financial.salvageRecoveryValuesalvage_recovery_value
option.financial.storageCoststorage_cost
option.assessment.titleComplexityScoretitle_complexity_score
option.assessment.disposalSpeedScoredisposal_speed_score
option.risk.environmentalComplianceScoreenvironmental_compliance_score
Business Data Fragment
{
  "claims": [
    {
      "optionId": "option-1",
      "name": "Auction Salvage Sale",
      "financial": {
        "salvageRecoveryValue": 18000,
        "storageCost": 3600
      },
      "assessment": {
        "titleComplexityScore": 25,
        "disposalSpeedScore": 82
      },
      "risk": {
        "environmentalComplianceScore": 82
      }
    }
  ]
}
Prepared Option Values
{
  "optionId": "option-1",
  "name": "Auction Salvage Sale",
  "values": {
    "salvage_recovery_value": 18000,
    "storage_cost": 3600,
    "title_complexity_score": 25,
    "disposal_speed_score": 82,
    "environmental_compliance_score": 82
  }
}

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.

Profile IDNamePurpose
balancedBalancedPreserves the default criterion priorities for this insurance decision.
cost_controlCost ControlPlaces stronger emphasis on claim cost, premium adequacy, reserves, settlements, and expense control.
risk_averseRisk AversePlaces stronger emphasis on liability, coverage, fraud, compliance, severity, and legal exposure.
customer_focusedCustomer FocusedPlaces stronger emphasis on customer impact, service speed, retention, mobility, and experience quality.
Scenario IDNameUse When
standardStandard Claim HandlingNormal operating conditions with ordinary claim volume and complete claim information.
catastrophe_eventCatastrophe EventHigh-volume event conditions where triage speed and severity prioritization become more important.
coverage_uncertaintyCoverage UncertaintyPolicy, liability, eligibility, or loss facts are incomplete and additional review is required.
customer_escalationCustomer EscalationCustomer sensitivity is elevated because of complaint risk, hardship, or service-level commitments.

Prepared Input

For Prepared Decision Input, send decisionId, selected profile/scenario IDs, and option values keyed by canonical criterion ID. This request intentionally does not duplicate values under display labels.

Prepared Decision Input JSON
{
  "decisionId": "AUTO-INS-036",
  "profileId": "balanced",
  "scenarioId": "standard",
  "algorithm": "TOPSIS",
  "weightStrategy": "Manual",
  "runSensitivity": false,
  "requestContext": {
    "correlationId": "auto-ins-036-demo-001"
  },
  "options": [
    {
      "optionId": "option-1",
      "name": "Auction Salvage Sale",
      "values": {
        "salvage_recovery_value": 18000,
        "storage_cost": 3600,
        "title_complexity_score": 25,
        "disposal_speed_score": 82,
        "environmental_compliance_score": 75
      }
    },
    {
      "optionId": "option-2",
      "name": "Direct Recycler Sale",
      "values": {
        "salvage_recovery_value": 33000,
        "storage_cost": 6600,
        "title_complexity_score": 37,
        "disposal_speed_score": 75,
        "environmental_compliance_score": 75
      }
    },
    {
      "optionId": "option-3",
      "name": "Retain for Parts Recovery",
      "values": {
        "salvage_recovery_value": 48000,
        "storage_cost": 9600,
        "title_complexity_score": 49,
        "disposal_speed_score": 68,
        "environmental_compliance_score": 68
      }
    }
  ]
}

Execute

cURL
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-ins-036-demo-001" \
  --data @auto-ins-036-execute.json

DDE retrieves authoritative criteria, validation metadata, and constraints from DKS, excludes candidates that fail mandatory hard constraints, executes the deterministic ranking, 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.

Successful Response Shape
{
  "service": "decisioq",
  "version": "7.6.3",
  "requestId": "0HNE...",
  "operation": "Decide",
  "success": true,
  "decisionType": "AUTO-INS-036",
  "decisionVersion": "13.9.3",
  "timestampUtc": "2026-07-19T00:00:00Z",
  "decisionResult": {
    "winner": "option-1",
    "confidence": 91,
    "ranking": [
      {
        "optionId": "option-1",
        "score": 0.91,
        "breakdown": {
          "salvage_recovery_value": 0.30,
          "storage_cost": 0.15,
          "title_complexity_score": 0.20,
          "disposal_speed_score": 0.20,
          "environmental_compliance_score": 0.15
        },
        "normalizationBreakdown": {}
      },
      {
        "optionId": "option-2",
        "score": 0.84,
        "breakdown": {},
        "normalizationBreakdown": {}
      }
    ],
    "excludedOptions": [
      {
        "optionId": "option-3",
        "reasons": [
          "Environmental compliance score is below the minimum threshold of 70."
        ]
      }
    ],
    "explanation": {
      "summary": "Auction Salvage Sale ranked highest among eligible salvage options.",
      "strengths": [],
      "weaknesses": [],
      "exclusions": [
        "option-3: Environmental compliance score is below the minimum threshold of 70."
      ]
    }
  },
  "constraintSummary": {
    "definedConstraintCount": 1,
    "activeConstraintCount": 1,
    "eligibleOptionCount": 2,
    "excludedOptionCount": 1,
    "eligibleOptions": [
      "option-1",
      "option-2"
    ],
    "excludedOptions": [
      {
        "optionId": "option-3",
        "reasons": [
          "Environmental compliance score is below the minimum threshold of 70."
        ]
      }
    ]
  },
  "warnings": [],
  "requestContext": {
    "correlationId": "auto-ins-036-demo-001"
  }
}
WinnerThe selected option ID in decisionResult.winner.
RankingOnly eligible options ordered by deterministic score.
ExclusionsHard-constraint failures listed under constraintSummary and decisionResult.excludedOptions.

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.

Sensitivity Result Shape
{
  "sensitivityResult": {
    "stableWinner": true,
    "winner": "option-1",
    "mostSensitiveCriterion": "storage_cost",
    "confidence": 95,
    "criterionImpacts": {
      "storage_cost": 0.1842
    },
    "winnerChangeCounts": {
      "storage_cost": 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 by the service, the response may also include an ai block with structured business-language explanation fields.

AI Explanation Shape
{
  "ai": {
    "enabled": true,
    "generated": true,
    "schemaValidated": true,
    "explanation": {
      "summary": "The selected salvage option provided the strongest overall balance of recovery value, storage cost, title complexity, disposal speed, and environmental compliance.",
      "whyRecommended": "It met the hard environmental compliance threshold and ranked highest among eligible salvage options.",
      "keyDrivers": [],
      "tradeoffs": [],
      "competitors": [],
      "sensitivitySummary": "Sensitivity analysis was not included in this response.",
      "scenarioSummary": "The standard scenario was selected.",
      "risks": [],
      "nextSteps": [],
      "assumptions": []
    }
  }
}
Explanation output is supporting context. Business-facing pages should render the explanation, warnings, assumptions, and limitations without provider branding.

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-INS-036 metadata from https://dks.vinquery.com/decisioncatalog/decisions/AUTO-INS-036.
  3. Execute a Prepared Decision Input at https://dde.vinquery.com/api/v1/decide.

Set these environment variables before running any companion example:

Environment variables
DECISIOQ_CLIENT_ID
DECISIOQ_CLIENT_SECRET

Optional:
DECISIOQ_AUDIENCE=vinquery:api:decisioq
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

SymptomLikely CauseWhat to Check
401 UnauthorizedMissing, expired, or invalid bearer token.Request a fresh jwtToken from Identity and send it as Authorization: Bearer ....
Decision not foundThe decision ID is not in the active catalog.Load /decisioncatalog/decisions/AUTO-INS-036 and confirm the ID is published.
Validation failedA required criterion value is missing or outside its rule.Use canonical criterion IDs and keep score values in the expected range.
Candidate excludedA mandatory hard constraint failed.Review constraintSummary.excludedOptions for the exact candidate and reason.
HTML error responseAn upstream hosted service failed before returning JSON.Check service health and server logs for Identity, DKS, or DDE.

Production Checklist

Security

Keep API Consumer credentials and jwtTokens on the server side. Use HTTPS, short-lived bearer tokens, and an API Consumer linked to a DecisioQ account for usage accounting.

Catalog

Load decision metadata from DKS and cache cautiously. Refresh when catalog versions change.

Request Quality

Use canonical criterion IDs, validate value ranges, and send at least two candidate options.

Constraints

Show excluded candidates separately. Do not include them in user-facing ranking tables.

Explanation

Display explanation text as supporting context only. Never let AI text override deterministic results.

User Experience

Show business labels to users and keep raw execution trace collapsed for advanced diagnostics.