AgentsStepAppendedPayload agents.step.appended@1

Generated at from openvibe-contracts v0.419.0 and openvibe-sdk v0.161.0.

Version
1.0.0
Owner
actor
Visibility
first-party
Status
active
Compatibility
backward
Decision
ADR-044
Schema
https://openvibe.network/contracts/events/payloads/agents.step.appended.v1.json

agents.step.appended v1 (one agent system, 2026-11-12). A step was appended to a run: the payload is the appended agents.step@1, whole. OpenVibe.Events carries it with the run's owner as the subject, the product that ran it as the source (actor, codes, run, …) and visibility subject; a reader follows a run live without polling the step log. The namespace is agents (hyphen-free: Events namespaces cannot contain a hyphen). One producer per run: the product that stores the run publishes its steps, and the step's own product names the agent.

Fields

This schema has no named fields.

Examples

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

Valid: message
{
  "run_id": "tsk_01K9R2V6M8Q4T0B7C3D5E9F2GH",
  "seq": 6,
  "kind": "message",
  "text": "I found the failing test and am fixing it.",
  "started_at": "2026-11-12T10:00:30Z",
  "ended_at": "2026-11-12T10:00:30Z"
}
Rejected: missing-seq
{
  "run_id": "tsk_01K9R2V6M8Q4T0B7C3D5E9F2GH",
  "kind": "message",
  "text": "A step without its place in the log.",
  "started_at": "2026-11-12T10:00:30Z"
}

Validate

const contracts = require('openvibe-contracts');
contracts.validate('agents.step.appended@1', value);   // { valid, errors: [{ path, message }] }