Branch main Contract DiagnosticReference

Contract: Diagnosticreference

Back to Branch Overview

Field	Value
Branch	main
Source	specs/contracts/DiagnosticReference.schema.json
Commit	774b981ef226
Synced (UTC)	2026-06-29T06:00:16Z

Visual Context

Contract pages define the machine-checkable object shape that crosses a lifecycle boundary.

flowchart LR
  Producer["Lifecycle producer"] --> Contract["Contract schema"]
  Contract --> Example["Schema example"]
  Example --> Validator["Schema validator"]
  Contract --> Fixture["Conformance fixture output"]
  Fixture --> Gate["Base-design gate"]

Loading

Reading Checklist

Question	Where to look
Which lifecycle boundary uses it?	Read description, required fields, and linked references.
What diagnostics are mandatory?	Inspect diagnostic reference fields and rule-reference links.
How is it validated?	Compare this schema with fixtures/schema_examples/ and conformance vectors.

---

JSON Payload

{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "title": "DiagnosticReference",
  "description": "Reference from decisions and audit events to a diagnostic chain.",
  "type": "object",
  "properties": {
    "diagnosticID": {
      "type": "string"
    },
    "chainRootReference": {
      "type": "string"
    },
    "diagnosticKind": {
      "type": "string",
      "enum": [
        "STATE_VALIDITY",
        "RECOVERY",
        "POLICY",
        "BACKUP",
        "EXECUTION",
        "VERIFICATION",
        "ROLLBACK",
        "FALLBACK",
        "CONTAINMENT",
        "SAFE_HALT",
        "AUDIT",
        "MAPPING",
        "JSON_SEMANTICS"
      ]
    },
    "ruleReferences": {
      "type": "array",
      "items": {
        "$ref": "RuleReference.schema.json"
      },
      "minItems": 1
    }
  },
  "required": [
    "diagnosticID",
    "chainRootReference",
    "diagnosticKind",
    "ruleReferences"
  ],
  "additionalProperties": false
}