Orchestrator API Reference
Schema definitions for orchestrator endpoints covering task creation, approvals, budgets, and audit exports.
Task lifecycle
`TaskCreateRequest` accepts goal text, context attachments, policy mode, and budget configuration. Responses stream `TaskEvent` entries describing plan creation, step transitions, approvals, and completion.
- Budgets enforce limits on duration, tool invocations, and outbound classifications.
- `TaskArtifact` schema references stored files with SHA-256 hashes for integrity checks.
- `TaskError` surfaces retriable vs. fatal categories for automated remediation.
Approval workflow
`ApprovalRequest` objects contain step metadata, risk class, and recommended next action. Approvers respond with `ApprovalDecision` including justification notes.
- All approvals are logged with actor ID, signature (planned), and timestamp.
- `approval_webhook` configuration notifies external systems like Slack or PagerDuty.
- `ApprovalEscalation` events fire when requests exceed SLA thresholds.
Audit exports
Use the `/tasks/{id}/export` endpoint to bundle plan graphs, artifacts, and logs into a portable package for review.
- Evidence bundles include the model hash that executed the run.
- Large artifacts stream in chunks with optional compression.
- Roadmap includes signed manifests for third-party verification.