Skip to content
worca

Events reference

Every event worca emits, by domain. See Events overview for the envelope and how to subscribe. The source of truth is src/worca/events/types.py in the repo.

Pipeline events

Section titled “Pipeline events”

A single run’s lifecycle, telemetry, and control plane.

  • pipeline.run.* — run lifecycle.
    started, completed, failed, interrupted, cancelled, resumed, paused, resumed_from_pause
  • pipeline.stage.* — per-stage lifecycle.
    started, completed, failed, interrupted
  • pipeline.agent.* — agent telemetry (high volume).
    spawned, tool_use, tool_result, text, completed
  • pipeline.bead.* — task tracker.
    created, assigned, completed, failed, labeled, next
  • pipeline.git.* — git operations.
    branch_created, commit, pr_created, pr_merged
  • pipeline.test.* — test loop.
    suite_started, suite_passed, suite_failed, fix_attempt
  • pipeline.review.* — review loop.
    started, verdict, fix_attempt
  • pipeline.circuit_breaker.* — error classification.
    failure_recorded, retry, tripped, reset
  • pipeline.cost.* — cost / token telemetry.
    stage_total, running_total, budget_warning
  • pipeline.milestone.*, pipeline.loop.* — control plane.
    milestone.set, loop.triggered, loop.exhausted
  • pipeline.hook.* — governance telemetry.
    blocked, test_gate, dispatch_blocked, dispatch_allowed
  • pipeline.preflight.*, pipeline.learn.*.
    preflight.completed, preflight.skipped, learn.completed, learn.failed
  • pipeline.claude_md.* — CLAUDE.md load mode resolution.
    mode_resolved (records the effective mode + its precedence source: CLI flag, template, project setting, or default)

Control events

Section titled “Control events”

Inbound signals external systems use (typically a control webhook response) to steer a run.

  • control.milestone.approve
  • control.pipeline.pause
  • control.pipeline.resume
  • control.pipeline.abort

Fleet events

Section titled “Fleet events”

Lifecycle of a fan-out run across N independent projects.

  • fleet.launched, fleet.halted, fleet.completed, fleet.failed, fleet.circuit_breaker.tripped

Workspace events

Section titled “Workspace events”

Lifecycle of a coordinated run across interdependent projects.

  • Lifecycle: launched, completed, failed, halted, paused, resumed, circuit_breaker.tripped, guide_conflict
  • Plan: plan.started, plan.completed, plan.failed, plan.loaded, plan.partial
  • Tier: tier.started, tier.completed, tier.failed
  • Integration: integration_test.started, integration_test.passed, integration_test.failed, umbrella_issue.created

Chat-rendered subset

Section titled “Chat-rendered subset”

Chat integrations render a curated subset into messages — typically run completed / failed / interrupted, PR created / merged, circuit-breaker tripped, and budget warnings. Other events fire but aren’t sent to chat unless a renderer is added. See Chat integrations.