The Vehicle Inspection & Testing sector in the DecisioQ Decision Catalog is identified by AUTO-INSP. It currently covers 100 decision types across safety inspection, emissions testing, diagnostic testing, roadworthiness assessment, compliance, certificate issuance, inspection operations, quality assurance, fraud detection, equipment analytics, data reporting, fleet programs, and strategic inspection network planning.

DecisioQ integrations should load sector, category, decision, Decision Preparation Model, scenario, criterion, and decision overview metadata from the Decision Catalog. Do not hard-code old static decision lists or legacy request models.

DecisioQ should not replace certified measurement equipment or statutory pass/fail rules. It should support explainable business decisions around routing, prioritization, review, certification workflow, exception handling, and audit-ready recommendations.

Vehicle inspection client applications should use the same discovery flow as the Business Decision Studio:

1. Load GET /decisioncatalog through the approved server-side Decision Catalog gateway.
2. Populate Sector from catalog.sectors[] and select AUTO-INSP for Vehicle Inspection & Testing.
3. Populate Category from selectedSector.categories[]. Example categories include Safety Inspection, Emissions Testing, Diagnostic Testing, Roadworthiness Assessment, Compliance & Certification, Inspection Operations, Inspection Quality Assurance, Fraud & Anomaly Detection, Calibration & Equipment Analytics, and Strategic & Enterprise Operations.
4. Populate Decision from selectedCategory.decisions[] when available, or call /decisioncatalog/sectors/{sectorCode}/categories/{categoryCode}/decisions.
5. Display Decision Name only in the dropdown while keeping decisionId as the option value.
6. Load full decision detail from /decisioncatalog/decisions/{decisionId} before rendering Guided Data Collection.

For regional deployments, keep DecisioQ technical identifiers stable and localize only user-facing labels and guidance. Unless the selected endpoint and decision schema explicitly support unit-qualified input, convert mileage, distance, pressure, temperature, mass, volume, speed, fuel consumption, and other measurements to the required canonical units before submission. Do not infer units or currency from locale.

Vehicle inspection integrations should map operational inspection data into decision-specific Business Data. The selected decision detail defines which criteria are required, how values are measured, and which direction, scale, and unit each criterion expects.

Do not invent criterion IDs. Use the canonical criteria returned by /decisioncatalog/decisions/{decisionId}, including criterion overview metadata, unit, direction, scale, and data guidance.

1. Authenticate through the approved server-side identity flow. Browser pages should not directly handle credentials.
2. Load the Decision Catalog and let the user choose Sector, Category, Decision, Decision Preparation Model, and Scenario.
3. Load decision detail and render Guided Data Collection from returned criteria.
4. User or system prepares Business Data for candidate vehicles, inspection outcomes, inspectors, bays, equipment, retest actions, certificates, or review cases.
5. Call POST /api/v1/validate to validate and prepare the decision input before execution.
6. Call POST /api/v1/decide to return the authoritative Decision Result.
7. Display recommendation, ranked alternatives, warnings, assumptions, and Explanation of Decision Result.
8. Keep execution trace and diagnostics collapsed by default for developer and integrator review.

The exact fields depend on the selected Vehicle Inspection & Testing decision. The example below shows the integration style rather than a guaranteed schema for every decision.

{
  "decisionId": "AUTO-INSP-008",
  "decisionPreparationModelId": "AUTO-INSP-PROFILE-STANDARD",
  "scenarioId": "AUTO-INSP-SCENARIO-SAFETY-REVIEW",
  "businessData": {
    "correlationId": "inspection-20260717-1042",
    "inspectionType": "SafetyInspection",
    "jurisdiction": "ON",
    "stationId": "STATION-102",
    "vehicleClass": "Passenger",
    "options": [
      {
        "optionId": "INSPECTION-ACTION-PASS-WITH-ADVISORY",
        "label": "Pass With Advisory",
        "values": {
          "safetySeverityScore": 28,
          "evidenceCompletenessScore": 96,
          "regulatoryRiskScore": 12,
          "customerImpactScore": 35,
          "retestLikelihoodScore": 22
        }
      },
      {
        "optionId": "INSPECTION-ACTION-REQUIRE-REPAIR",
        "label": "Require Repair Before Certificate",
        "values": {
          "safetySeverityScore": 78,
          "evidenceCompletenessScore": 92,
          "regulatoryRiskScore": 84,
          "customerImpactScore": 64,
          "retestLikelihoodScore": 70
        }
      }
    ]
  }
}

Call DecisioQ from a trusted backend service. Keep identity credentials, account verification, and service configuration outside public browser code.

async function executeVehicleInspectionDecision(jwtToken, preparedDecisionInput) {
  const response = await fetch(`${process.env.DECISIOQ_BASE_URL}/api/v1/decide`, {
    method: "POST",
    headers: {
      "Authorization": `Bearer ${jwtToken}`,
      "Content-Type": "application/json"
    },
    body: JSON.stringify(preparedDecisionInput)
  });

  const payload = await response.json();

  if (!response.ok) {
    throw new Error(payload.message || "Decision execution failed.");
  }

  return payload;
}

• Use a guided decision selector: Sector, Category, Decision, Decision Preparation Model, and Scenario.
• Show Selection Overview for sector, category, and decision metadata so business users understand the decision before entering data.
• Render Guided Data Collection from criterion definitions and show criterion overview summaries where available.
• Display Decision Name in selectors and show the selected decisionId separately for developers and integrators.
• For inspection stations, keep operational screens simple: recommendation, reason, required action, warnings, and next step.
• Keep execution trace and diagnostics available to integrators but collapsed by default.
• Never expose internal proxy URLs, service credentials, signing keys, or account verification details in browser code.

• Confirm inspection decisions support the right jurisdiction, inspection type, vehicle class, and effective policy date.
• Validate Business Data before execution and show user-friendly validation messages.
• Persist correlation ID, VIN, plate, inspection ID, station ID, inspector ID, device ID, certificate ID, decision ID, profile ID, scenario ID, selected option, score, and explanation for audit.
• Retain the successful decision response requestId with the host business transaction, then call POST /api/v1/decision-outcomes when the action and realized result are known.
• Require an overrideReason for overridden recommendations; never infer acceptance merely because a result was displayed.
• Monitor GET /api/v1/decision-outcomes/summary for acceptance rate, override rate, and realized-value aggregates. Treat outcome feedback as reporting evidence, not automatic model training.
• Keep statutory pass/fail rule evaluation separate and deterministic; use DecisioQ for multi-factor routing, prioritization, review, and recommendation decisions.
• Monitor preview failures, execution failures, account verification errors, timeout rates, and unexpected warning counts.
• Review Decision Preparation Models and scenario assumptions with inspection, compliance, operations, and quality owners when rules, equipment, or market conditions change.