AuditResult v1.0-alpha3

Overview

AuditResult represents the output of evaluating a customer-interaction against an audit-criteria policy.

Alpha3 preserves, per indicator:

• the indicator definition snapshot (type/description/polarity/weight)
• the observed value
• the computed score
• optional evidence snippets

Important note (known issue in alpha3)

In v1.0-alpha3.json, the root required includes audit_result_id, but the schema properties defines id instead. This makes payloads inconsistent to validate strictly.

• For a fixed version, use audit-result/v1.0-beta1.json (recommended).

Schema structure

Root fields

References

customer_interaction and audit_criteria objects:

• s3_uri: string
• <schema>_id: string

CriterionResult

Required fields:

• id, name, score, indicator_results[]

Optional:

• description, weight, enabled

IndicatorResult

Required fields:

• id (pattern ^[A-Z0-9]+-I[0-9]+$)
• type (boolean | metric | enum)
• description
• polarity (-5..5)
• value (boolean | number | string)
• score (number)

Optional:

• weight (0..1 or null), enabled (boolean or null), evidence[]

Example (from schema)

{
  "schema_type": "audit-result",
  "schema_version": "v1.0-alpha3",
  "audit_result_id": "ar-20240101-001",
  "timestamp": "2024-01-01T10:30:00Z",
  "customer_interaction": {
    "s3_uri": "s3://ontopix-interactions/customer-001/interaction-20240101-001.json",
    "customer_interaction_id": "ci-20240101-001"
  },
  "audit_criteria": {
    "s3_uri": "s3://ontopix-schemas/audit-criteria/policy-customer-service-v2.json",
    "audit_criteria_id": "policy-customer-service-v2"
  },
  "criteria_results": [
    {
      "id": "C1",
      "name": "Professional Introduction",
      "score": 80.0,
      "indicator_results": [
        {
          "id": "C1-I1",
          "type": "boolean",
          "description": "Agent stated their name",
          "polarity": 3,
          "value": true,
          "score": 2.4,
          "evidence": [
            "Agent: 'Hi, my name is Sarah and I'll be helping you today.'"
          ]
        }
      ]
    }
  ]
}

Migration notes

alpha2 → alpha3

Alpha3 introduces a different (simpler) representation focused on:

• customer_interaction + audit_criteria references
• per-criterion results with indicator_results[]
• polarity-based scoring alignment with audit-criteria v1.0-alpha3

alpha3 → beta1 (recommended)

• Root id is normalized to id
• S3 URIs are validated more strictly (format: uri + ^s3://...)