-
Notifications
You must be signed in to change notification settings - Fork 0
Branch main Contract ExecutionStepResult
github-actions[bot] edited this page Jul 1, 2026
·
75 revisions
| Field | Value |
|---|---|
| Branch | main |
| Source | specs/contracts/ExecutionStepResult.schema.json |
| Commit | 774b981ef226 |
| Synced (UTC) | 2026-07-01T05:54:14Z |
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"]
| 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. |
{
"$schema": "http://json-schema.org/draft-07/schema#",
"title": "ExecutionStepResult",
"description": "Result for each recovery or execution step.",
"type": "object",
"properties": {
"executionStepResultID": {
"type": "string"
},
"stepID": {
"type": "string"
},
"status": {
"type": "string",
"enum": [
"SUCCEEDED",
"FAILED",
"SKIPPED",
"BLOCKED"
]
},
"observedHashAfterStep": {
"type": "string"
},
"diagnosticReference": {
"$ref": "DiagnosticReference.schema.json"
}
},
"required": [
"executionStepResultID",
"stepID",
"status",
"observedHashAfterStep",
"diagnosticReference"
],
"additionalProperties": false
}