ExecutionSlice
Minimal Execution Slice
Schema-valid JSON for the Execution Slice resource.
ExecutionSlice · ORBIT v0.1
ExecutionSlice
The next bounded change justified by current evidence.
A bounded, execution-ready change derived from a Reconciliation and tied to the Plan revision and repository state that justified it.
The raw JSON Schema is the machine contract for this resource. The field reference below is derived from that schema.
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://orbitspec.dev/schema/execution-slice/v0.1.json",
"title": "ORBIT Execution Slice",
"type": "object",
"required": [
"specVersion",
"id",
"planId",
"outcomeId",
"basedOn",
"objective",
"why",
"contributesTo",
"scope"
],
"properties": {
"specVersion": {
"const": "0.1",
"description": "ORBIT specification version."
},
"id": {
"type": "string",
"description": "Stable ExecutionSlice identifier."
},
"planId": {
"type": "string",
"description": "Referenced Plan identifier."
},
"outcomeId": {
"type": "string",
"description": "Referenced Outcome identifier."
},
"basedOn": {
"type": "object",
"required": [
"planRevision",
"reconciliationId",
"repositories"
],
"properties": {
"planRevision": {
"type": "integer",
"minimum": 1,
"description": "Plan revision used for reconciliation."
},
"reconciliationId": {
"type": "string",
"description": "Reconciliation that justified the slice."
},
"repositories": {
"type": "object",
"description": "Repository revisions used as evidence."
}
},
"additionalProperties": false,
"description": "Provenance for the slice."
},
"objective": {
"type": "string",
"description": "Bounded change objective."
},
"why": {
"type": "string",
"description": "Reason the change is justified."
},
"contributesTo": {
"type": "array",
"items": {
"type": "string"
},
"description": "Acceptance Criteria advanced by the slice."
},
"scope": {
"type": "object",
"required": [
"include",
"exclude"
],
"properties": {
"include": {
"type": "array",
"items": {
"type": "string"
},
"description": "Included work."
},
"exclude": {
"type": "array",
"items": {
"type": "string"
},
"description": "Excluded work."
}
},
"additionalProperties": false,
"description": "Explicit change boundary."
}
},
"additionalProperties": false
}| Field | Type | Required | Meaning | Constraints |
|---|---|---|---|---|
specVersion | const "0.1" | yes | ORBIT specification version. | must equal "0.1" |
id | string | yes | Stable ExecutionSlice identifier. | — |
planId | string | yes | Referenced Plan identifier. | — |
outcomeId | string | yes | Referenced Outcome identifier. | — |
basedOn | object | yes | Provenance for the slice. | — |
basedOn.planRevision | integer | yes | Plan revision used for reconciliation. | minimum 1 |
basedOn.reconciliationId | string | yes | Reconciliation that justified the slice. | — |
basedOn.repositories | object | yes | Repository revisions used as evidence. | — |
objective | string | yes | Bounded change objective. | — |
why | string | yes | Reason the change is justified. | — |
contributesTo | array<string> | yes | Acceptance Criteria advanced by the slice. | — |
scope | object | yes | Explicit change boundary. | — |
scope.include | array<string> | yes | Included work. | — |
scope.exclude | array<string> | yes | Excluded work. | — |
| Resource | Reference | Meaning |
|---|---|---|
| Based on | basedOn.planRevision + basedOn.reconciliationId | Identifies the Plan revision and Reconciliation that justified this slice. |
| Advances | outcomeId | Links the bounded change to an Outcome in the Plan. |
| Contributes to | contributesTo[] | Links the change to Acceptance Criteria it advances. |
| Bound to | basedOn.repositories | Preserves relevant repository revisions used to justify the slice. |
JSON Schema validates structure. These semantic rules explain what a structurally valid ExecutionSlice must mean in the ORBIT model.
ExecutionSlice
Schema-valid JSON for the Execution Slice resource.
ExecutionSlice
Schema-valid JSON for the Execution Slice resource.
The canonical machine-readable contract is available at /schema/execution-slice.schema.json.
Use it for tooling, CI validation, and agent integrations. The human guide explains semantics; the schema defines structural conformance.