Owned event types
This processor owns no event types.
Consumes
events.iterate.com/slack-agent/createdowned by slackBirth certificate for the Slack facet on an agent stream.events.iterate.com/slack/thread-route-configuredowned by slackDeclares that a Slack thread timestamp maps to a stream path. The Slack router reduces this into its routing table on `/integrations/slack/{connection}`.events.iterate.com/slack/webhook-receivedowned by slackRaw Slack Events API callback body, appended by the webhook route to `/integrations/slack/{connection}` and forwarded unchanged to routed thread streams.events.iterate.com/agent/summary-updatedowned by agentUpdates the agent's human-readable summary. Omitted fields remain unchanged, null clears an optional field, and pinned false unpins. The same event is used whether an agent or a human initiated the edit; the processor's own conditional waiting clear ({ waitingFor: null, clearWaitingForThroughOffset }) only clears a wait established at or before the waking input's offset.events.iterate.com/stream/processor-revivedowned by coreA recovery-wired stream processor was revived after its incarnation died owing background work (in-flight obligations lost to an eviction). Appended by the platform's recovery keepalive, never emitted by a processor; the payload's processorSlug names which processor was revived (the type string is shared by every recovery-wired processor). Consumption is optional and only needed when the processor reacts to the fact itself; an unconsumed tail still receives the runner's eventless at-head turn so open obligations are not stranded.
Emits
events.iterate.com/agents/context-addedowned by agentModel-visible context arrived (user message, developer note, assistant output, system item). The single source of truth for what the LLM sees.events.iterate.com/capability-host/script-run-requestedowned by capability-hostA script should run in this capability scope. Before any attempt starts, the code is typechecked against the scope's capability types: a script with a PROVABLE error — a syntax error, or a near-miss typo where the compiler names the fix ("Did you mean 'get'?") — settles straight to an error completion carrying the compiler errors, without ever running (no started event). Everything less certain runs: capabilities are provided dynamically and declared types can lag the runtime, so bare property/argument mismatches, unknown/untyped capabilities, non-async block shapes, and checker failures all let the script run unchecked.events.iterate.com/agent/binding-setowned by agentSets or enriches the typed external object this agent represents. Bindings are normally emitted atomically with integration agent creation, never inferred from paths. Contract-owned but reduced by integration processors, not by the agent.