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-006version1.0.0- Default Profile
balanced- Default Scenario
standard- Catalog
DKR-AUTO-RUNTIME-001, version13.9.3
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 ID | Name | Direction | Weight | Validation |
|---|---|---|---|---|
vehicle_availability_score | Vehicle Availability Score | maximize | 25 | score_0_to_100 |
buyer_fee_level | Buyer Fee Level | minimize | 20 | non_negative_currency |
average_vehicle_quality | Average Vehicle Quality | maximize | 20 | score_0_to_100 |
distance_to_facility | Distance to Facility | minimize | 15 | non_negative_integer |
auction_reputation_score | Auction Reputation Score | maximize | 15 | score_0_to_100 |
title_processing_speed | Title Processing Speed | maximize | 5 | score_0_to_100 |
Data Preparation Guide
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 Constraint | Status | Effect |
|---|---|---|
AUTO-AUCT-006-REPUTATION-MIN-80 | Hard, enabled, mandatory | Requires auction_reputation_score >= 80 before a candidate can participate in ranking. |
{
"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."
]
}
]
}
}
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 Path | Transformation | Canonical Criterion ID | Unit | Validation |
|---|---|---|---|---|
option.assessment.vehicleAvailabilityScore | direct value | vehicle_availability_score | Score | Input Contract |
option.financial.buyerFeeLevel | direct value | buyer_fee_level | Currency | Input Contract |
option.assessment.averageVehicleQuality | direct value | average_vehicle_quality | Score | Input Contract |
option.vehicle.acquisition.distanceToFacility | direct value | distance_to_facility | Kilometres | Input Contract |
option.assessment.auctionReputationScore | direct value | auction_reputation_score | Score | Input Contract |
option.vehicle.acquisition.titleProcessingSpeed | direct value | title_processing_speed | Score | Input Contract |
{
"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
}
}
}
]
}
{
"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
}
}
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 ID | Name | Purpose |
|---|---|---|
balanced | Balanced | Preserves the default Decision Catalog criterion weights. |
cost_focused | Cost Focused | Places stronger emphasis on minimized financial and operating cost criteria. |
quality_focused | Quality Focused | Places stronger emphasis on quality, value, condition, inventory fit, and performance criteria. |
risk_averse | Risk Averse | Places stronger emphasis on risk reduction, certainty, condition, title, and operational exposure. |
| Scenario ID | Name | Use When |
|---|---|---|
standard | Standard Operating Scenario | Routine auction decision execution. |
limited_budget | Limited Budget Scenario | Purchasing capital is constrained and financial discipline is emphasized. |
high_demand | High Demand Scenario | Inventory demand is high and speed or availability matters more than normal. |
risk_control | Risk Control Scenario | Title, 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.
{
"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 -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.
{
"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"
}
}
decisionResult.winner.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.
{
"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": {
"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": []
}
}
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.includeDiagnosticsis true.
Code Examples
These examples demonstrate the current DecisioQ flow:
- Request
jwtTokenfromhttps://identity.vinquery.com/connect/token. - Load
AUTO-AUCT-006metadata fromhttps://dks.vinquery.com/decisioncatalog/decisions/AUTO-AUCT-006. - Execute a Prepared Criteria Mode 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
| Symptom | Likely Cause | What to Check |
|---|---|---|
| 401 Unauthorized | Missing, expired, or invalid bearer token. | Request a fresh jwtToken from Identity and send it as Authorization: Bearer .... |
| Decision not found | The decision ID is not in the active catalog. | Load /decisioncatalog/decisions/AUTO-AUCT-006 and confirm the ID is published. |
| Validation failed | A required criterion value is missing or outside its rule. | Use canonical criterion IDs and keep score values in the expected range. |
| HTML error response | An 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.
