---
title: "actor.task-event@1 · OpenVibe.Services"
canonical: "https://openvibe.services/docs/contracts/actor.task-event@1"
updated: null
---

# actor.task-event@1 · OpenVibe.Services

HTML: [actor.task-event@1 · OpenVibe.Services](https://openvibe.services/docs/contracts/actor.task-event@1)

# ActorTaskEvent `actor.task-event@1`

Generated at 2026-11-13 06:25:48 UTC from [`openvibe-contracts v0.419.0`](https://github.com/OpenVibers/OpenVibe.Contracts/tree/v0.419.0) and [`openvibe-sdk v0.161.0`](https://github.com/OpenVibers/OpenVibe.SDK/tree/v0.161.0).

An older major, still in the catalog. The current one is [`actor.task-event@2`](/docs/contracts/actor.task-event).

- Version: 1.0.0
- Owner: actor
- Visibility: public
- Status: active
- Compatibility: backward
- Decision: [ADR-044](/docs/adr/ADR-044)
- Schema: [`https://openvibe.network/contracts/actor/task-event.v1.json`](/docs/contracts/actor.task-event@1.json)

actor.task-event@1: one event on a task's live stream (GET /api/v1/tasks/:id/events, text/event-stream; the SSE id is SEQ, so a reader resumes with Last-Event-ID). KIND is run.job-stream-event@1's three, as platform.task@1 progress names them: state (the task moved to STATE), output (one step of the agent's work: AGENT says what it is doing in TEXT, or calls TOOL with a short INPUT summary, or a tool answered), end (the task ended in STATE; nothing follows). Events are best-effort; the task record (GET /api/v1/tasks/:id) is the source of truth.

## Fields

| Field | Type | Required | Description | Constraints |
| --- | --- | --- | --- | --- |
| `task_id` | string | yes |  | - `pattern ^tsk_[0-9A-HJKMNP-TV-Z]{26}$` |
| `seq` | integer | yes |  | - `minimum 1` |
| `kind` | enum | yes |  | - `one of "state", "output", "end"` |
| `at` | string | yes |  | - `format date-time` |
| `state` | enum |  |  | - `one of "queued", "running", "verifying", "succeeded", "failed", "cancelled"` |
| `agent` | string |  |  | - `pattern ^[a-z][a-z0-9-]{1,63}$` |
| `step` | enum |  |  | - `one of "plan", "text", "tool_call", "tool_result", "check", "handoff"` |
| `text` | string |  |  | - `maxLength 8000` |
| `tool` | string |  |  | - `maxLength 128` |
| `input` | string |  |  | - `maxLength 2000` |
| `is_error` | boolean |  |  |  |

## Examples

From the contract's own test fixtures: valid ones validate, rejected ones must fail.

The fixtures that ship with the package are the current major's.

## Validate

~~~~
const contracts = require('openvibe-contracts');
contracts.validate('actor.task-event@1', value);   // { valid, errors: [{ path, message }] }
~~~~