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

AUTO-AUCT-006 End-to-End Example

Select Auction House using Identity, the secured Decision Catalog, Decision Catalog token propagation, and Prepared Criteria Mode execution.

Automotive Auto Auctions Vehicle Acquisition TOPSIS
IdentityIssue bearer token
CatalogDiscover decision metadata
ProfileSelect weights and scenario
ExecuteRun deterministic ranking
ExplainReview result context

Overview

AUTO-AUCT-006, Select Auction House, ranks candidate auction houses by acquisition fit, cost control, vehicle quality, logistics, reputation, and title handling.

Decision ID
AUTO-AUCT-006
Decision Name
Select Auction House
Decision Preparation Model
auto-auctions-select-auction-house-auto-auct-006 version 1.0.0
Default Profile
balanced
Default Scenario
standard
Catalog
DKR-AUTO-RUNTIME-001, version 13.9.3
The deterministic Decision Service ranks the options. The explanation object is explanatory only and must not choose, rerank, or override the deterministic result.

Understanding This Decision

Select Auction House helps a buyer choose the auction source that best balances inventory access, fee discipline, expected vehicle quality, logistics, auction reputation, and title-processing reliability.

Business question

Which auction house should be used for the current acquisition need?

Expected outcome

A ranked list of candidate auction houses with a recommended winner and criterion-level score evidence.

Typical users

Vehicle acquisition managers, dealership buyers, inventory planners, and integration teams building acquisition workflows.

Decision boundary

Use this decision to compare auction sources. It does not replace legal, compliance, title, or vendor-contract review.

Criteria

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

Criterion IDNameDirectionWeightValidation
vehicle_availability_scoreVehicle Availability Scoremaximize25score_0_to_100
buyer_fee_levelBuyer Fee Levelminimize20non_negative_currency
average_vehicle_qualityAverage Vehicle Qualitymaximize20score_0_to_100
distance_to_facilityDistance to Facilityminimize15non_negative_integer
auction_reputation_scoreAuction Reputation Scoremaximize15score_0_to_100
title_processing_speedTitle Processing Speedmaximize5score_0_to_100

Data Preparation Guide

Loading criterion-specific integration guidance...

Constraint Processing

This decision includes a catalog-defined hard constraint. Decision Catalog returns the constraint with the decision detail, and Decision Service evaluates it before criteria-based ranking.

Verified Catalog ConstraintStatusEffect
AUTO-AUCT-006-REPUTATION-MIN-80Hard, enabled, mandatoryRequires auction_reputation_score >= 80 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": [
          "Auction reputation score is below the minimum threshold of 80."
        ]
      }
    ]
  }
}
Constraint Handling Pattern
const constraints = decisionDetail.constraints || [];
if (constraints.length > 0) {
  // Decision Service 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-AUCT-006, option-3 is excluded from the showcase sample because its auction reputation score is below the catalog threshold.

Decision Preparation Model

The published Decision Preparation Model validates and transforms illustrative Business Data into the canonical criteria required by AUTO-AUCT-006 before Decision Service applies ranking.

Profile ID
auto-auctions-select-auction-house-auto-auct-006
Version
1.0.0
Options Path
$.auctionLots
Option ID Path
$.optionId
Display Name Path
$.name
Client Business Data PathTransformationCanonical Criterion IDUnitValidation
option.assessment.vehicleAvailabilityScoredirect valuevehicle_availability_scoreScoreInput Contract
option.financial.buyerFeeLeveldirect valuebuyer_fee_levelCurrencyInput Contract
option.assessment.averageVehicleQualitydirect valueaverage_vehicle_qualityScoreInput Contract
option.vehicle.acquisition.distanceToFacilitydirect valuedistance_to_facilityKilometresInput Contract
option.assessment.auctionReputationScoredirect valueauction_reputation_scoreScoreInput Contract
option.vehicle.acquisition.titleProcessingSpeeddirect valuetitle_processing_speedScoreInput Contract
Illustrative Business Data
{
  "requestContext": {
    "sourceSystem": "automotive-profile-factory",
    "correlationId": "factory-auto-auct-006"
  },
  "auctionLots": [
    {
      "optionId": "LOT-006-01",
      "name": "Select Auction House Option 1",
      "assessment": {
        "vehicleAvailabilityScore": 43.0,
        "averageVehicleQuality": 65.0,
        "auctionReputationScore": 88.0
      },
      "financial": {
        "buyerFeeLevel": 137500.0
      },
      "vehicle": {
        "acquisition": {
          "distanceToFacility": 204000.0,
          "titleProcessingSpeed": 43.0
        }
      }
    },
    {
      "optionId": "LOT-006-02",
      "name": "Select Auction House Option 2",
      "assessment": {
        "vehicleAvailabilityScore": 25.0,
        "averageVehicleQuality": 61.0,
        "auctionReputationScore": 92.0
      },
      "financial": {
        "buyerFeeLevel": 102500.0
      },
      "vehicle": {
        "acquisition": {
          "distanceToFacility": 219000.0,
          "titleProcessingSpeed": 76.0
        }
      }
    }
  ]
}
Prepared Option Values
{
  "optionId": "LOT-006-01",
  "name": "Select Auction House Option 1",
  "values": {
    "vehicle_availability_score": 43.0,
    "buyer_fee_level": 137500.0,
    "average_vehicle_quality": 65.0,
    "distance_to_facility": 204000.0,
    "auction_reputation_score": 88.0,
    "title_processing_speed": 43.0
  }
}
This example illustrates the published request structure. Adapt it to your organization and validate it against the Input Contract.

Profiles and Scenarios

This example selects a Profile for evaluation emphasis and a Scenario for operating context. Discover both from the selected Decision Catalog definition.

Profile IDNamePurpose
balancedBalancedPreserves the default Decision Catalog criterion weights.
cost_focusedCost FocusedPlaces stronger emphasis on minimized financial and operating cost criteria.
quality_focusedQuality FocusedPlaces stronger emphasis on quality, value, condition, inventory fit, and performance criteria.
risk_averseRisk AversePlaces stronger emphasis on risk reduction, certainty, condition, title, and operational exposure.
Scenario IDNameUse When
standardStandard Operating ScenarioRoutine auction decision execution.
limited_budgetLimited Budget ScenarioPurchasing capital is constrained and financial discipline is emphasized.
high_demandHigh Demand ScenarioInventory demand is high and speed or availability matters more than normal.
risk_controlRisk Control ScenarioTitle, condition, market, or operational uncertainty must be controlled more aggressively.

Prepared Input

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

Prepared Criteria Mode JSON
{
  "decisionId": "AUTO-AUCT-006",
  "profileId": "balanced",
  "scenarioId": "standard",
  "algorithm": "TOPSIS",
  "weightStrategy": "Expert",
  "runSensitivity": false,
  "requestContext": {
    "correlationId": "auto-auct-006-demo-001"
  },
  "options": [
    {
      "optionId": "MANHEIM-TORONTO",
      "name": "Manheim Toronto",
      "values": {
        "vehicle_availability_score": 88,
        "buyer_fee_level": 1250,
        "average_vehicle_quality": 88,
        "distance_to_facility": 54,
        "auction_reputation_score": 88,
        "title_processing_speed": 88
      }
    },
    {
      "optionId": "ADESA-TORONTO",
      "name": "ADESA Toronto",
      "values": {
        "vehicle_availability_score": 81,
        "buyer_fee_level": 1750,
        "average_vehicle_quality": 81,
        "distance_to_facility": 71,
        "auction_reputation_score": 81,
        "title_processing_speed": 81
      }
    }
  ]
}

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-auct-006-demo-001" \
  --data @auto-auct-006-execute.json

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

Interpret the Result

The successful response includes both the deterministic decisionResult and a top-level explanation object. The explanation adds context but does not select, rerank, recalculate, or override the ranking.

Successful Response Shape
{
  "service": "decisioq",
  "version": "7.6.3",
  "requestId": "0HNE...",
  "operation": "Decide",
  "success": true,
  "decisionType": "AUTO-AUCT-006",
  "decisionVersion": "13.9.3",
  "timestampUtc": "2026-07-18T00:00:00Z",
  "decisionResult": {
    "winner": "MANHEIM-TORONTO",
    "confidence": 72.4,
    "ranking": [
      {
        "optionId": "MANHEIM-TORONTO",
        "score": 0.8421,
        "breakdown": {
          "vehicle_availability_score": 0.25
        },
        "normalizationBreakdown": {}
      }
    ],
    "excludedOptions": [
      {
        "optionId": "IMPACT-AUTO-AUCTIONS",
        "reasons": [
          "Auction reputation score is below the minimum threshold of 80."
        ]
      }
    ]
  },
  "explanation": {
      "summary": "The selected auction house provided the strongest overall fit.",
      "whyRecommended": "It combined strong availability and quality with acceptable cost.",
      "keyDrivers": [],
      "tradeoffs": [],
      "competitors": [],
      "sensitivitySummary": "Sensitivity analysis was not included in this response.",
      "scenarioSummary": "The standard scenario was selected.",
      "risks": [],
      "nextSteps": [],
      "assumptions": []
  },
  "constraintSummary": {
    "definedConstraintCount": 1,
    "activeConstraintCount": 1,
    "eligibleOptionCount": 2,
    "excludedOptionCount": 1,
    "eligibleOptions": [
    "MANHEIM-TORONTO",
    "ADESA-TORONTO"
    ],
    "excludedOptions": [
      {
        "optionId": "IMPACT-AUTO-AUCTIONS",
        "reasons": [
          "Auction reputation score is below the minimum threshold of 80."
        ]
      }
    ]
  },
  "warnings": [],
  "requestContext": {
    "correlationId": "auto-auct-006-demo-001"
  }
}
WinnerThe selected option ID in decisionResult.winner.
RankingAll eligible options ordered by score.
BreakdownCriterion-level evidence for the ranking.

Sensitivity Analysis

runSensitivity is an optional execution flag supported by both Business Data Mode and Prepared Criteria Mode. Set it to true when the client wants recommendation-stability information in the same response. The sensitivity engine analyzes the prepared criteria produced by either input path, perturbs criterion weights by controlled factors, and reports whether the winner remains stable.

Sensitivity Result Shape
{
  "sensitivityResult": {
    "stableWinner": true,
    "winner": "MANHEIM-TORONTO",
    "mostSensitiveCriterion": "buyer_fee_level",
    "confidence": 95,
    "criterionImpacts": {
      "buyer_fee_level": 0.1842
    },
    "winnerChangeCounts": {
      "buyer_fee_level": 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 includes a provider-neutral top-level explanation object. It explains the already-finalized deterministic result and does not change the ranking.

Explanation Shape
{
  "explanation": {
      "summary": "The selected auction house provided the strongest overall fit.",
      "whyRecommended": "It combined strong availability and quality with acceptable cost.",
      "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 Decision Service to Decision Catalog.
requestContext.correlationId
Optional payload value echoed in the response and used for tracing.
configurationUsed
The authoritative effective weight strategy, ranking algorithm, profile, scenario, sensitivity setting, and source for each value.
diagnostics
Safe execution counts returned only when responseOptions.includeDiagnostics is true.

Code Examples

These examples demonstrate the current DecisioQ flow:

  1. Request jwtToken from https://identity.vinquery.com/connect/token.
  2. Load AUTO-AUCT-006 metadata from https://dks.vinquery.com/decisioncatalog/decisions/AUTO-AUCT-006.
  3. Execute a Prepared Criteria Mode 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_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-AUCT-006 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.
HTML error responseAn upstream hosted service failed before returning JSON.Check service health and server logs for Identity, Decision Catalog, or Decision Service.

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 Decision Catalog and cache cautiously. Refresh when catalog versions change.

Request Quality

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

Operations

Send correlation IDs, record request IDs, and monitor non-JSON upstream failures.

Explanation

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

User Experience

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