Branch main Contract VerificationResult

Contract: Verificationresult

Back to Branch Overview

Field	Value
Branch	main
Source	specs/contracts/VerificationResult.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": "VerificationResult",
  "description": "Verification result paired with a verification plan.",
  "type": "object",
  "properties": {
    "verificationResultID": {
      "type": "string"
    },
    "verificationPlanID": {
      "type": "string"
    },
    "status": {
      "type": "string",
      "enum": [
        "PASSED",
        "FAILED",
        "BLOCKED"
      ]
    },
    "expectedSemanticState": {
      "$ref": "AshState.schema.json"
    },
    "actualSemanticState": {
      "$ref": "AshState.schema.json"
    },
    "diagnosticReference": {
      "$ref": "DiagnosticReference.schema.json"
    }
  },
  "required": [
    "verificationResultID",
    "verificationPlanID",
    "status",
    "expectedSemanticState",
    "actualSemanticState",
    "diagnosticReference"
  ],
  "additionalProperties": false
}